Custom posts slug translation options

This topic contains 7 replies, has 2 voices, and was last updated by  Stiofan O’Connor 9 years, 9 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: , ,

  • Author
    Posts
  • #2456

    eqhes
    Expired Member
    Post count: 40

    Hi,

    I’m using WPML for translating the content. This plugin has got an option for translating posts slugs. If, for example, I try to use different slugs in different languages for Events, I can see that in English (original language) the slug is “events/%gd_taxonomy%”. So I tried to add something like “eventos/%gd_taxonomy%” for the slug in Spanish, but then I get URLs like “eventos/gd_taxonomy/my-content-slug”, which isn’t the desired behaviour.

    The question is: are custom slugs per language supported?

    Thank you in advance for the reply.

    #2469

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    HI eqhes,

    I have never used this feature, i will do some testing and get back to you.

    Thanks,

    Stiofan

    #3692

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Hi eqhes, i have tried to get this to work but i can’t even find where i would translate the slugs, please give me step by step instructions on how to do this.

    Thanks,

    Stiofan

    #3844

    eqhes
    Expired Member
    Post count: 40

    Hi @stiofan,

    Sorry about the delay. You can follow the official WPML documentation: http://wpml.org/documentation/getting-started-guide/translating-page-slugs/

    Regards.

    #3845

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Yeah i had a read of that but i could not get the options to show, it sounds like you have?

    Stiofan

    #3850

    eqhes
    Expired Member
    Post count: 40

    This is how I do this:

    1. Make that custom post type translatable

    a) WPML –> Translation Management –> Multilingual Content Setup –> Custom posts

    b) Check “Translate” for those custom post types you want to translate. For example: “Places”.

    c) “Save”

    2. Enable slug translation for the site

    a) WPML –> Translation Management –> Multilingual Content Setup –> Custom posts slug translation options

    b) Check “Translate custom posts slugs (via WPML String Translation).”

    c) “Save”

    3. Select to use different slugs in different languages

    a) WPML –> Translation Management –> Multilingual Content Setup –> Custom posts

    b) For your preferred custom post type (p.e. “Places”) you can check “Use different slugs in different languages for Places.”

    c) Read the issue with this option on my first missage on this thread.

    #3852

    eqhes
    Expired Member
    Post count: 40

    More information that may be interesting in order to check the issue:

    If on step 3b) I don’t check “Use different slugs in different languages for Places.”, but I go to “WPML –> String Translation” and there I translate the URL slug (looking for “%gd_taxonomy%” gets me the string to translate), then I see the URL getting translated properly in the public side, but the new URL throws a 404 error when accessing to it.

    Hope you can understand me and see what I’m talking about :).

    #9236

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    OK i managed to get it turned on and i can confirm it does not work, it seems to mess with out location url’s also, i think this might be one thing that is not compatible but if you want you can add it as a feature request and if you get enough support we will look into if further. https://wpgeodirectory.com/requests/

    Thanks,

    Stiofan

Viewing 8 posts - 1 through 8 (of 8 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket