<b>Background of the issue: </b>
I am trying to translate a Dutch (NL) article to English and then to French (FR). When translating to English, there is no issue, but translating to French afterwards results in the English slug being used. Translating first to French and then to English works correctly. I also want to know if it's possible to translate the slug immediately when using the Gutenberg sidebar, as currently, everything except the slug is automatically translated. We have selected to translate the slug manually because we create shorter slugs in Dutch.
<b>Symptoms: </b>
When translating a Dutch article to French after English, the slug is incorrectly translated to English. Additionally, the slug is not automatically translated with the rest of the article.
<b>Questions: </b>
Is it possible to translate the slug immediately when using the Gutenberg sidebar?
And create the correct translation (now EN in FR) for the slug?
While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly. There are a few options you can use, in your case maybe the best would be to use a slug from the translated title, which is probably the settings you have now. You can also choose to translate the slug.
Go to WPML → Settings. Scroll to Translated documents options. Under Page URL, choose the Translate option. Click Save.
Directly translated from the title is not what we need. A lot of the titles are quite long and that's why we create a shorter version of the slug (in dutch). We would like that to be directly translated to the other 2 languages. Now we always have a extra step between (and a bug for the french translation).
Thank you for the updates. Sorry for the delay happened because of the weekend.
By default, we have three options in WPML >> Settings >> Translated documents options>>Page URL. The first two options, *Auto-generate from the title (default)* & *Translate (this will include the slug in the translation and not create it automatically from the title)*, will not support your requirement, am I correct?
If so, we have a request. Can you please share a couple of screenshots for a better understanding of the following. This requires further checking, especially *a bug in the French translation*.
We would like that to be directly translated into the other 2 languages. Now we always have an extra step between (and a bug for the French translation).
Thank you for the details. As per the screenshots, the translation is not 100% complete now. So please click on the *Save* button after translating the Slug and then press the *Complete* button on the bottom of the screen. Then make sure you are getting the expected results or not. Refer to the attached image for more details.
The problem is not that the slug is not translating. We know that we have to save it to get the slug translated.
The problem is that the slug is not correctly translated. You can see in the example that the translation of the text is in French via DeepL. The slug however is translated in English. THAT is the bug.
Thank you for the updates. Please upgrade to the latest version of WPML (4.6.15 series) after a full site backup {mandatory} and clear all types of caches.
After that create a simple post or page for testing, then translate it to a secondary language, and ensure the issue exists or not.
--
Thanks!
Bigul
The topic ‘[Closed] Bug when translating slug to FR’ is closed to new replies.
