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.
