Problem: You are trying to have slugs translated automatically using WPML, but the slugs are not consistently translated. Sometimes, despite using the automatic translation feature, the slug remains in English. Solution: We recommend checking your WPML settings. Specifically, ensure that under WPML → Settings → Translated documents options, the option “Auto-generate from title (default)” is selected. This setting automatically generates the slug from the translated title when you use automatic translation. If you are currently using the “Translate” option, it requires manual translation of the slug in the Advanced Translation Editor and will not automatically translate the slug. For a detailed guide on how to set this up, please visit Translating Page/Post URL Slugs.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are developing a site with a custom post type (CPT) and a taxonomy set as non-translatable. You've noticed that when you update the English post with some terms, the translations do not update with the terms from the English post. You are unsure of the pattern or timing of these updates. Solution: We recommend not expecting WPML to synchronize non-translatable taxonomies between translations, as they are designated as non-translatable. If you need the taxonomy terms to appear or sync with the translations, consider changing their status to translatable. This adjustment will allow them to sync automatically when you update the original post. For more details on how to set taxonomies to be translatable and synchronize them, please visit our documentation:
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client has a custom taxonomy set as not translatable, yet translations are being added to the terms. The taxonomy consists of country codes as slugs, and the client is concerned that making the taxonomy translatable will alter the slugs (e.g., 'GR' becoming 'GR-DE'), which could affect the site's geolocation functionality. Solution: We advised that while WordPress does not allow duplicate slugs for taxonomy terms by default, WPML can manage this issue. When translating a taxonomy term, the client can edit the term to remove the language prefix, thus keeping the original slug intact (e.g., changing 'GR-DE' back to 'GR'). Additionally, if the client wants the terms to be synced across translations with the English post as the source, this functionality should already be in place.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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 at WPML support forum.
