Skip Navigation


Resolved in: 4.2.7


Translating a term with the same slug as the original term will automatically add a suffix with the language code. This is because WordPress API does not allow to have more than one occurrence of a slug for a specific taxonomy.

Here’s an example of what we expect:

Currently, a language suffix is automatically added to the translated term =>

A ticket has been created in WordPress Trac to overcome this issue: (feel free to add a comment to this ticket to make it move forward).


As a workaround, you can use the following steps (or watch a screencast of the workaround):

  • create the term first
  • update it with the “quick edit” link
  • change the slug value and click Update {Taxonomy name}

15 Responses to “It's not possible to have the translated term slug identical to the original term slug”

  1. Good that it is logged. Here it is described what the erroneous situation is. Good.

    Could you please also explicitly declare what the required functionality is, as that is not clear here.

    And maybe provide an example with a default language and translation language, where the suffix is automatically added?

  2. When adding an identical term to a post on the post edit screen, the term is not added with a language suffix, but the original term (in another language!) is used.
    The adding of an identical term only works correctly from the term overview admin page.

  3. I’ve found a workaround for this.
    Add the category with the translation service
    After it’s added, go to the language tab in the category overview and use ‘quick edit’, this will allow you to use the same slug.

      • I cant send the screenshot here but this workaround doesnt work for me.

        My step:

        – created a new taxonomy (eng translation) with differente name and NO SLUG
        – SLUG automatically ADDED succesfully with the “-ENG” suffix or a number
        – click on a QUICK EDIT and modify the SLUG at the same name of the other language
        – get an error from WORDPRESS who avoid to rename it because its already used from another taxonomy

      • You miss one step.

        Here its the correct order:

        – WPML > TAXONOMY TRANSLATE : and add the language of the new taxnonomy
        – when the popup jump out COPY THE SAME SLUG from the language source with the copy button
        – moving to the category taxonomy and follow the step showed in the screenshot

        But after, in the result page, i get ZERO RESULT and NO TRANSLATION.

        Seems the TAXONOMY do not catch the database or the original taxonomy (who are now the same)

    • Hi, no this is not added to WPML yet. It’s on the list of our features but I do not have an estimation for when can it be added.