Slug translation not working despite correct settings

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are experiencing an issue where WPML is not translating page slugs into target languages despite correct settings and fully translated pages. The expected behavior is for slugs to be translated into respective languages, such as /en/book-hotel/ for English, but the actual slug remains as the original, e.g., /en/hotel-buchen/.
Solution:
We recommend increasing the memory limit of your WordPress site. It appears from your WPML debug information that the memory limit is set too low. Please increase it to at least 256MB. This adjustment might help resolve the issue with slug translations not being applied correctly.

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 problems persist, please open a new support ticket.

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: Documentation request

This topic contains 3 replies, has 1 voice.

Last updated by Marcel 3 weeks ago.

Assisted by: Marcel.

Author	Posts
January 18, 2025 at 4:56 pm #16609445
raphaelM-28	Background of the issue: I am experiencing a critical issue with my multilingual WordPress site where WPML has failed to translate page slugs into the target languages, despite correct settings and fully translated pages. The website URL is hidden link. I am using WordPress Version 6.7.1 with the Astra theme and Elementor plugin. Slugs should be translated into respective languages, for example, /book-hotel/ for English and /réserver-hôtel/ for French. .E.g. the original slug in German is /hotel-buchen/. The expected English slug is /en/book-hotel/, but the actual English slug remains /en/hotel-buchen/. This affects all translated pages. In WPML > Settings > URL, it is set to 'Translate (the slug is included in the translation and not automatically created from the title)'. Actions taken include scanning plugins and themes under WPML > Theme and Plugin Localization, clearing WPML cache, resaving permalinks, verifying translations are complete and published in WPML > Translation Management, and trying to access slugs via the Translation Editor and 'Pages' section, but translations are not listed separately. Symptoms: WPML is not translating page slugs into the target languages, despite correct settings and fully translated pages. Questions: Why are the slugs not being translated despite the correct settings in WPML? What additional steps can I take to ensure slugs are translated correctly?
January 21, 2025 at 8:25 am #16616715
George Botsev Supporter Languages: English (English ) Timezone: Europe/Sofia (GMT+02:00)	Hello! The problem may be related to the plugin,theme or custom code that is being used for the "page" that is being used for the booking. Could you please arrange a temporary credentials so either me or one of my colleagues to take a look? I am enabling the private reply for your next reply.
January 22, 2025 at 3:10 pm #16623866
raphaelM-28	Hello, Thank you for your reply. We encountered a whole lot of other issues with the translations, such as buttons that don't link to the correct language version. I found a way to fix it, but it requires translating the pages again and we already spent 200,000+ credits on the initial translation. We are not consulting with an external WPML expert who is confident he can fix all issues. However, he says because of a wp_memory_limit-error, it is possible that we have to translate everything again. Is there any way to receive a discount on the necessary credits? Thanks
January 24, 2025 at 1:13 pm #16631525
Marcel Supporter Languages: English (English ) German (Deutsch ) Timezone: Europe/Madrid (GMT+01:00)	Hi there, Just a quick note to let you know that credits are non-refundable since we’ve already paid the translation engine once they’re used. That said, the content should still be available in the translation memory if you re-translate it. From your WPML debug info, it looks like the memory limit is set too low. Could you try increasing it to at least 256MB? That should help! Best regards, Marcel