Translations are creating unwanted tags throughout website.

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

Problem:
The client is experiencing an issue where translations are inserting unwanted
tags in the HTML across the website, which are not present in the original English text. This issue is visible on the homepage and menu, and there are [returns] in the backend text editor that should not be there.

Solution:
We have consulted with the developers of the Advanced Translation Editor (ATE), and they provided the following insights and suggestions:
1. When segments are manually joined, they are combined with a \n (e.g., joining phrase1 and phrase2 results in phrase1\nphrase2).
2. For the pages in question, it appears the segments may have been manually joined.
To address this, they suggest:
- Unjoining the segments, which should resolve the issue.
- Alternatively, updating the translations using the previously recommended solution.

Currently, there is no batch solution to address this issue comprehensively. The only option available is to fix it manually. Our developers are considering creating a script to automate the process, but it will require time as it may introduce additional complications.

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. If the issue persists, please open a new support ticket at WPML support forum for further assistance.

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: ATE

This topic contains 0 replies, has 0 voices.

Last updated by Jasper 4 weeks ago.

Assisted by: Kor.

Author	Posts
December 11, 2024 at 4:25 pm #16504621
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for your response. I’ve passed your feedback along to our 2nd Tier Support team. We are indeed working on the staging site you provided and have deactivated the third-party plugins to ensure they are not causing the issue. I’ll update you as soon as I receive any feedback.
December 12, 2024 at 8:57 pm #16509421
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for your patience. I’d like to share some feedback based on what our 2nd Tier Support has mentioned. Currently, we do not have a batch solution to address this issue. The only option available is to fix it manually. According to our developers, creating a script to automate the process is possible, but it will require time, as it may introduce additional complications. The issue is now escalated to our developers for consideration.
December 12, 2024 at 9:40 pm #16509496
Jasper	Hi Kor, Thanks for your reply. I want to make sure that I understand correctly. This issue is not something that can be fixed. Are we talking about manually fixing the current translated material? How about the other 30+ languages (multiplied with hundreds of posts) that I still need to have to automatically translate (and many more in the future). Is there no fox there too? Because this issue renders an enormous problem. Surely translating a standard text from WP that has no further formatting should not have this behavior? The impact on our budgets would be an enormous (if not impossible) strain. I really, really hope this is recognized as a problem impacting WPML functionality that needs further escalation. Please advise. Regards
December 13, 2024 at 5:04 am #16509900
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for your response. Unfortunately, yes, you will need to manually correct the current translated content. Our developers are aware of this issue, along with several others, and these are already in the queue for review and resolution. For now, there are no immediate solutions to prevent this from occurring in future translations.
December 13, 2024 at 9:38 am #16510612
Jasper	Oké. Regarding the issue... When is the issue-fix planned and how will I know when this is fixed? The problem is that If I were to fix this manually (thousands of pages/post). I need a system to do this: The most logical way is to use the 'review' translations' option. However this function does not work. It does state I have 600+ reviews to do now. But when I click it. I have no results. Naturally I am not fluid in 30+ languages. So I need a large international team to check all pages. These people will not be 'developers' so I need something simple to train and explain them. I am really worried about my project now. New threads created by Kor and linked to this one are listed below: https://wpml.org/forums/topic/review-translation-not-working-in-translation-management/
December 13, 2024 at 1:35 pm #16511587
Kor Supporter Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your reply. The review system should work. I've split the ticket here https://wpml.org/forums/topic/review-translation-not-working-in-translation-management/ so that we can follow up with the review translation issue. As for this ticket, I will drop a notice here once we have updates about the fixes.
December 14, 2024 at 11:23 am #16513395
Jasper	Hi Kor, I am still testing the issue with the <p>s. I might be interesting to keep this ticket open. I found that if I delete an automatic translation (restoring my credits) and then redo the translation on post level, most of the <p>s are gone except when it's a . This is good news if I understand how this bug works, because it seems that it can be managed providing I can do this in bulk.
December 14, 2024 at 11:41 am #16513444
Jasper	I seems also to work if i redo the translation in Translation Management. Problem is only that's unknown if it will affect my credits. So then the issue is very specific and only for the blockquote?
December 14, 2024 at 5:11 pm #16513770
Jasper	Never mind... That delivered other problems. The still there. I now solved it with a CSS code: br { display: none; } It's not a clean solution but it works.