Automatic Translation Feature Broken – $$$$

  • I’ve had a premium membership for about four months now. We configured our site to use the Automatic Translations feature via Google Cloud API. This has proven to be extraordinarily expensive due to bugs in the TranslatePress code. We’re looking at close to $1000 USD in API charges for our organization because this plugin is sending duplicate requests over and over and over– several thousand duplicate requests that we’ve logged. We submitted a support request at the tail-end of October, jumped through hoops to get them backups of our site, and then sat through over a month of radio silence without any update on the issue.

    We did finally hear back this morning, and they’ve told us that an update is coming next week that will resolve our issue… We’ll see.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Alex

    (@alexcozmoslabs)

    First of all, we are sorry that you had issues with TranslatePress automatic translation feature.
    From what I remember, your website had a large amount of content, if I’m wrong, right? Also, since you had a lot of additional languages configured on the website, somewhere over 20 languages, high costs are expected.

    About the cumbersome investigating process, this was because there were errors on your website that did not allow us to investigate how fast we wanted. Due to this fact, prior clarifications were needed.

    A fix for your issue will be part, as you said, of this new version of the plugin that will be released this week. Everything should be fine now.
    For any other ambiguities or possible bugs, you can contact us, and we will try to come up with a solution as soon as possible as we do for each of our users.

    Best Regards,

    Thread Starter bourn404

    (@bourn404)

    You’re correct that our website has a lot of content and that we wanted to offer many languages. That’s why we chose a plugin that translates “on the fly” when a page is requested, instead of translating our entire site upfront.

    All of that being the case, that’s still not a great excuse for the duplicate requests that were supposed to be stored in the database. I’m glad to hear that there is a fix available–I would have liked to know much earlier that the problem had been identified and there was a solution in the works. The lack of communication on how the situation was being fixed was a disappointment.

    The other issue that seems to cause extraordinarily high expenses is that when the page is requested in one language (ex. Spanish), your plugin requests translations for all enabled languages — that doesn’t really make a lot of sense. You should only make translation requests for the language that was requested.

    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    Thank you for your detailed feedback.

    Did you download our latest version as it should fix your problem? Let me know how it goes.

    I’ll try to clarify some of the things you’re mentioning.
    We only make translation requests for the language that was requested (so just one language).
    The only exception to this is when entering the Translation Editor.
    When navigating or using the editor, this does not happen. I hope this information helps.
    Also, when search engines try to index the pages, they tend to do it in all languages.

    Once again, I appreciate your detailed feedback and we’ll do our best to avoid situations like this in the future.

    Best Regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Automatic Translation Feature Broken – $$$$’ is closed to new replies.