404 Errors on Translated English Pages Using TranslatePress (Version 2.8.7)

  • Dear Support Team,

    I am experiencing an issue with TranslatePress (Version 2.8.7) on my website, where all the translated pages in English are returning 404 errors. My site’s default language is Spanish, and everything works fine in that language. However, whenever I attempt to access any English-translated page (for example: https://www.bodegasgongora.com/en/producto/mardeluces-2/), it leads to a 404 page not found error.

    Here are the steps I’ve already taken to troubleshoot the issue:

    1. I have re-saved the permalinks several times.
    2. I have cleared the site cache and even disabled LiteSpeed Cache entirely.
    3. I have checked the .htaccess file and reset it to default settings.
    4. I verified that “Force language in custom links” is enabled in the TranslatePress settings.

    Despite these efforts, the problem persists. It seems to specifically affect the English translations, as the original Spanish pages work without any issues.

    I would appreciate your guidance on resolving this matter. Could this be a known issue with the current version of TranslatePress (Version 2.8.7), or is there another configuration I should check?

    Thank you for your assistance.

    Best regards,
    Mario Suárez
    https://www.bodegasgongora.com

    • This topic was modified 4 months, 4 weeks ago by solidoes.

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

Viewing 16 replies (of 16 total)

  • lila22: This worked for me. Thank you very much. I tried the solution from Translate Press and was trying hours and hours…but nothing….now I can go to bed after many hours….its 02:08 h….its getting tired….

    This was the answer from support:

    Thank you for reaching us!

    To fix issues regarding infinite redirect loops or 404 on pages where the custom post type base slug has a -2 suffix, update TranslatePress plugins to latest versions.
    If you see the admin notice to Run The Update, then please click it. The issue should be resolved.

    If no admin notice to Run the Update, it means that you already performed the database upgrade, and you need to fix the issues manually. Follow these steps:
    1. Open Translation Editor -> String Translation -> Post type base, and search for the post type base where this issue occurred.
    2. Edit translation in each language by removing the -2 suffix if present. There are 2 outcomes:

    3.a. If the translation is not used anywhere else, then no suffix will be added after clicking Save. The pages should work correctly now. No need for further action (ignore the next 3.b. point).

    3.b. However, if the translation you want to save is already taken, then the Translation Editor will automatically ensure slug uniqueness by adding suffixes ( -2, -3, etc.). The pages will now work with the suffixed slugs (no 404s or infinite redirects).
    If you want to get rid of the suffix, then you will need to change the conflicting translation so that it becomes available to use where you want it.

    It’s possible that the translation you want to use is already taken up by an inactive post type base slug. You should be able so see it in the String Translation, Post type base tab. In this case you need to edit it and delete all translations from it.
    If the actual inactive post type base slug is the translation you want to use, then you need to delete that slug from the database. To do this, you need to remove it from the trp_slug_originals table database. You can use a plugin such as WP Data Access to delete the entire row that contains the slug you want to remove.

    • This reply was modified 3 months, 3 weeks ago by trixicom.
Viewing 16 replies (of 16 total)
  • You must be logged in to reply to this topic.

Tags