Skip Navigation

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.

Tagged: 

This topic contains 36 replies, has 3 voices.

Last updated by Marcel 2 months, 1 week ago.

Assisted by: Marcel.

Author Posts
September 3, 2024 at 4:33 pm #16136911

Marcel
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Madrid (GMT+01:00)

Thank you for the information.

Yes, internal links are automatically directed to the translated version. If you want to change this behavior so they appear differently, a manual adjustment in the XML configuration might be necessary, as my colleague mentioned earlier.

However, you've indicated that manual translation of internal links isn't required. The key point is that these links shouldn't even be visible, as they're automatically redirected to the translated version.

It would be helpful if you could provide a few examples to clarify. I look forward to your feedback.

Best regards,
Marcel

September 3, 2024 at 6:17 pm #16137430

ronaldT-5

I already have. See my first post of this ticket. The URL I'm asked to translate in ATE no longer exist, meaning if you enter that URL in a browser, you'll see page not found.

September 4, 2024 at 2:32 pm #16141201

Marcel
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Madrid (GMT+01:00)

Hi there!

So, how is this related to WPML? The reason you're seeing a URL from your default language in our translation editor is that it's connected to the specific page ID. If you checked your database manually, I’m confident you’d see the same thing.

Let me give you an example: if you had titles or meta descriptions from Yoast and then removed the plugin, that old data would still stay in your database. That’s why it could still appear in our WPML editor, as it’s part of the page content.

Hope this helps!

Best regards,
Marcel

September 4, 2024 at 5:49 pm #16142201

ronaldT-5

Can I just ignore it? Or, would it show up in the translated page?

September 5, 2024 at 11:15 am #16144518

Marcel
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Madrid (GMT+01:00)

You can simply ignore or delete that from your database. It shouldn't appear on the translated page if it isn't showing up anywhere on the default language page. It's just a part of the database entry in the original language.

Best regards,
Marcel

September 12, 2024 at 1:08 am #16168446

ronaldT-5

So far so good. I will know soon if ignoring it does the trick. Cleaning the database is too tedious for me.

September 12, 2024 at 6:44 am #16168918

Marcel
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Madrid (GMT+01:00)

Thanks for the info!

Best Regards,
Marcel