Good approach, with many bugs and useless support

  • TranslatePress is a well-designed plugin for multilingual websites. Conceptually it has many advantages over e.g. WPML.

    However, TranslatePress has a lot of bugs. If you build something more than a simple website, you will quickly run into limitations. In addition, it feels like more bugs are added with every update. For example, TranslatePress is not compatible with WP Rocket (lazyloading, WEBP images etc. fly around your ears) or SEOPress Schema.org schemas are not supported. A professional website is therefore difficult to implement.

    The support for premium users seems to be overstrained. Sometimes you get a quick answer, sometimes you wait for weeks. Usually the support has no solution for problems, but can only say that the problem is already known. Solutions are generally not promised.

    On our email from 17. May 2021, that “URL Slugs Translation” since the named current version are no longer translated and thus essential parts of our website are no longer accessible, we have received no response until today despite multiple reminders. Only a staging environment was requested, which was never used.

    Very sad because the concept of the plugin itself has a lot of potential!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    We apologize for the time you need to wait to get a reply from our team.

    This is uncommon for us but we need to manage the tickets to make every customer happy.

    We try to make our plugin compatible with all the plugins from WordPress and we work on this but we need to have time to solve these fixes to work as expected.

    Also, you have issues that you reported, these issues will arrive at the developer team but will take some time until these issues will be prioritized.

    Once again, we are sorry for all the things that happened!

    Kind Regards,

    Thread Starter devowl.io GmbH

    (@devowl)

    After seven weeks you get back to us by email. You said that you are able to reproduce the bug, but you will not fix it in the near future (no ETA for fixing the bug). The proposed solution is to change all our broken URL and not translate it anymore. By doing this, we would not only harm ourselves severely in terms of SEO, but also hundreds of links would have to be changed on our end, links from affiliate partners would no longer work, and more collateral damage would occur.

    This is pretty sad and not only will we now have to look for an alternative for TranslatePress because it is not usable in our “complex” setup. Unfortunately, we can no longer recommend TranslatePress to our 70,000+ users of our WordPress plugins.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Good approach, with many bugs and useless support’ is closed to new replies.