Nearly Two Months Old Bug Not Solved - WYSIWYG Not Displaying at Custom Field

This support ticket is created 5 years, 9 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/Hong_Kong (GMT+08:00)

Tagged: Setting up custom fields, Types plugin

This topic contains 1 reply, has 2 voices.

Last updated by Luo Yang 5 years, 9 months ago.

Assisted by: Luo Yang.

Author

Posts

March 5, 2019 at 2:54 am #1209784

Susan Siow

Dear Toolset,

I have started this thread on January 10, 2019 - https://toolset.com/forums/topic/wysiwyg-not-displaying-at-custom-field-secondary-languages/ and it's almost two months but not fixed.

Please help, thanks.

March 5, 2019 at 6:24 am #1209811

Luo Yang

Hello,

As you can see it is in our known issue list in open status:
https://toolset.com/errata/wysiwyg-field-assigned-to-woocommerce-products-and-translated-in-wpml-becomes-simple-text-inputs-in-wpmls-translation-editor/

I have checked it in our to-do list, it is marked as "Major" Priority task, our developers are working on it, but I am not sure when will it be fixed.

Currently, as a workaround, you can try to copy/paste the HTML codes in your screenshot:
hidden link

From left to right input box, only translate the text, do not translate the HTML tags.