Custom Post Type slug translation leading to 404 error

  • Resolved fderooy

    (@fderooy)


    2 years, 2 months ago

    Hi.

    I’ve been doing much reading regarding the relation between Translatepress and Custom Post Types in WordPress, as I came up to an issue that results in 404 errors whenever I activate de language switcher and enable the translation of my website to a second language (English in this case; Spanish is the original).

    As you can see, when the plugin is activated and the user browses the website in its original language (Spanish), all the links in its main menu categories operate correctly. They lead to the custom post types corresponding to Team Members (Miembros de Equipo, in Spanish) and Services (Servicios, in Spanish), which also have slugs in Spanish. But when you activate the English translation (with the Translatepress switcher in the main nav bar), these navigation menu subcategory links are also translated (from “miembro_equipo” to “team_member”, and from “servicio” to “service”), resulting in a 404 errors. What I see is that it is an issue that only happens with navigation menu items that point to custom post types. The plugin does not do the same with links to pages.

    Any ideas on how to solve it? Thanks in advance.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter fderooy

    (@fderooy)

    By the way: I have pretty permanlinks already configured. Also tried the “Force Language in Custom Links” solution provided in the FAQs section of Translatepress support website. Nothing seems to work.

    Dragos

    (@dragosvrejiu)

    Hello,

    Thank you for getting in touch with us!

    TranslatePress should not present conflicts with CPT’s. Are you using some sort of permalink modifiers?

    E.g. plugins that remove the category base from the URL

    Best regards,

    Thread Starter fderooy

    (@fderooy)

    Hi, thanks for your reply. I’m not using any plugins that remove categories from URL. The only modification to URL’s in the website came through the translation of the theme’s .pot core files. That’s all.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Custom Post Type slug translation leading to 404 error’ is closed to new replies.