Error: "WPML tried to translate this page three times" and Critical Memory Exhaustion (712MB) Duri...

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

Problem:
The client is experiencing issues with WPML on their website. When updating translations after modifying a page in the original language, they encounter an error stating 'WPML tried to translate this page three times without success' and a critical memory exhaustion issue.
Solution:
We recommend checking if these issues persist under the following conditions:
1. Deactivate all plugins except for WPML to determine if there is an interaction issue with other plugins.
2. Switch the theme to a WordPress default, such as Twenty Twenty, to check for theme interaction issues.
If the problem continues, we suggest providing WordPress and FTP credentials for further investigation. Please ensure you follow our security guidelines when sharing sensitive information: Privacy and Security Policy.

If this solution does not apply because it might be outdated or not relevant to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if issues persist: 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: Exception

This topic contains 3 replies, has 0 voices.

Last updated by beataK-8 5 months, 4 weeks ago.

Assisted by: Bruno Kos.

Author	Posts
October 31, 2025 at 12:38 pm #17535797
beataK-8	Background of the issue: I am trying to update translations on my site hidden link using WPML. The issue arises when I edit an existing page in the original language (Polish), add or modify links, save the changes, and then attempt to update the translation in another language (e.g., English) using the Advanced Translation Editor. Symptoms: Error: "WPML tried to translate this page three times without success." Additionally, there is a critical memory exhaustion issue (712MB) during translation updates. Questions: How can I resolve the error message indicating WPML tried to translate the page three times without success? What steps can I take to address the critical memory exhaustion issue during translation updates?
October 31, 2025 at 1:39 pm #17535965
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Hi, Can you try this? 1. Edit wp-config.php and insert the following lines (just before /* That's all, stop editing! Happy publishing. */ part) define( 'WP_DEBUG', true); define( 'WP_DEBUG_LOG', true); define( 'WP_DEBUG_DISPLAY', false); 2. Reproduce the issue 3. Locate the debug log in: /wp-content/debug.log 4. Paste the latest lines here. No need to paste the entire log file, just 10 lines or so will do. Please censor any sensitive information. https://codex.wordpress.org/Debugging_in_WordPress But more importantly we need this: - do the above reproducing (so from step 2) - get the latest server debug logs (you can ask hosting support if unsure how to locate them) Let us know how it goes or if you need further information! This may tell us what exactly is causing the memory exhaustion issue. Also, if these logs don't point to any specific plugin, can you please check if this issue appears when: - only WPML plugins are activated, as it will tell us if there is an interaction issue with other plugin - theme is set to a WordPress default like Twenty Twenty as it will tell us if there is an interaction issue with your theme Regards, Bruno Kos
October 31, 2025 at 1:57 pm #17535991
beataK-8	Hi, here are the 10 latest debug logs. Regards [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML_ST_Verify_Dependencies::verify_wpml(): Implicitly marking parameter $dependenciesFilepath as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/wpml-string-translation/classes/class-wpml-st-verify-dependencies.php on line 15 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Core\Component\Translation\Domain\Settings\Settings::__construct(): Implicitly marking parameter $reviewMode as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Settings/Settings.php on line 25 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Core\Component\Translation\Domain\Settings\Settings::__construct(): Implicitly marking parameter $translationEditor as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Settings/Settings.php on line 25 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Core\Component\Translation\Domain\Settings\Settings::enableTranslateEverything(): Implicitly marking parameter $reviewMode as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Settings/Settings.php on line 78 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Core\Component\Translation\Domain\Settings\Settings::enableTranslateEverything(): Implicitly marking parameter $translationEditor as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Settings/Settings.php on line 78 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Core\Component\Translation\Domain\Links\HandleUpdateTranslation::adjustOnlyOnce(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Links/HandleUpdateTranslation.php on line 75 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Legacy\Component\Translation\Domain\Links\AdjustLinks::adjust(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Domain/Links/AdjustLinks.php on line 22 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Legacy\Component\Translation\Domain\Links\AdjustLinks::adjustLinksInStringTranslations(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Domain/Links/AdjustLinks.php on line 76 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Legacy\Component\Translation\Domain\Links\AdjustLinks::revertNameInTranslatedLinks(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Domain/Links/AdjustLinks.php on line 127 [31-Oct-2025 13:49:25 UTC] PHP Deprecated: WPML\Core\Component\Translation\Domain\Links\AdjustLinksInterface::adjust(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /home/lstusux/bws/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Links/AdjustLinksInterface.php on line 12
October 31, 2025 at 2:22 pm #17536151
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Can you please check if this timeout error issue appears when: - only WPML plugins are activated, as it will tell us if there is an interaction issue with other plugin - theme is set to a WordPress default like Twenty Twenty as it will tell us if there is an interaction issue with your theme As for the "WPML tried to translate this page three times without success." error, would you be willing to provide me with WordPress and FTP credentials so I could investigate the issue directly? https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ I marked your next reply as private so that you can safely add credentials.
November 3, 2025 at 12:05 am #17539288
beataK-8	Hi, I wanted to give you an update regarding the issue I previously reported. The problem with translating those specific pages disappeared on its own after about two days — I didn’t make any changes or take any action to fix it. The pages simply started translating normally again. However, I’ve noticed that WPML still occasionally behaves irregularly in a few ways: Sometimes it loses fragments of previously saved translations. Occasionally, translated pages display with a broken layout. This usually fixes itself after I make another change to the original page and then update the translation again. I’m not sure if these issues are related, but I wanted to let you know in case they point to an underlying problem. Thank you, Regards