Skip Navigation
Buy Now
Home » Errata » WYSIWYG field assigned to WooCommerce Products and translated in WPML becomes simple text inputs in WPML’s Translation Editor

WYSIWYG field assigned to WooCommerce Products and translated in WPML becomes simple text inputs in WPML’s Translation Editor

Resolved

Reported for: Toolset Types 3.0.1

Resolved in: WCML 4.6.7

Topic Tags: Setting up custom fields, Types plugin

Symptoms

WYSIWYG fields assigned to WooCommerce Products, which are then translated in WPML, become simple text inputs instead of Rich WYSIWYG Fields in WPML’s Translation Editor.

This works fine on any other post type and happens only if the WYSIWYG is attached to WooCommerce Products.

Workaround

There is currently no workaround for this.

10 thought on WYSIWYG field assigned to WooCommerce Products and translated in WPML becomes simple text inputs in WPML's Translation Editor

    • Our developers are aware of this issue and will do their best to resolve this problem. I have no ETA as of yet, however. We will update this erratum, as soon we have news.

    • Susan, this is an issue within Types and only happening with WooCommerce. It is not due to WPML and the fix will be shared here once available.

      Can I ask why you comment with several different users and emails?
      I can then remove the ones of the user that you do not want to appear, I have at least 2 authors of comments , both seem to be you 🙂
      Please let me know which you want to use (I suggest the Toolset user)

      Thanks!

  • Hi Beda,

    Kindly apply ‘Susan Siow’.

    The reason of the duplicated comments is I encountered your commenting publication issue. How’s the bug fixing status now?

    Thanks.

  • 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 in WPML’s interface.

    Clients will find it impossible to translate a multi-paragraph using that UI. They’ll have to work in another editor, copy/paste, and hope for the best.

    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

    • The fix is slated for 4.6.6 in WooCommerce Multilingual, together with a necessary change in Types 3.3.5

      I cannot state any release ETA as this is not yet confirmed.

  • This issue should be resolved now, with the latest Toolset and WPML/WCML Versions running.
    Please open a new support ticket in case you find other issues, we will be replying as soon as possible to any report.

    Thank you all for the patience.

Comments are closed