Translation of specific element not saved because of HTML Tags

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	-
-	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	-

Supporter timezone: Asia/Singapore (GMT+08:00)

Tagged: Bug

This topic contains 9 replies, has 2 voices.

Last updated by Kor 8 months, 2 weeks ago.

Assisted by: Kor.

Author	Posts
June 10, 2024 at 5:20 pm
edoardod-8	Background of the issue: I am trying to save the translation of a specific element but encountered an error. Here is the link to the screenshot: hidden link. The issue can be seen on this page: hidden link. Symptoms: The original text contains nested formatting tags (one tag inside another). Please nest the formatting markers in your translation in the same order. It doesn't save the translation element. Questions: Why is the translation of the specific element not being saved? How can I resolve the error related to nested formatting tags?
June 10, 2024 at 5:32 pm
June 10, 2024 at 6:11 pm #15723600
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for your patience. I've generated a new button on this page hidden link , as illustrated in the attached screenshot, and managed to translate it without encountering any problems. Please attempt to replicate the method I've described and confirm if it resolves the issue for you as well.
June 10, 2024 at 6:27 pm #15723641
edoardod-8	I want you to fix the above button that causing the problem of HTML Tag. It should not cause the problem when all the tags are placed but still it's not saving it. Please don't give a generic solution, There are hundreds of pages, I cannot create duplicate buttons on all pages. I want you to fix the problem of "element not saving because of tag"
June 10, 2024 at 7:13 pm #15723703
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for responding. I appreciate your understanding. I'll double-check and provide you with an update as soon as possible.
June 11, 2024 at 5:55 pm #15728555
edoardod-8	Any updates?
June 11, 2024 at 6:42 pm #15728735
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I'm able to replicate the issue here hidden link on our sandbox site and this is the test page hidden link . I will escalate this further to our 2nd Tier Support for further investigation and will get back to you once I've feedback.
June 12, 2024 at 7:03 pm #15733357
edoardod-8	Its been 2 days, any updates ?
June 12, 2024 at 7:10 pm #15733376
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I've received a response from our 2nd Tier Support and this is what they mentioned. Please use the workaround by changing the HTML code to the one below. From : <a class="button primary-button tooltip-container button-callout show-callout" href="#plan-show">VIEW PLANS <span class="tooltip" > TRY RISK FREE <br>For 14Days! </span></a> To : <a class="button primary-button tooltip-container button-callout show-callout" href="#plan-show">VIEW PLANS<span class="tooltip">TRY RISK FREE <br>For 14Days!</span></a> You can test it here hidden link Using the login link here hidden link A fix will be available soon.
June 13, 2024 at 1:29 pm #15736459
edoardod-8	My question's still there: Why I cannot able to update translation with following code: VIEW PLANS TRY RISK FREE For 14Days!
June 13, 2024 at 2:05 pm #15736670
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for responding. The problem stems from the nbsp markers, which fail to save into xliffs, thus leading to issues with the Advanced Translation editors. Our developers are already working on resolving this, and a fix will be provided shortly. In the meantime, please utilize the suggested workaround I provided earlier.

The topic ‘[Closed] Translation of specific element not saved because of HTML Tags’ is closed to new replies.