Skip to content Skip to sidebar

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

Problem:

You are trying to update translations for your WordPress site using WPML but encounter errors. Specifically, for the homepage, you receive the error 'we tried three times but failed. Please contact support'. For other pages, you encounter a fatal WordPress error or an error message.

Solution:

We have created separate tickets to track the issues you are facing with WPML more efficiently. Please follow the workarounds suggested in these tickets:

Additionally, create a new post (a simple one for testing) and check if you can translate it as expected. For already translated pages that are showing errors, try the workaround suggested here: Translation status stuck or displaying an error.

If these solutions do not resolve your issue or seem 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 problem persists, please open a new support ticket.

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: 

This topic contains 0 reply, has 0 voices.

Last updated by Bigul 1 year, 1 month ago.

Assisted by: Bigul.

Author Posts
February 27, 2025 at 3:15 pm

wannesD

Background of the issue:
I am trying to update translations for my WordPress site using WPML, but I encounter errors. I expected to see the translation page.

Symptoms:
I can't translate pages correctly. For the homepage, I get the error 'we tried three times but failed. Please contact support'. For other pages, I encounter a fatal WordPress error or an error message. WPML heeft deze pagina drie keer proberen te vertalen, maar dat is niet gelukt. Om hem te laten repareren, neem contact op met Ondersteuning van WPML.

Questions:
Why am I getting errors when updating translations?
How can I resolve the 'we tried three times but failed' error?

February 27, 2025 at 4:33 pm #16757237

Bigul

Hello,

Please tries the following troubleshooting steps after a full site backup{mandatory}.

1) Go to WPML>>Support page, click on the Troubleshooting link (blue link in the middle of the page)

2) On the Troubleshooting page, please click on the following options of the *Clean up* section. Wait for confirmation of processing after each one.

- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Set language information
- Fix WPML tables collation
- Assign translation status to duplicated content
- Fix terms count
- Fix post type assignment
- Cleanup and optimize string tables
- Synchronize local job ids with ATE jobs
- Synchronize translators and translation managers with ATE

Then make a minor change in the Homepage content in the original language (to refresh the translation settings), and update it. After that, resend it for translation in English and make sure the issue is existing or not.

--
Thanks!

Bigul

March 10, 2025 at 8:03 pm #16798421

wannesD

Hi,

I followed these steps, but unfortunately this did not fix my issue...

March 11, 2025 at 6:43 am #16799479

Bigul

Hello,

Thank you for the updates. Please create a new page or post (a simple one for testing) and check whether you can translate it.

Also, please share the WordPress debug.log (not WPML debug information) with us so we can collect more details on this. Refer to the following pages for instructions

https://wpml.org/documentation/support/debugging-wpml/

https://wordpress.org/documentation/article/debugging-in-wordpress/

To enable WordPress Debug log, open your wp-config.php file of the site root and look for define('WP_DEBUG', false);. Change it to:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
 
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
 
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

The errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check you are getting any errors or warnings related to WPML in the log file.

If you can paste your debug.log to http://pastebin.com/index.php and provide me that link, it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion).

--
Thanks!

Bigul

March 17, 2025 at 7:43 pm #16827091

wannesD

Hi,

I wasn't able to translate the new page...

Pasted the log file here: https://pastebin.com/iuiZVhnV

March 18, 2025 at 7:41 am #16828244

Bigul

Hello,

Thank you for the updates. Just to make sure, have you migrated or changed the URL recently?

Please allow me to create simple posts (as private) for testing.

--
Thanks!

Bigul

March 19, 2025 at 7:50 am #16833573

wannesD

Hi,

I just think that we moved from one server to another...
So the URL did not change, but probably the underlying IP adres did.

March 19, 2025 at 2:01 pm #16835697

Bigul

Hello,

Thank you for the updates. I created a simple post for testing. However, it shows the following error message while translating the post to English or French.

There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

Therefore please allow me to make a duplicator copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the issue without affecting your live site.

--
Thanks!

Bigul

March 19, 2025 at 8:08 pm #16837106
wannesD

Dear,

Thank you for futher investigation, you can do so!
Normally there is a duplicator pro on it.

March 20, 2025 at 3:49 pm #16841040

Bigul

Hello,

Thank you for the permission. I made a copy of the site and debugging the issue locally now, we will get back to you as soon as possible. Please wait.

--
Thanks!

Bigul

March 21, 2025 at 9:08 am #16843328

Bigul

Hello,

I created a couple of new tickets for the easy tracking of the issues you are facing with WPML. It will help us to avoid discussing multiple problems in a single ticket.

So please try the workaround suggested in the following tickets first.

https://wpml.org/forums/topic/uncaught-typeerror-strtr-argument-1-string-must-be-of-type-string-array-given/

https://wpml.org/forums/topic/php-deprecated-creation-of-dynamic-property-wpml_cms_nav_cachecache_to_option-is-deprecated-in/

After that create a new Post (a simple one for testing) and check if you can translate it as expected or not.

For the already translated pages, you can try the workaround suggested here - https://wpml.org/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/

--
Thanks!

Bigul