Translating Scripts

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

Problem:
You need to translate scripts within a post, such as iframes or shortcodes, for different languages. However, when using the Advanced Translation Editor (ATE), you encounter issues where the original language script appears blank and modifications in the new language do not save correctly. After editing and saving the post, scripts revert back to the original language.
Solution:
We recommend not using the ATE for pages that contain scripts you need to translate. Instead, use a different method to manage translations for these specific pages to avoid the issues you're experiencing. For detailed guidance on how to implement this, please refer to our documentation on using different translation editors for different pages: Using Different Translation Editors for Different Pages.

If this solution does not apply to your case, or if it seems outdated, we highly recommend 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. Should you need further assistance, please do not hesitate to open a new support ticket 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.

Tagged: Documentation request

This topic contains 36 replies, has 2 voices.

Last updated by Bruno Kos 4 months, 2 weeks ago.

Assisted by: Bruno Kos.

Author	Posts
July 11, 2024 at 9:21 am #15933845
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	I did not access your site since I posted an answer yesterday. Does this happen for every new translation?
July 11, 2024 at 9:50 am #15933991
justinK-16	So far only the very first NEW post I created and went to translate for the first time. I have opened another other post to translate (for example in French for the first time, but the original post had already been translated to Italian) and all appears fine. I have also translated Pages in other languages with no problems appearing. At this point, it only seems to be this one post. And yes it was a brand new post and the first of any translation of that post. As I said earlier this happened to be the first translation since you accessed the site. I'm not saying you did anything just if you are aware of doing anything that may have caused this to occur it would be helpful so we can resolve it.
July 11, 2024 at 11:06 am #15934531
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Can you try creating a new post/page with the same elements but only minimal content, does it show duplicate translation now? Or take one of the existing posts, make small change there (such as adding something to the title), remove this change, save again and open in translation editor. Are these fields doubled? Because XML we provided should not cause it.
July 11, 2024 at 12:32 pm #15934977
justinK-16	Hi Bruno I DID NOT at any point add/register the XML - as I noticed this issue first. I don't want to make any changes until all is working properly again. As you suggested, I modified a couple of existing posts, saved, removed, saved, and opened again and I cannot replicate the error/issue. I have also canceled the jobs - the issue still remains upon translating again. I have also been translating existing pages all morning and have not had the issue arise. It is just this one post that I am aware of. If you still have access to our site, can you please have a look at this page as it may be obvious to you as to what the issue is. hidden link About halfway down you will see the repetition of the post but instead of the original language displaying "Heading (h3)" or "Text editor" - it now displays "wpml_string_wrapper_content" next to every field in the original language.
July 11, 2024 at 1:01 pm #15935196
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Can you create a new ticket for this issue? As this ticket is already going quite long and this non-related issue could even prolong it further (this is also for our support rules to handle one issue at a time).
July 11, 2024 at 1:17 pm #15935265
justinK-16	It doesn't seem unrelated...considering the issue arose the next time I performed a translation after I provided access to the site to assist with an issue. This "new" issue happened while investigating while investigating the past issue.
July 15, 2024 at 5:57 am #15952182
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	This ticket is about methods of translating scripts. If there is anything else related to translating scripts let me know.