This thread is resolved. Here is a description of the problem and solution.
Problem: You are using global modules with WPML in Divi and have set translations for these modules in the Divi Library. However, when placing the global module on a page, WPML still prompts for translations on the page itself and ignores the translations set in the Divi Library. Solution: First, ensure you have followed the steps outlined in the documentation for translating Divi and Extra global modules with WPML. You can find the guides here:
If the problem persists after following these guides, consider switching from the Classic Translation Editor to the Advanced Translation Editor for more flexibility with translations.
If these solutions do not resolve your issue or seem outdated, we recommend opening a new support ticket. We also advise checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I'm testing using global modules with WPML. I've created a global module on my root language: EU English. I went into the Divi -> Divi Library and updated the translations for all other languages connected to English.
Symptoms:
When I put the global module on a page, the page still expected me to add translations to the page itself for the global module, even though the global module already has its own translations in the divi library. When I update the translations on the page itself, WPML completely ignores those translations, and instead displays the translations set in the divi library.
Questions:
Is there a setting to sync translations between the Divi library and the page itself?
I've reviewed that page and it seems to state something contradictory to what is actually happening:
"Perform the translation as normal. Now when you translate a page that uses the global module, only the other elements of the page will need to be translated. The translated content of the global module is preloaded into the translator."
My global module is fully translated; however, when I place it on a page, it expects me to still translate all the global module text for the page. However, it doesn't actually use those translations, but instead uses the divi library global module translations.
I am using the classic editor.
Here's a video showcasing my problem clearly: hidden link
Thank you for providing the screencast — it really helped clarify the issue.
From what I can see, the behavior you’re experiencing is likely due to using the Classic Translation Editor.
The documentation excerpt:
“Perform the translation as normal. Now when you translate a page that uses the global module, only the other elements of the page will need to be translated. The translated content of the global module is preloaded into the translator.”
…assumes that you’re using WPML’s Advanced Translation Editor (ATE). The Classic Editor is WPML’s legacy tool and lacks many modern features, including better handling of translations.
I recommend switching to the Advanced Translation Editor and testing again. Please note that the Classic and Advanced editors are not synchronized, so you’ll need to retranslate the pages using ATE.
That's unfortunate. Is there no alternative solution while keeping the Classic Translation Editor?
The advanced translation editor lacks some features that we require. Primarily, if a paragraph has even one word changed, it requires the entire paragraph to be re-translated. The Classic Translation Editor does well on this - it keeps the old translation so that if one word is changed in English, only one new word has to be translated.
Unless the Advanced Translation Editor has been updated to be more user friendly, we'd like to stay with the Classic Translation Editor and find a solution for it. Please let me know if there is any, thanks!
I’m afraid there is no alternative solution if you’re expecting the behavior as described in the documentation.
However, if you’ve been using the Classic Translation Editor for a while, I recommend giving the Advanced Translation Editor a try. It offers more flexibility, including the ability to split paragraphs into multiple segments for translation. To enable this, simply deactivate the option “I prefer bigger segments” in the editor settings.
