Translations Add-On Release Notes
8.1.1
Released: 30th July 2026
Bug fixes
- Fixed an issue introduced in 8.1.0 where, for documents already part of a translation set, the FTP connector could submit identical files for every target locale in a job, with no indication inside any file of which locale it was actually for. Each target's exported document now correctly carries its own target locale again, while still avoiding the repeated, redundant document export per target that the 8.1.0 change was introduced to fix. (TRANSLATIONS-413))
8.1.0
Released: 30th July 2026
Bug fixes
- Fixed an issue where a single corrupted or incomplete translation job or target could prevent the Translations dashboard from loading. Affected rows are now flagged individually (with details on hover/click) instead of breaking the page. (TRANSLATIONS-411)
- Fixed a concurrency issue where translating multiple documents at the same time could leave translation jobs stuck in an error state due to conflicting repository writes, including cases where documents shared the same untranslated parent folder. (TRANSLATIONS-413)
- Fixed a thread-safety issue in document export that could occasionally produce corrupted translation XML under concurrent load. (TRANSLATIONS-416)
- The FTP connector now generates each document's submission file once per document instead of once per target locale, reducing redundant processing for jobs with multiple target languages. (TRANSLATIONS-413)
- Fixed copy-to-clipboard actions in the dashboard failing silently in browsers or contexts where the Clipboard API is unavailable or blocked. (TRANSLATIONS-411)
Backwards compatibility
- Breaking: JcrTranslationJobPersistenceManager's JCR mapping/binding logic (mapTranslationJob, mapTranslationJobItem, mapTranslationTarget, bindTranslationJobNode, bindTranslationJobItemNode, bindTranslationTargetNode, getTotalSizeForTranslationNodes) has been extracted into internal helper classes and removed from this class. Any custom subclass overriding these methods to customize job/target JCR mapping will fail to compile and must be revisited - there is currently no public extension point for this customization. getTranslationJobById(String, Session) also no longer declares throws RepositoryException; overrides declaring that checked exception will likewise fail to compile.
- The translation job dispatch thread pool is now bounded to 5 concurrent threads by default (previously unbounded). Restore higher concurrency via the new translation.threadpool.size module configuration property if needed.
- For the FTP connector, re-translating an already-translated document no longer embeds a per-file targetLocale property in the submitted XML (a single export is now reused across all target locales). Confirm no external translation-vendor tooling depends on that field.
8.0.1
Released: 25th March 2026
CMS 16.7+ compatibility release.
TRANSLATIONS-409
8.0.0
Released: 19th February 2026
This major version has been released due to a change in behaviour in the underlying library (exim), which changes how nodes are evaluated. It includes performance improvements and the ability to detect node types during evaluation to ensure the translations add-on updates the correct node. This is particularly useful in instances where compound nodes are used and the fields are re-orderable or can contain more or fewer nodes.
We do, however, recommend that if the target translation is different in structure or content from the source document, then it should be created as a different document, as the translations add-on is designed to translate whole documents.
As per the release notes below, you must update to the versions mentioned if explicitly importing the listed dependencies otherwise you will see some discrepencies in behaviour.
Improvement:
- Added the ability to translate nested compound types and overwrite the target document, which will most commonly be used for compounds that have the ability to re-order/add items.
- Updated exim library to 7.0.0 (If explicitly imported, you must update the exim library to this version or above to ensure the best compatibility with 8.x)
- Updated pojo-bind library to 4.0.0 (If explicitly imported, you must update the pojo-bind library to this version or above to ensure the best compatibility with 8.x)
7.x
See here for the release notes for versions 7.x on Bloomreach Experience Manager 16.
6.x
See here for the release notes for versions 6.x on Bloomreach Experience Manager 15.
5.x
See here for the release notes for versions 5.x on Bloomreach Experience Manager 14.
4.x
See here for the release notes for versions 4.x on Bloomreach Experience Manager 13.
3.x
See here for the release notes for versions 3.x on Bloomreach Experience Manager 12.
2.x
See here for the release notes for versions 2.x on Bloomreach Experience Manager 11.