Translations Add-On Release Notes
Info: Bloomreach provides Enterprise support for this feature to Bloomreach Experience customers. The release cycle for this add-on may differ from the core product release cycle.
This feature requires an additional license. Contact your account manager or sales representative for details.
9.x
For release notes for versions 9.x on brXM 17, see Translations Add-On Release Notes 9.x.
8.1.2
Release date: 10 August 2026
Improvements
-
The add-on now detects folder name conflicts during translation. If the translated folder structure would overlap with an existing, unlinked folder of the same name, the system raises a specific
FolderNameConflictExceptioninstead of failing without explanation. -
The ChatGPT and Star connectors now report a specific error key (
SENDING_FAILED) on translation targets when submission fails, instead of using a genericERRORstatus. -
A new "Error details" modal is available for locale- or target-level translation errors. Access it from the dashboard row actions. The modal displays the error type and message, job item and document IDs, and connector-specific error keys. Additional features include:
-
A "View document" action to navigate directly to the source document.
-
A link to the conflicting folder in the CMS content perspective when a folder name conflict occurs. This link works even if the CMS is behind a reverse proxy that rewrites its externally visible path prefix.
-
A fallback path ensures that a rendering crash for a target's row still displays in this modal, rather than failing separately.
-
8.1.1
Release date: 30 July 2026
Bug fixes
- Resolved an issue introduced in 8.1.0 where, for documents already included in a translation set, the FTP connector could submit identical files for every target locale in a job, without indicating the intended locale in any file. Each target's exported document now correctly includes its target locale, while still avoiding redundant document exports per target as intended in 8.1.0. (TRANSLATIONS-413)
8.1.0
Release date: 30 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 available on hover or click, instead of breaking the entire page. (TRANSLATIONS-411)
-
Resolved a concurrency issue where translating multiple documents simultaneously could leave translation jobs in an error state due to conflicting repository writes, including cases where documents shared the same untranslated parent folder. (TRANSLATIONS-413)
-
Addressed 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. This reduces redundant processing for jobs with multiple target languages. (TRANSLATIONS-413)
-
Fixed copy-to-clipboard actions in the dashboard that previously failed silently in browsers or contexts where the Clipboard API is unavailable or blocked. (TRANSLATIONS-411)
Backwards compatibility
-
Breaking change: The
JcrTranslationJobPersistenceManager's JCR mapping and binding logic (mapTranslationJob,mapTranslationJobItem,mapTranslationTarget,bindTranslationJobNode,bindTranslationJobItemNode,bindTranslationTargetNode,getTotalSizeForTranslationNodes) has been moved to internal helper classes and removed from this class. Any custom subclass that overrides these methods for job or target JCR mapping will no longer compile and must be updated. There is currently no public extension point for this customization. Additionally,getTranslationJobById(String, Session)no longer declaresthrows RepositoryException; overrides that declare this checked exception will also fail to compile. -
The translation job dispatch thread pool is now limited to 5 concurrent threads by default (previously unbounded). To increase concurrency, set the
translation.threadpool.sizemodule configuration property. -
For the FTP connector, re-translating an already-translated document no longer embeds a per-file
targetLocaleproperty in the submitted XML. A single export is now reused across all target locales. Ensure that external translation vendor tooling does not depend on this field.
8.0.1
Release date: 25 March 2026
This release provides compatibility with CMS 16.7+.
TRANSLATIONS-409
8.0.0
Release date: 19 February 2026
This major version addresses a change in behavior in the underlying exim library, which now evaluates nodes differently. The update includes performance improvements and the ability to detect node types during evaluation, ensuring the translations add-on updates the correct node. This is especially relevant when using compound nodes with re-orderable fields or variable node counts.
If the structure or content of the target translation differs from the source document, create a separate document. The translations add-on is designed to translate entire documents.
You must update to the specified library versions below if you explicitly import these dependencies. Failure to do so may result in inconsistent behavior.
Improvements
-
Added support for translating nested compound types and overwriting the target document. This is most relevant for compounds that allow reordering or adding items.
-
Updated the exim library to version 7.0.0. If you explicitly import this library, update to version 7.0.0 or later for compatibility with 8.x.
-
Updated the pojo-bind library to version 4.0.0. If you explicitly import this library, update to version 4.0.0 or later for compatibility with 8.x.
7.x
See the release notes for versions 7.x for brXM 16.
6.x
See the release notes for versions 6.x for brXM 15.
5.x
See the release notes for versions 5.x for brXM 14.
4.x
See the release notes for versions 4.x for brXM 13.
3.x
See the release notes for versions 3.x for brXM 12.
2.x
See the release notes for versions 2.x for brXM 11.