I added Machine Translation extension to our XWiki instance (16.10.15), and the extension works only partially. Drop-down menu works, therefore translation also works. However, clicking on the Translate button does’t open the modal it should.
Another thing is the remaining characters available statistic is incorrect. E.g. with test API 1,000,000 characters is provided, but the Machine Translation extension shows only half of that, at 500,000 characters.
I’d like to know if the extension is still maintained before procceeding with full implementation and a DeepL subscription.
hello, sounds you’ve found issues in Machine Translation. If those are not known yet, you can report them on MT Jira project. Maybe some developers who maintain this extension can fix it or provide feedback on the issue.
I opened several issues, but looking at it, I don’t think the extension is actively developed anymore. I’d definitely like to know if there are any plans for it or if the project is dead.
From what I’ve seen, the extension isn’t completely abandoned, but it also doesn’t seem to receive much active development these days.
The behavior you’re describing with the Translate button not opening the modal sounds more like a frontend compatibility issue than a translation backend problem, especially since the dropdown translation itself still works. It would probably be worth checking the browser console for JavaScript errors and verifying whether there are any known incompatibilities with XWiki 16.10.x.
As for the remaining character count showing 500,000 instead of 1,000,000, that doesn’t sound expected either. It could be an issue in how the extension interprets the API quota rather than the actual limit on your DeepL account.
If you’re planning to extend the workflow anyway, another option is to move the translation logic outside the extension entirely. Tools like https://latenode.com/products/agent-builder make it fairly straightforward to build an AI-powered workflow that reacts to page updates, calls DeepL or another translation provider, applies custom validation, and pushes the translated content back automatically. That way you’re less dependent on the maintenance status of a single extension.
I’d also be curious whether anyone has tested the latest release against newer XWiki versions, or if this is simply a regression that hasn’t been reported yet.