Default language message is not displayed when you go to translate it.

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

Problem:
The client was experiencing an issue where the WPML translation editor was not displaying the latest version of the default language content for translation. Despite making updates to the default language content, the translation editor showed an older version. Additionally, there were concerns about Cloudflare and Rest API affecting content translation.
Solution:
We recommended the following steps to resolve the issue:
1. Edit the content in the original language and make a small change.
2. Save the changes.
3. Navigate to WPML -> Translation Management, select the content, and send it for translation.
4. Go to WPML -> Translations and ensure the content is 100% translated.
5. If the issue persisted, we suggested checking the Rest API status and deactivating Cloudflare temporarily to see if it resolved the issue.
6. In cases where the problem continued, deleting the outdated translation and re-translating the page was advised.
7. We also discovered a database error which was fixed by our 2nd tier support team, resolving the translation issues.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, 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.

Tagged: ATE, Exception

This topic contains 2 replies, has 0 voices.

Last updated by Carlos Rojas 6 months ago.

Assisted by: Carlos Rojas.

Author	Posts
January 30, 2025 at 12:48 pm #16651538
nielsO-5	It does not translate... We need to fix this fast, because this page get's a lot of traffic...
January 30, 2025 at 1:13 pm #16651735
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Could you create a staging site with a copy of the production site where we can run all the necessary tests without affecting the live site? I have set your next message private so you can securely share the access credentials to the staging site.
January 30, 2025 at 1:21 pm #16651801
nielsO-5	We don't have a staging environment....
January 30, 2025 at 1:26 pm #16651807
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Could you contact your hosting providers and ask them to create one for you?
January 30, 2025 at 1:27 pm #16651809
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Also, you can use this plugin to create a staging site: https://wordpress.org/plugins/wp-staging/
January 30, 2025 at 1:50 pm #16652122
nielsO-5	hidden link Same password as before.
January 31, 2025 at 10:33 am #16654968
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Thank you for creating the staging site. I have run several tests but the issue persists. I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at the problem and isolate its cause. Please don't modify the staging site and don't modify the credentials, so our 2nd tier specialists can run further tests if necessary. I will get back to you as soon as I get more information. Thank you very much for your patience and understanding!
January 31, 2025 at 12:49 pm #16655557
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi there, Our 2nd tier specialists found an error in the database and it was already solved. I updated the translation to Spanish (hidden link) and the issue disappeared. Could you confirm that the problem is solved?
January 31, 2025 at 2:50 pm #16656302
nielsO-5	You are amazing! It looks like it’s fixed, and everything that was in the queue marked as “complete translation” should have gone through as well. So we don't need to check everything manually. Two more questions: For most blogs, we only add the country code and don’t translate the link. Example: • Original: taggrs.io/set-up-gdpr-tool/ • Translated: taggrs.io/en/set-up-gdpr-tool/ \| taggrs.io/de/set-up-gdpr-tool/ Now, I noticed that the English version of the Enhanced Tracking Script blog was published at: ➡️ hidden link Whereas we actually want it to be taggrs.io/en/enhanced-tracking-script/ (like the default language). Did something change in the system that now automatically publishes the URL as soon as a translation is published? Normally, we can adjust the URL before it goes live. 2️⃣ What was the exact issue with the database? Was it on our end? We’d love to understand what happened. Thanks again!!!!
February 3, 2025 at 9:26 am #16661802
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi there, I'm happy to hear that the issue was solved 🙂 1.- We haven't made any changes to the configuration. You can find the URL translation options in WPML -> Settings -> Translated documents options -> Page URL Also, in WPML -> Settings -> Automatic translation you can see the configuration is set to review the translated content before publishing it. 2.- The issue was with a corrupted key in the database that we fixed. It wasn't an issue you caused. Have an excellent day!