This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is experiencing an issue where the "Translate automatically" feature in the Advanced Translation Editor (ATE) fails to populate the URL slug field, despite the field being visible and other content translating correctly. The client has enabled "Translate (custom values of slugs)" in WPML settings, made the URL field visible through the "Quick Edit" method, and attempted re-translating from scratch, but the automatic translation engine still does not fill the URL slug field.
Solution:
We explained that when the option "Translate (this will include the slug in the translation and not create it automatically from the title)" is selected, WPML will not automatically translate the slug. Instead, slugs are typically auto-generated from the translated title of the post or page. To have the slugs automatically populated, the client should use the default setting "Auto-generate from title (default)". For more details, please visit Translating Page Slugs documentation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, 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 1 replies, has 0 voices.
Last updated by 2 weeks, 2 days ago.
Assisted by: Lucas Vidal de Andrade.
