Reference to our discussion in the other ticket, I've created this new ticket for that CTE translations issue.
I've escalated the matter to our 2nd tier team for further investigation. Please keep fresh and daily backups of the site, until this issue is resolved.
Just adding a note to this, because due to the other issue the menu page in the local language was updated, so now all languages of that page have been retranslated with the ATE.
These languages were translated by a professional translation agency, so WPML uses the Classic Translation editor for this.
- Chinese (Simplified)
- Dutch (default)
- English
- French
- German
- Italian
- Russian
- Spanish
These languages are new and have been translated by the ATE.
- Arabic
- Japanese
- Korean
- Portuguese (Portugal)
The WPML setting is to use the CTE for old translations and the ATE for new translations. However, the pages with old translations now also lead to the ATE, meaning I it has lost the old professional translations.
» I need to get the professional translations back urgently !!!
Hello, still no reply nor solution. What is taking so ling? I am getting pretty fed up with the time it takes to fix all these WPML issues for this website.
Our team investigated the package and found that something (or somehow) altered some of the jobs from the expected entry to one rather unexpected.
A potential workaround could be to run the following query, to fix it:
UPDATE `wp_icl_translate_job` SET
`editor` = 'wpml'
WHERE `editor_job_id` IS NULL;
Please also note that if there was structure change (i.e. new changes made in the content, fields changed, added/removed) - some things won't be translated in CTE as well. In this case, you may see some of these as incomplete translations, which you 'll need to fill in and complete.
Please take full backup of site and database before proceeding with the above mentioned workaround. And dully confirm that you've the latest backup available.
Please let me know if you need help running that query in the database. In this case, please also confirm about the latest backup.
Hi, unfortunately that didn't permanently fix the problem.
- I did run the query
- Then I could open the translations again with the CTA, but some translations were missing. I accepted for further testing.
- Then I made a change to the source (Dutch menu)
- Then I tried to edit the English translation, and it opened the ATE again.
So running the query gave a temporary fix, but after editing the source, it keeps going to the ATE again, while the setting is to keep the CTA for existing content.
--
After all that I wanted to start from scratch so
- I restored a backup from 26 January from before this mess started.
- I ensured all translations of all pages use the CTA
- I changed the setting to use the ATE for new translation with "Publish and mark for review", and keep the CTA for existing translations.
- I made a change to a source page
- Verified that the translations used the CTE » looks good
- I added Portuguese as a new language.
PROBLEM 1
- Portuguese is translated but not published.I checked translations management, and there it shows as in Progress, but there is no way to get it published
PROBLEM 2
In translation management, the Chinese reservation page had a green check mark showing it was translated with the ATE while this was originally translated with the CTA. I went to edit the translation and it indeed sent me to the ATE.
PROBLEM 3 (new)
Translation Management for the 'Privacyverklaring' says that the item needs to be updated for all languages except English. This is incorrect. The problem here is that:
- Dutch was translated to English with the CTA
- All other languages were translated with the CTA as copies of English
- Looks like the ATE doesn't see that
I created a new duplicator package, so if you give me a private reply box I can give you the download link. I also have a database backup from before I switched to the ATE, so that might be useful for you too.
I think things are now mixed up, initially if that query didn't resolve the issue, we can work further on that.
But you've restored the backup leading to the problems fixed in the other ticket which our team has fixed and closed the matter. In that ticket the problem was about site not linking properly, causing these problems (incomplete or stuck translations).
Unfortunately we can not keep mixing the issues in one ticket, as per our support policy, that's why we split into separate tickets.
So, if we fix that linking problem again, the CTE issue 'll return and we'll be at the same point we're now.
At this moment, I 'll recommend restoring the site to the point where you ran that query and it fixed the issue temporarily, so I can then provide the details to the team to look into it further - continuing to resolve the CTE problem
If you want to start over, then please open a separate ticket and we can try again fixing those site-linking issues first and then return to this one.
Sorry, maybe it wasn't a smart move to restore a backup to that point after all. The thing is that during the past 3 weeks various people have been working on fixes, and when one issue was fixed the next one popped up. Technically it's probably different issues for you, but to me, it's all the same: using the ATE for new translations and the CTE for existing translations doesn't work as it should.
Because there have been several switches between CTE and ATE, I lost track and I got worried everything was messed up even more so than how it was at the start. In the mean time the customer also told me they will need me to change all their menu prices this week and I can't deal with content changes when there are still translation issues.
At the moment the site is back at CTE, I fixed the database collation issue, I reconnected the plugin with a new key and I ran the database update query. Once the customer has sent me their new prices I will update them in all current languages with the CTE, and after that I'll see what happens when I switch to the ATE for new translations and when I add a new language. Then we'll take it from there.
