Home›Support›English Support›[Resolved] WPML AI / translation gets stuck in progress in the Translation Job
[Resolved] WPML AI / translation gets stuck in progress in the Translation Job
This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to translate a published page using the + icons in the post edit UI. When you click on the +, it launches the Advanced Translation Editor (ATE) with all translations prefilled. After accepting and completing the translation, the ATE closes, and the + icon changes to a refresh icon, then a cog icon. However, the translated page is not accessible via the icon or the language dropdown, and there is a translation job marked as 'in progress' in the Translation Management > Translation jobs table that never completes. Solution: The issue occurs because the page contains an HTML block with a large JavaScript script, which breaks when ATE tries to translate it, resulting in an invalid XLIFF file. WPML then rejects this file. We recommend two possible workarounds: 1. Temporarily delete the problematic section and add it back after the translations are complete. 2. Avoid using ATE for this page. Instead, use the Classic Translation Editor (CTE) or the WordPress editor to manually edit the translations with Elementor. This method is more time-consuming but allows you to use the automatically translated texts from the translation memory. We have escalated this issue to our developers for a permanent fix.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking for 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 problem persists, please 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.
I was able to delete the jobs using the mentioned interface. I then modified slightly the original page, saved it then re created the translation job. Unfortunately, these are also stuck in progress.
not sure if it helps but i cloned the website locally to have an easier access to the php-fpm logs and it shows these warnings. We do not use nor need xliff, is there a way to disable this ?
[17-Apr-2025 13:45:17 UTC] PHP Warning: mb_ereg_replace_callback(): mbregex search failure in php_mbereg_replace_exec(): retry-limit-in-match over in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-validate-html.php on line 363
[17-Apr-2025 13:45:17 UTC] PHP Warning: mb_ereg_replace_callback(): mbregex search failure in php_mbereg_replace_exec(): retry-limit-in-match over in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-validate-html.php on line 363
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): Entity: line 426: parser error : Opening and ending tag mismatch: source line 65 and script in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): /script>]]></script>]]></source> in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): ^ in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): Entity: line 426: parser error : Sequence ']]>' not allowed in content in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): /script>]]></script>]]></source> in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): ^ in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): Entity: line 426: parser error : Opening and ending tag mismatch: trans-unit line 64 and source in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): /script>]]></script>]]></source> in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): ^ in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): Entity: line 789: parser error : Opening and ending tag mismatch: body line 17 and trans-unit in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): </trans-unit> in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): ^ in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): Entity: line 978: parser error : Opening and ending tag mismatch: file line 3 and body in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): </body> in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): ^ in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): Entity: line 979: parser error : Opening and ending tag mismatch: xliff line 2 and file in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): </file> in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
[17-Apr-2025 13:45:45 UTC] PHP Warning: simplexml_load_string(): ^ in /var/www/html/web/app/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Madrid (GMT+01:00)
Hi there,
I’m really sorry for the ongoing delay. Our team is actively investigating the problem—so far we’ve tested several potential fixes, but none have fully resolved the issue. Rest assured we’re treating this with priority, and I’ll update you the moment we have concrete news or a permanent solution in place.
Thanks Paola. It's a really weird issue. I just tried again deleting and entirely recreating the page manually, then translate it, just for one language at a time, to no avail. The translation job get stuck as "in progress".
The only error I see is the xliff one I mentioned earlier: "The xliff file could not be read."
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Madrid (GMT+01:00)
First of all we want to apologize for the delay.
The issue arises because the Atlas AI page contains an HTML block with a large JavaScript script block, and that is getting broken when the advanced translation editor (ATE) tries to translate the page, and the generated XLIFF file of the translation is invalid, so when ATE tries to deliver the translation via an XLIFF file back to WPML, WPML rejects it.
There are two possible workarounds until this is fixed.
1. is to delete that section for the time being (they could add it back after translations are complete), or
2. is to not use ATE for this page (which means the automatic translations are not available). Either use classic translation editor (CTE) for this page, or choose the WordPress editor to edit the translations (and then edit them with Elementor).
With the latter it is somewhat time consuming, but if the client uses the + buttons to translate this page in ATE, they won't be able to complete the translation, but they will be able to copy and paste all of the automatically translated texts which are still available in translation memory.
