A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
I'm not sure what causes the issue, but you could implement your own Translator Provider for use with LanguageManager.
Have a look at this blog post. It has links to both an addon for LanguageManager that uses OpenAI, and even the source code, so you could implement your Translator Provider.
https://www.gulla.net/en/blog/auto-translate-with-openai-gpt-4o-in-optimizely-cms/
Yeah, I'm aware I could write my own provider and attempt to fix the issue myself but I'm thinking this is a bug within the addon that should be addressed?
If this is not the case I'll have no option but to copy the default provider and write my own workaround but this usually adds on technical debt down the road.
Thanks for the suggestion however Tomas!
Hi,
We have a custom language code "en-SE" setup on our site and it seems that when choosing "Auto-translate" it gives an error message in version 5.3.0.
In the previous version "4.0.3" this succeeds without issues.
My best guess is that "en-SE" is not supported by Microsoft translator but I haven't confirmed this.
Edit: The issue seems to be that if a related block/page doesnt have editing enabled for the language code it is not automatically enabled for translation and hence causing an exception to be thrown.
So I have two questions:
Thanks in advance!