Skip Navigation

[Resolved] WYSIWYG Not Displaying at Custom Field (Secondary Languages)

This support ticket is created 5 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 34 replies, has 4 voices.

Last updated by Susan Siow 5 years, 3 months ago.

Assisted by: Waqar.

Author
Posts
#1278157

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Sorry! Didn't mean to alarm you, that's a typo on my part, the version is 4.2.8

#1278209

Hi Nigel,

Thank you for the clarification! 🙂

Regards,
Susan

#1328243

I'd like to add my voice to this issue, as I'm encountering the same problem : added multiple WYSIWYG custom fields with Type to WooCommerce products and seing all of them as single line. Clients will find it impossible to translate.

You advertise Toolset's capabilities to interact with WooCommerce, and WPML is part of the OTG family... surely, this can be fixed after having been reported in 2018 in a few threads, and now here since January?

Tks

#1329235

Hi Susan & Jean,

I'm happy to update that a fix for this issue has been included in the next release of Types ( 3.3.5 ) and WooCommerce Multilingual ( 4.6.6 ).

I can understand that you've been waiting too long for this fix, but both these versions are planned to be released soon.

Will update you through this ticket, once they're out.

regards,
Waqar

#1338325

The issue is resolved with the latest updates, thanks Waqar!