rannooo

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.

Problem:
The client is unable to see URL slugs in the page translation UI when trying to translate a new page URL slug, despite following the guide on translating page slugs. This issue is inconsistent across different environments and accounts.
Solution:
1. Make a minor edit to the page in the default language and update it. Then, check if the translation shows the URL slug correctly.
2. If the issue persists, create a new test page or post, add a translation, and see if the slug appears in the editor.
3. Clear your site's cache as it might be a caching issue affecting the visibility of translated slugs.
4. If none of the above steps resolve the issue, it could be helpful to test using a different user account to see if the problem persists.
5. For further troubleshooting, especially if the problem occurs only in specific environments, provide temporary access to your site for detailed investigation by the WPML support team.

Please note that the solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket.