This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is unable to automatically translate the URL slug when using WPML. Despite having automatic translations enabled, the URL field remains empty in the translation editor and defaults to the English slug, which does not meet the client's needs as they often differ from the page title.
Solution:
1. To address the issue of untranslated URL slugs, we recommend following the steps in our guide on translating page slugs. You can find the guide here: Translating Page Slugs.
2. If you prefer the URL slug to auto-translate based on the page title, select the 'Auto-generate from title (default)' option in WPML -> Settings -> Translated documents options -> Page URL.
3. For manual translation of the slug, choose the 'Translate' option in the same settings area. This will allow the slug to appear in the Translation Editor for manual adjustment.
4. If these settings do not resolve the issue, we have also provided a screencast with additional steps that might help. View the screencast here: WPML Slug Translation Screencast.
Please note that the solution provided might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, 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.
This topic contains 6 replies, has 0 voices.
Last updated by 2 months, 2 weeks ago.
Assisted by: Carlos Rojas.