Home›Support›English Support›[Escalated to WPML Developers team] Prevent WPML from Translating Post and Taxonomy Slugs
[Escalated to WPML Developers team] Prevent WPML from Translating Post and Taxonomy Slugs
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.
Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.
I'm adding Arabic as a new language to my website using WPML, but I’ve noticed that when I translate taxonomies, their slugs are automatically translated into Arabic, and /ar/ is added to the URL. When I add pages for exemple I don't have this issue
For example:
Original (French): hidden link
Translated (Arabic): hidden link
I want to keep the original slug structure and prevent WPML from translating post and taxonomy slugs. Ideally, the Arabic version should retain only the /ar/ prefix while keeping the original post or category name for example: hidden link
How can I achieve this?
Symptoms:
The slugs of taxonomies are automatically translated into Arabic when using WPML.
Questions:
How can I prevent WPML from translating taxonomy slugs while adding a new language?
Is there a way to keep the original slug structure in the translated version?
Our second-tier supporter explained that it was not designed to have the option 'Copy from original language if translation language uses encoded URLs' for taxonomies (categories.) It only works for posts and pages. However, our second-tier supporter submitted this as a feature request. Our developers will consider adding this in future versions of WPML. However, I can promise it will be added. It is up to our developers to decide. If our developers choose to add this new feature, we will update you here.
We also have a known issue where having the same slug for a taxonomy term is impossible. This is actually a WordPress limitation. We explain it in the following link.
