I would like to keep the slugs in English everywhere. Can you help me set it correctly? Right now, the slugs are sent to crowdin for translation and, despite our instruction to just duplicate them, sometimes the translators translate them. I tried the setting "Copy from original language if translation language uses encoded URLs", but it was sent to translation as we use both encoded and non encoded translation languages (korean, french, zh-cn, japanese). So, after reading this (https://wpml.org/forums/topic/i-wish-all-the-language-slugs-to-be-same-as-default-eng-slug/) I have now set to "Translate (this will include the slug in the translation and not create it automatically from the title)", which does send it to crowdin.
1. Translate (this will include the slug in the translation and not create it automatically from the title)
2. Copy from original language if translation language uses encoded URLs
I really miss a third option:
3. Copy from original language
Welcome to the WPML support forum. My name is Nicolas and I will be happy to help you today.
Unfortunately we don't have that option. The results you got from your search are on point:
- "Copy from original language if translation language uses encoded URLs" will only work with encoded URLs which is not the case for some of your languages (for example FR).
- "Translate" is the alternative solution we give but in that case your translators must copy it from the original (which can lead to human errors).
The only thing I can offer you that this point is to create a feature request that will be reviewed by our devs. I can't guarantee that it will be implemented or give you an ETA.
Please let me know if I should go ahead with the request.
I may have spoken too fast. I think I found a hack: we have an option to encode urls!
1. As always, make a backup first
2. Go to "WPML > Languages" then click on "Edit Languages"
3. On that screen you can set the option "Encode URLs" to YES for all languages (except the original)
4. Make sure you've selected "Copy from original language if translation language uses encoded URLs"
5. Send a new page to translation as a test.
6. For already translated pages you need to make a small edit on the original page (like adding a space in the title) and resave it. Then enter the translation and resave the translation.
I hope it give you the solution you were looking for.
Thank you for clarifying this for me.
I will try the proposed hack on my development environment and experiment.
Regarding the feature request, I would like to, indeed, feature this option as it brings clarity and fills a business need (this project is our company website - this slug option is what is being recommended for historic reasons by our external SEO consulting agency). We do plan to move to a localized urls slugs in the future but we need to go in gradual steps: this step is about moving the existing website to WordPress without doing any public visible changes. changing the urls structure would mean a lot of extra work, and so, additional resources.
