Resolved

Reported for: WPML Multilingual CMS 4.1.0

Resolved in: WPML 4.1.2

Topic Tags: Media Translation

Symptoms

There is an issue which prevents editing translations of page builder contents using the native WordPress editor.

After clicking the Update button, the translated content is replaced with the original.

This issue occurs when the following conditions are met:

  • The Translation Management, String Translation, and Media Translation add-on plugins are active.
  • The post content was built using a page builder (WPBakery, Divi, Elementor, etc.).
  • The translation was previously translated through a translation job (using the Classic or Advanced Translation Editor, or job sent to a remote service).

 

Workaround

As a workaround, we can suggest 2 options:

  • Use a translation editor (Classic or Advanced) instead of the native WordPress editor.
  • Temporarily disable the WPML Media Translation add-on while editing the post translation through the native editor. Please note that this might result in images not to be converted in the post content. For example, if you have an image http://example.org/english-image.jpg which was “translated” to http://example.org/french-image.jpg, the URL replacement in the post content will not work if you translate from English to French.

25 Responses to “Cannot edit page builder translations with the native WordPress editor”

  1. Same problem here – can’t save the changes on the secondary language’s homepages, using WPBakery.

    When do you provide us with this minor update?

    • Hi @davidG-36,

      We are planning to release a minor update with a fix for this issue next week (possibly on Monday).

      Thanks,
      Pierre

  2. Thanks! Disabling WPML Media fixes the issue. Please roll out an update ASAP as we’re in the middle of the holiday shopping season…

  3. I am having the same issue with WPBakery Page Builder.. Is there a workaround? Hoping you get back with an update soon, as i recently committed to both a WPML subscription and a WPBakery reliant theme under the assumption (based on the theme’s spec list) that they were compatible and I will be late on a deadline for a client if things aren’t resolved soon.

    • Hi @hayaM,

      We released an minor version of WPML (4.1.2) this morning and it includes a fix for this issue.

      Could you please update to this new version and let us know if it fixes your problem?

      Thanks,
      Pierre

      • Thanks I have a question: I installed WPML on my staging site last week, and still haven’t registered it because the URL is a temporary one given to me by GoDaddy and I will register WPML once I push my staging site onto the live site. Is there a way to update the plugin on the staging site and then use it again when it’s on the live site?

        Thanks

        • Hello @hayaM,

          I think you can register the staging site (with staging key), and when you move to the production site you can unregister (remove staging key) and register again with a new key.

          Let me know if this works for you.

          Thanks!

          • Thanks Pierre! Just to clarify: I can start off with registering the staging site, then in a month I can update it? Will the system allow me to do that?

            • Hi @hayaM, I don’t think it’s a problem since you can unregister and register again on WPML side. Depending on your purchased plan, you might need to remove a site key before to add a new one. If you have some doubts about it, feel free to open a support ticket.

              Thanks,
              Pierre

  4. I don’t see the update possibility in WordPress Dashboard > Plugins.
    It still shows 4.1.1 as a last version.

    Is it necessary to update wordpress to 5.0?
    If yes, I will not do it! Because of too many bad reviews for 5.0

    I need the solution for wordpress 4.9

  5. I can say with certainty that this didn’t fix the issue for me. If anything it made it worse. My images are 100% in english regardless of what language the site is using or how wpml media is active or not.