• TranslatePress is causing many of of my post slugs for my default language (English) to change by adding a number suffix ( such as -2, -3-,-4, or -2, -2-2, -2-2-2 etc) from the original post slug.
    E.g.: site.com/slug-post get redirected to site.com/slug-post-2, and after a fays days to site.com/slug-post-2-2, and then after a few more days to site.com/slug-post-2-2-2 automatically. This causes an endless loop of ever creating new post slugs for the same post, and for anyone who knows SEO basics, this is a HUGE issue.
    I then tried to change manually the Englush slug to the original slug and this caused the post slug now to change from the ‘site.com/slug-post-2-2-2’ structure to ‘site.com/slug-post-3’ instead of changing back to site.com/slug-post
    I was trying to find what’s going on with those slugs by reviewing phpMyAdmin, and noticed that this happens because some of the secondary translated languages occupy/replace the original default language slug. For example on the wp_postmeta table the slug wp_postmeta5165_trp_automatically_translated_slug_es_ES replaced the guid of my original post.
    I tried to change then the guid of this slug to another so it doesn’t occupy the original post slug, and then changed again the default language slug to its original form, but this still did not resolve this issue since it create just a new numerical sufix. ( ‘site.com/slug-post-4’
    Why is this critical bug happening and how can it be resolved immediately?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Anca

    (@ancavictoria)

    Hello,

    I apologize for the confusion this situation has caused. We have experienced some problems with the latest updates concerning refactor slug translation. Due to this, we’ve decided to roll back to the previous versions temporarily.

    Therefore, you should continue to use  TranslatePress-Multilingual 2.8.3 and TranslatePress-Business 1.4.1 / TranslatePress-Developer 1.4.1 / TranslatePress-Personal 1.2.8 versions until we address these problems with a new plugin update. Please, open a ticket on our website in order to send you the previous version of the pro plugin.

    I understand the inconvenience this issue has caused, and we are sorry for the situation. At TranslatePress, we strive to make our products as reliable as possible, but it’s possible that some issues might go undiscovered before rolling out updates. We are learning from this incident and working hard to rectify the problem.

    Thank you for your patience and understanding. We hope you continue to place your trust in our product.

    If you are already using these versions and the problem still persists, please let us know.

    Kind Regards,

    Anca

    Thread Starter sociobrightwp

    (@sociobrightwp)

    Thank you Anca, the issues are now resolved. I appreciate your quick response.

    @sociobrightwp

    I just came across your topic and I currently have the same problem. It’s hell for SEO.
    May I ask how you solved the problem please?
    I find it incredible that such a bug hasn’t been solved yet. It impacts SEO in an incredible way.
    Currently, every time an article is modified, it creates a new url.
    It’s a very, very big problem

    it would be really great if you could tell me how you solved it.
    Many thanks in advance

    • This reply was modified 1 month, 3 weeks ago by mrxpookie.
    Thread Starter sociobrightwp

    (@sociobrightwp)

    Hi Anca, several months have passed and this issue is still creating problems for my website: Google Search Console is still reporting thousands of 404 despite that now I deleted the TranslatePress plugin, and moreover whenever my WordPress pages update there are still language specific versions being updated which cause errors. I have asked for help to resolve those issues numerous times and I have recieved no resolution yet. Owill take legal action if TranslatePress will not help me resolve those issues immediately.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.