[Resolved] "WPML didn't manage to translate this page."
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues where you cannot edit translations on your site and receive errors like 'WPML didn't manage to translate this page' or 'WPML tried to translate 3 times but failed', it might be due to server communication problems, especially after a site migration. Solution: First, check your server's ability to communicate with WPML's services. Ask your hosting provider to ensure that domains such as wpml.org, cdn.wpml.org, api.wpml.org, api.toolset.com, and cloudfront.net are not blocked and are whitelisted. For more details, refer to our guide: https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/ If the problem persists, try re-registering your site with a new WPML site key by following these steps: 1. Remove your current site key from your account on wpml.org. 2. In your WordPress dashboard, go to Plugins → Add New → Commercial tab and click 'Unregister WPML from this site'. 3. Once the page reloads, click 'Register WPML'. When prompted for a key, click 'Get a key for this site'. 4. Complete the site key wizard in your WPML account, setting the site type to Production. 5. Copy the new key and paste it into the Commercial tab to register the site again. If these steps do not resolve the issue, consider asking your hosting provider to temporarily disable the firewall for testing, or test the site on another hosting environment.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. 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 our 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.
Unfortunately, even after registering again the key, the problem is still here, and still on only 1 page, the same.
The request to our hosting provider is still ongoing, and the ticket was escalated to the next support level.
I will send them the link to the forum thread you mention, and see if that helps them.
In the meantime, is there anything I can do on my side to try and fix this ?
I would still recommend testing this on an alternative hosting environment to see whether the issue occurs there as well. This can help determine if the problem is related to the current hosting configuration.
Our hosting provider has deactivated temporarily the ModSecurity (firewall), so all outwards connections should be authorized. But the problem was not solved.
I can't reproduce the error
"AM ATE Server Communication Unable to authenticate".
I just have several
"Job resent to ATE 361 0 {"retry_count":1}"
I will end up deleting the page and recreate it, but what if this kind of error pops up again ?
If it’s easy to recreate, please test this by creating the page again from scratch and checking the results. Please avoid simply duplicating the existing page.
Let me know how it goes. If the same issue still occurs, I will check further with my team to see if there is anything else we can do.
Sorry for the delay of this response.
It seems that creating a new page, translating it again didn't work : the problem is back, this time on the new page. I was able to translate to one language, but not to others.
A coworker (who knows more than me in terms of hosting) suspects a ModSecurity blocking on the server, that would interfere with certain API requests with WPML servers, cuasing intermitten errors. I understand absolutely nothing about that.
I will continue my long (and painful) conversation with my hosting provider's support, who remains adamant about the problem not being related to the server configuration.
Thank you very much for your help and the time you spent on this, I really appreciate it.
I created a local staging for my website, and after a lot of testing, I was finally able to reproduce the problem.
So I feel a bit bad for fighting against my hosting provider, and as it was a very specific sequence of events on my part, I understand why you could not reproduce it on your own local copy of the website.
In case this can help somenone in the future, here is how I reproduced the issue:
* I created a new WP page
* I used the Elementor editor to add a bit of text
* I published the page
* I translated it using WPML ATE
* In the list of pages on WordPress, I used the quick edit function to change the slug
* I tried to edit the translation > the problem appeared.
A couple of notes on this problem:
* I was not able to solve it using troubleshooting recommendations (emptying WPML cache, removing ghost entries, etc.)
* I couldn't solve it by duplicating the page using the EA Duplicator plugin
After a couple of other tests, I could not reproduce this with the native WP editor, so I'm guessing Elementor has an importance in the process.
Having identified the cause of the problem, I could create another page, and take care of not messing with the slug in WP quick edit.
Thank you again for your patience, and have a great day!
Thank you for sharing all the details. I’m a bit surprised that the issue occurred in this way. You did a great job of identifying the sequence.
I’ll use the steps you provided to try to reproduce the issue in a local environment and, if confirmed, report it to our team to see whether we can prevent it in the future.
