Home›Support›English Support›[Resolved] Split: Previous translations created with CTE are opening in ATE
[Resolved] Split: Previous translations created with CTE are opening in ATE
This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported that pages previously translated using the Classic Translation Editor (CTE) were unexpectedly redirected to the Advanced Translation Editor (ATE), resulting in the loss of professional translations.
Solution: We discovered that an alteration in the database might have caused this issue. We recommend running the following SQL query to address the problem:
UPDATE `wp_icl_translate_job` SET `editor` = 'wpml' WHERE `editor_job_id` IS NULL;
Before executing this query, ensure you have a full backup of your site and database. If there were structural changes to the content (fields changed, added, or removed), some translations might appear incomplete in the CTE, and you will need to manually complete these translations.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, 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.
To update on the current status
- All prices have been updated and translated with the CTE.
- I updated the editor in wp_icl_translate_job as instructed in reply #16729534.
- The ATE is activated and set it to keep old CTE translations.
- I tested editing the menu page, and translation updates use the CTE👍
- I added Portuguese as a new language.
- I went to All Pages » clicked the + icon to translate in Portuguese. It translated with the ATE to 100% but when I return to All Pages, it shows the cog icon, and under 'translation jobs', it remains 'in progress'.
- I cancelled the job, used the translation dashboard to send it to translate automatically, and that way also gets stuck at 'in progress'.
That ticket (https://wpml.org/forums/topic/how-to-accept-all-ate-translations/) has been closed almost a month ago and can not be reopened, however you can visit that ticket and see if the option is available for you to reopen. Otherwise, you can open a new one, with reference to that ticket, so our support can catch up accordingly.
The issue resolved in there was not in the database but was a problem with your site records in our servers. And it was fixed by our relevant team by hand.
For this very ticket, if you think that CTE vs ATE issue for existing vs new language (i.e. Menukaart page) has been resolved, please feel free to close it.
However, since restoring from backup has resurfaced previous issue, I'll recommend keeping this ticket with you, while that issue is fixed again via the new (or other) ticket. So you can determine that if the editors issue is also back or not (and can continue accordingly).
Since you have been working with me on this, can you please pick it up?
---
PS: this AI rewriting support requests is really bad. It removes most of the background including the links to the other two related tickets. I complaint about this many times before and since it doesn't seem to improve, so I copy my entire message before submitting it, and then paste that back under 'questions' in the AI result. To a certain degree I can understand support uses AI to summarise and improve submissions, but it should also keep the original message with it. Can you please forward this AI support feedback to the relevant people? Thanks.
And if that does not work, do not restore site from backup but let me know (via that ticket), so we can move forward.
IMPORTANT: I'll recommend creating a staging site based on the live site and then try the solution from this ticket, so if issue remains we can continue working on the staging one.
