Plugin Support
Anca
(@ancavictoria)
Hello @vmajor
The issue you reported shouldn’t have happened – it’s possible the translations weren’t saved in the database or something else triggered the problem you encountered.
The suggestion would be to test on a staging site using the free version of TranslatePress together with Google Translate automatic translation to check if this issue occurs again: https://translatepress.com/docs/automatic-translation/generate-google-api-key/.
You can also try enabling the ‘Log machine translation queries’ option in TranslatePress Settings → Automatic Translation tab.
Please let us know if the issue reappears.
Kind regards,
Anca
Thread Starter
vmajor
(@vmajor)
OK I will try this, however even with Google I got a nasty surprise when all of a sudden my monthly bill shot up to USD 150. I really do not like surprises. How can I instead debug what translatepress is doing – for example what I believe should be happening is:
1. Translatepress checks its database table(s) if a URL has all designated translations and if not it makes a translation call to Google Translate/DeepL or your own AI for a URL
2. Translation is performed and returned to Translatepress which saves the translation to the appropriate database location
I would like you to tell me if there is a debug option for Translatepress where I can check what it is actually doing before I again end up paying surprise translation fees. This becomes particularly pertinent since I am considering the USD 199 subscription and deployment to two sites. I truly do not want to wake up to a USD 1000+ bill.
I am testing it now with debugging… and will disable it in a few hours
One more question, I looked at your documentation briefly but could not see it mentioned, do you provide hooks to call external translation APIs? For example I find translation by an LLM to be indistinguishable from a human translator – allowing for stylistic differences. No machine translation comes even close and we use LLMs for actual business negotiations in several languages now.
I want to be able to place a translation call to an LLM – we can set up the LLM side of things to present the translation request, and output in the format that Translatepress uses.
Thread Starter
vmajor
(@vmajor)
I did some testing and the translations no longer seem to be duplicated, however Translatepress breaks the page layout. Please see here:
https://www.venn-cycling.com/ja/product/venn-18-mth-1k-filament-wound-ultralight-mtb-rim/
and compare to the original layout that needs to be preserved:
https://www.venn-cycling.com/en/product/venn-18-mth-1k-filament-wound-ultralight-mtb-rim/
The layout breaks for all languages I tested.
Thread Starter
vmajor
(@vmajor)
I guess nobody will reply. I will just remove the plugin and look elsewhere.
Plugin Support
Anca
(@ancavictoria)
Hello,
I apologize for the delayed response!
Thank you for the feedback, we’re glad to hear that the translations are no longer duplicated.
You can limit the number of words used for automatic translation either from your API key settings or by adjusting the “Limit machine translation/characters per day” option in the TranslatePress → Automatic Translation tab, in order to stay within your desired usage limit.
TranslatePress checks each string on the page (this is not related to the page slug) and automatically translates any string that doesn’t already have a translation assigned in your local database.
This means that if you modify a string in the default language, its existing translation will be lost, and if automatic translation is enabled, the string will be retranslated automatically.
While we support three automatic translation engines, we currently do not have a hook to call external translation APIs.
Let me know if you have any further questions.
Kind regards,
Anca
