I guess by not checking the "Use also for old translations created with the classic editor" checkbox, the translations made with the legacy translation editor should still be editable (via this legacy editor), but even on these cases, the translations are loaded trough the new advanced editor (e.ate.wpml.org).
Older posts date back to 2021, when I think there wasn't an advanced editor available.
I’ve taken and deployed a copy of your website, but I’m having trouble reproducing the issue you described.
For example, I checked Project > Protocol abordatge ..., and when I click that post, it opens correctly in the ATE editor and is fully translated there, which mean they used ATE editor and where translated there.
So I’m not sure which posts you’re referring to when you say they were created in the CTE (legacy) editor but now open in the ATE (new) editor with empty translations. Could you please share a few examples?
apologies for the late reply, I was'n subscribed to get notifications for this thread.
Keep in mind that I made some tests and re-translated some projects. Here you have some examples with issues:
1) VI Pla Estratègic de Gènere de les Illes Balears
Te ate shows empty translations (most fields) but the project is correctly translated on the front-end: hidden link
2) Protocol d’abordatge de les violències masclistes per l’Ajuntament de Barbens
Te ate mainly shows flagged for later strings, most of them still in catalan (not in spanish as they should be). The front is working correctly as well, telling us that the project had been correctly translated in the past: hidden link
To avoid confusion, be aware of the full project names, as some of them repeat the same first words, for example "protocol abordatge".
Let me know wether this helps or you need further details.
Since these translations were originally created using the Classic Translation Editor (CTE), they should not open in the Advanced Translation Editor (ATE) at all, so any behavior observed after that point is irrelevant.
I have escalated this case and shared it with our second-tier support team. Let’s wait for their response. Hopefully, we’ll be able to reactivate the Classic Translation Editor, so your translations will be available there again.
We’ve reviewed the translation history for this post and would like to clarify why the Advanced Translation Editor (ATE) is opening, even though it’s not currently enabled for older translations in your settings.
Although the option “Use also for old translations created with the Classic Translation Editor” is currently disabled, our investigation shows that this post was previously opened and edited using ATE. In total, there were several translation attempts made with ATE, and some content was translated during those attempts.
When a translation job has already been created with ATE, it is marked accordingly in the system. As a result, that specific translation will continue to open in ATE regardless of the current global setting for older translations.
This situation can occur if, at some point in the past:
- The option to use ATE for older translations was enabled
This action created an ATE version of the translation, which remains linked to the post even after the setting was later disabled
If you plan to continue working with the Classic Translation Editor, we recommend continuing to set to use CTE for translation for now. We’re also checking whether it’s possible to switch the editor for this specific post back to CTE at a datatabse level.
Additionally, could you please confirm whether these translations were imported into the site, or if they were created directly on this installation? This will help us advise you more accurately.
We’ve updated the translation editor for this specific post on hidden link so that it now uses the **Classic Translation Editor (CTE)** instead of the Advanced Translation Editor (ATE).
From now on, when you update the translation for this post, ATE should no longer open.
To confirm everything is working as expected, please:
1. Make a small change in the original (Catalan) content.
2. Then try updating the translation again.
You should now see the **Classic Translation Editor**.
Additionally, if you prefer to continue using CTE for previously created translations, please make sure that the option **“Use also for old translations created with the Classic Translation Editor”** remains **unchecked** in **WPML → Settings**. Enabling this option may cause older translations to open in ATE again.
If it works fine and you prefer this for some other posts also, please let us know and we can try to make the same change.
