Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is using the Divi theme builder and has translated strings related to the Divi template builder. Despite being visible in WPML > string translation, these translated strings are not showing on the frontend.
Solution:
1. Ensure that the Divi template itself is translated, as strings found in the String Translation might belong to the template. If the template is not translated, the strings will not appear translated on the frontend. Detailed steps for translating Divi templates can be found here: Translating Divi Templates Documentation.
2. Use the Advanced Translation Editor (ATE) which includes Translation Memory. This feature helps in avoiding repetitive translation of the same content across different layouts. More information on ATE and Translation Memory can be found here: Translation Memory Documentation.

If this solution does not resolve your issue or seems 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: 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.

Tagged: 

This topic contains 6 replies, has 0 voices.

Last updated by Carlos Rojas 1 week ago.

Assisted by: Carlos Rojas.

Author Posts
November 21, 2024 at 10:49 am #16428525

marcom-187

Background of the issue:
I am working on a site under development using the Divi theme builder. I have updated everything and confirmed there are no debug errors after the update related to the known issue (https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/comment-page-1/?unapproved=9050984&moderation-hash=e12e94b570ead16ad38b544f6a2e0567#comment-9050984).

I have translated strings related to the Divi template builder, specifically domain: page-builder-shortcode-strings-5048. Translations are visible in WPML > string translation.

Symptoms:
The translated strings are not visible on the frontend despite being visible in WPML > string translation.

Questions:
Why are the translated strings not showing up on the frontend?

November 21, 2024 at 11:34 am #16428718

Carlos Rojas
Supporter

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

Timezone: Europe/Madrid (GMT+01:00)

Hello,
Thank you for contacting us

1.- These strings seem to come from a Divi template, if this is the case, then you need to translate the template, and there you will be able to translate the strings. Please check this section of the documentation where the steps to translate the Divi templates are described: hidden link

Could you tell me the results of the steps described above?

2.- Please share the debug information of the site as described in this link: https://wpml.org/faq/provide-debug-information-faster-support/

Regards,
Carlos

November 21, 2024 at 2:54 pm #16429771

marcom-187

Thanks for the response.
The problem of the default method is that it require really long time.
Since I found in "string translation" the only strings I needed to translate and well associated to the template I believe that I could translate directly there.

However if I translate there there is no effect. Off course the body template method is working, but was not the way I was looking for.

Are you sure there is not a workaround?

November 21, 2024 at 3:07 pm #16429944

Carlos Rojas
Supporter

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

Timezone: Europe/Madrid (GMT+01:00)

Hi,

The strings that you found in String Translation might belong to the template, but if the template itself is not translated, then the strings won't appear translated.

November 21, 2024 at 3:12 pm #16429989

marcom-187

Ok I understand. Now I'd like then to clear the translation queque from translations that are useless, like those string translation. However if I select them and click on "cancel translation reviews" I receive the error " This action does not apply to any of the selected translation jobs". If it is not the right button please let me know how to fix

November 22, 2024 at 8:24 am #16432210

marcom-187

Just a small integration related to the previous response:

The problem is that I have a lot of divi builder layouts, all sharing some modules.
Those modules are exactly the same across different layouts, and following your guide I should translate the same module many times.

To give an idea:

Module A is shared across 10 layouts. I have 5 language on my site.
Following your approach I should do 40 translations of the same module (10 * 4 languages, excluding the default language).

As you may imagine, I need a workaround to manage this scenario more smartly.
This would require a long effort not only the first time I configure all, but also for future updates.

That's why I hoped to manage ti through string translation and not by fully translating each layout.

Can you suggest a solution in this direction please?

November 22, 2024 at 11:01 am #16433399

Carlos Rojas
Supporter

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

Timezone: Europe/Madrid (GMT+01:00)

Hi there,

Yes, there is a solution for that problem and it is to use our Advanced Translation Editor (ATE) that has Translation Memory (https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/) which will prevent you from translating the same content over and over 🙂