This thread is resolved. Here is a description of the problem and solution.
Problem: You are seeing obsolete URLs in the WPML translation editor, which include URLs that should not be up for translation and some that contain two slugs or non-existent URLs. Solution: The issue arises because these URLs are still associated with specific page IDs in your database, even if they are no longer active or relevant. This can happen if data from previously used plugins (like Yoast) remains in your database even after the plugin is removed. To resolve this, we recommend checking your database for any residual data linked to these page IDs and removing them if they are no longer needed. This cleanup will help ensure that only relevant and current URLs appear in the WPML editor.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
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.
On this reply (the private message) you gave me access to STAGING21 and told me to use that one, can you please confirm which staging site should I use?
It just happened to me again. I changed a text anchor link URL with another one, then went straight to the ATE. Then, I discovered the previous URL is still there. I presume if I had made another small change on the page, it might have helped.
So, that is something you could easily replicate on your side. No need to use my site, in my opinion.
Just so you know, within the new ATE, the obsolete URL's are not clickable, therefore not translatable.
The 2nd tier support team came back with an update related to your issue and they said links like this one:hidden link; are internal links and are made to be automatically translated by WPML and not appearing in ATE. This happens as per ATE design/functionalities.
In case there is a specific reason to translate those links manually it is necessary to use a custom wpml-config.xml.
my name is Marcel, and I'll be handling your ticket from here.
Could you please clarify whether you need to manually update the links? It appears that modifying the XML may be necessary, though you mentioned you're already aware of that. If you could provide more details on what you're specifically looking for, perhaps with an example, it would help us better understand your requirements.