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!
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.
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.
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.
