Skip to content Skip to sidebar

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.

This topic contains 2 replies, has 0 voices.

Last updated by cedricV-14 2 months, 1 week ago.

Assisted by: Otto.

Author Posts
November 13, 2025 at 2:49 pm #17575524

cedricV-14

Background of the issue:
I am trying to resolve a PHP error that occurs multiple times an hour. The error is related to the simplexml_load_string() function in the WPML plugin. I have already searched the database for the sequence ']]>' and ']]>' but couldn't find it.

Symptoms:
PHP Warning: simplexml_load_string(): parser error: Sequence ']]>' not allowed in content in /data/sites/web/itdailybe/www/wp-content/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-xliff-reader.php on line 21.

Questions:
How can I stop receiving the PHP error related to simplexml_load_string()?
What could be causing the ']]>' sequence error in the WPML plugin?

November 13, 2025 at 4:51 pm #17576262

Otto
WPML Supporter since 09/2015

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

Timezone: America/Argentina/Buenos_Aires (GMT-03:00)

Hello,

The warning almost always means malformed XML in a specific job. The fastest path is to identify the job via ATE logs, cancel the job, fix the problem and send it again.

Let's try to do the first two things, and once we locate the problematic page, we will be able to understand the root cause of the problem.

1.
Go to WPML → Support → Advanced Translation Editor Error Logs and note any job/post IDs referenced around the warning timestamps

2.
If there is a hint about the problematic translation, go to WPML → Translations, select suspected jobs and cancel them

This should stop the warning.

Let me know how this go and we will move forward from there.

Best Regards,
Otto

November 13, 2025 at 8:58 pm #17576764

cedricV-14

Hi Otto,

Thanks for the help!
I've found the problem article (hidden link).
Removed the translation, fixed the code malfunction in the original language and translated again.

Now the issue is resolved.