Page tree
Skip to end of metadata
Go to start of metadata

The Content Translation Support Extended (CTSX) module enables you to translate content automatically. This module comes with several apps which are used to manage the translation tasks.


Maven is the easiest way to install the modules. Add the following dependencies to your bundle:

<!-- API and base classes that support the CTSX Translator modules. -->

NOTE: Installation on jdk 11 needs extra dependencies, visit the warnings section of this document.

Translation service

In addition to the core and apps modules, one (or more) of the translator modules should be installed:


3.1.1Magnolia 6.2
3.0.5Magnolia 6.1
2.9.4Magnolia 5.7
2.9.4Magnolia 5.6


Content Translation Support Extended (CTSX) enables you to translate content automatically over a translation provider ensuring a more accurate translation. Translation is done from a base language, typically English, to a target language. The base language should exist as content within your website or content app as properties. The target languages should be configured in your site definition. See Enabling multilanguage content for more information.




Defines the field types that are going to be translated, default is text and richText, possible values are composite and multiValue.



The class that finds the properties to be translated, default value info.magnolia.translation.ext.core.translation.finder.AdaptivePropertiesToTranslateFinder, finds the properties by processing the fields in the dialogs.



  • From version 3.0.3

Defines the source languages, the default is the value in the site definition fallbackLanguage, you can define as many languages as your 3rd party translator supports, the dialog will display just the ones supported in the current site definition.

Translation providers

There are three translation providers to choose from: Google, Microsoft Translator and To make use of the translation functionality, a user account is required for the chosen provider.

A translator module connects Magnolia to translation services. The behavior of the service depends on the translation service selected.


Returns directly the translated result for each translation request.

  • Google
  • Microsoft

Not support to translate the languages which contain the country information yet.

  • Translate from English to Germany (Supported)
  • Translate from English, United Kingdom to Germany, Switzerland (Not supported yet)

Does not return the translated result for each translation request. A second request is required to get the translated result.


Support to translate the languages which contain the country information.

  • Add the country information for locales in the site definition (e.g: country=GB for English, United Kingdom)
  • Mix the country information with fallbackLocale (or defaultLocale) property for setting the source language in the site definition (e.g: fallbackLocale=en_GB for English, United Kingdom)

Each translator has a common set of properties.



When true the content review process (workflow) is bypassed.



Definition class for the translator to be used.



The display name of the configuration in Magnolia.



Set the translator to be the default.



Enables or disable the configuration with true or false.



Implementation class for the translation service.

Translation Extend app

The module comes with the Translation Extend app which can be found under the tools menu of the appluancher. This app extends the functionality of Content Translation in the sense that translations can now automatized. It would still be possible to export those automatized translations from the Content Translation app after receiving them. 

Translation subapps

The app is made up of several subapps for managing translation files and submissions.

  • Batches: In the Batches subapp users can
    • Add a new or edit an existing batch.
    • Submit a batch for translation.
    • Get the history of the batch.
    • Cancel a batch submission.
    • Reload an exiting batch.
  • Histories: Allows for viewing and managing the batch histories.
  • Queues: Allows for managing the translation submission.
  • Comparison: Allows you to compare between original value and translated value before importing or reject.

Translation status

Once a batch is created it has a status. The status is visible from Batches subapp.

OPENCreated and not yet submitted
PROCESSINGProcessing and waiting to be submitted or imported
SUBMITTEDSubmitted to the translation provider
TRANSLATEDTranslated by the translation provider and was received
APPROVEDThe translation has been approved by the reviewer
IMPORTEDThe content was imported
REJECTEDThe translation has been rejected by the reviewer
REOPENEDReopened after going through review step
EMPTYThe resource has no i18n items


This module provides a workflow for users to review and approve translated content. If the setting autoTranslationAllowed is true then the content is imported directly without a review step. Otherwise the content review workflow process is started.

The workflow is identical in nature to the 4-eye content approval workflow used for the Pages app. In this case the editor is the translation provider an the reviewer can be any person in the group. To configure your desired group, change the property here: /modules/content-translation-support-ext-core/tasks/reviewTranslation/groups@publishers

Message views

Workflow message views define how messages display in the Pulse during translation workflow. See Message view definition for more.

Message views are configured here: /modules/content-translation-support-ext-core/messageViews

Work item handlers

The mapping is based on the work item name which is added to the jBPM process definition. There are two handlers configured for the workflow process.

  • approve: Handles importing translated content after approval.
  • reject: Handler for content rejection

Work item handlers are configured here: /modules/content-translation-support-ext-core/workItemHandlers

Translation jobs

The core module installs three scheduled jobs to automate the translation process. The translation is submitted to the translation provider. In the case of, a second request is required to retrieve the translation results. Finally, the translation is either directly imported or the workflow process is initiated.

The jobs are configured under: /modules/scheduler/config/jobs


The executeSubmissionTranslationCommand sends translation submission request to provider.

# Configuration shown in YAML but must exist as a JCR Node.
  catalog: workflowTranslation
  command: threadPoolSubmissionCommand
  cron: 1/60 * * * * ? # set to execute every minute at 1 second past the minute
  description: Output, Send, Update translation batch
  enabled: true
    batchSize: 100 # define how many tuples we retrieve at each execution of the job
    maxAttempt: 10 # define the max retry for each item
    poolSize: 10 # define the size of the thread pool


The executeGetTranslationCommand is for asynchronous translation. For translating services that require a second request to retrieve the translations you will need to use this job as well.

# Configuration shown in YAML but must exist as a JCR Node.
  catalog: workflowTranslation
  command: threadPoolGetTranslationCommand
  cron: 5/60 * * * * ? # set to execute every minute at 5 seconds past the minute
  description: Get translation from provider
  enabled: true
    batchSize: 100 # define how many tuples we retrieve at each execution of the job
    maxAttempt: 10 # define the max retry for each item
    poolSize: 10 # define the size of the thread pool


The executeImportTranslationCommand imports the translation immediately  or starts the workflow. The behavior is set by autoTranslationAllowed property in the translator configuration.

# Configuration shown in YAML but must exist as a JCR Node.
  catalog: workflowTranslation
  command: threadPoolImportCommand
  cron: 0/30 * * * * ? # set to execute every 30 seconds
  description: Import or create import workflow
  enabled: true
    batchSize: 100 # define how many tuples we retrieve at each execution of the job
    maxAttempt: 10 # define the max retry for each item
    poolSize: 10 # define the size of the thread pool

What is exported and imported

By default, text and rich text fields are included in export files. Additional field types can be registered here: /modules/content-translation-support-ext-core/config/propertiesToTranslateFinder. Add another property with the value set to the definition class of the field that should be included.

In addition to registration, the child fields of the composite field should have an i18n property set to true. It is not necessary for the composite field itself to have an i18n property.

    - name: tabText
        - name: composite 
          label: Sample Composite
          class: info.magnolia.ui.form.field.definition.CompositeFieldDefinition
            - name: title
              i18n: true
              label: Title
              class: info.magnolia.ui.form.field.definition.TextFieldDefinition
            - name: subtitle
              label: Subtitle
              class: info.magnolia.ui.form.field.definition.TextFieldDefinition

Notification Email

Magnolia uses Mail module to send a notification email to submitter in case of errors. The template provided is here. The notification email template is configured here: /modules/mail/config/templatesConfiguration/translationNotificationTemplate



  • This module is at INCUBATOR level.

  • OpenJDK Java 11 needs additional dependencies. 

    <!-- For OpenJDK 11 CTE 3.0 you will need to have the following dependencies -->
    <!-- in your web app lib folder-->
  • The frequency of the scheduled jobs may be high for most. For more information on how to configure the cron property see: Scheduler module.
  • DelegatingMultiValueChildNodeWithLocaleTransformer is the transformer to be used when nesting composite fields in multivalve fields, Magnolia 5.7 and 6.x only.
  • There is a NullPointerException when translating multilanguage in Magnolia 5.6.6+. Due to changes on 5.6.6, the registered translators were missing after changing language. 

    Restarting the server will help to reload the translator. Doing so should help resolve the issue.

  • NoSuchDefinitionException when clicking on review action in translation workflow after upgrading to 2.0.2 There was a missing update of the configuration for messageViews node after consolidating translation comparison app with others.

    Navigate to: /modules/content-translation-support-ext-core/messageViews/reviewTranslation/actions/review 

    Add properties: appName=extendContentTranslation and subAppName=comparison



  1. Does this work with 5.7? If so can you add it to the version table at the top?

    1. Yes, for 5.7 I believe you should be using 2.9-SNAPSHOT. Recently Adrien Manzoni did some updating but no official release yet. Still waiting on feedback.

  2. Any news on this ? For 5.7.6 , which exact version should we use ? We are going to start using this CTSX module very soon, so would be great to know what exact version.


    1. Still 2.9-SNAPSHOT on 5.7, better if you could upgrade to Magnolia 6.1 and use the 3.0.2 version.

  3. Thanks Teresa. Upgrading to 6.1 is not going to happen that soon, so we will need to still go for 2.9-snapshot. Btw, why still snapshot ?

  4. 2.9-SNAPSHOT is undergoing some testing, there was a change there last week, might be posible to release later this month but since is in incubator status it does not follow a tight schedule.

  5. Hi Richard Gange, above in the section "What is exported and imported" it's mentioned we can extend the supportedFieldDefinitions, like adding the support for CompositeFieldComposition. I suppose we can also add the MultiValueFieldDefinition and it will take care to automatically go through the mutil-value-fields' entries, given the fact that each sub-field will have the i18n property set to true.

    Do you confirm ?


    1. Exactly, thats how it's supposed to work. It should not matter how complex the data structure. It will still find it. 


      1. Hi Richard, just one last question: I suppose that the new Action "Add to Translation Batch" will be available to the Pages App and for our own Content Apps we just need to add it there as well. Correct ? Is there anything else specific we need to take into account to make it available for our own Content Apps and node types ?


        1. Hey-

          Yes, it's been added to the Pages add using decoration. See here. You can use those as a base for your content app. 


    2. Just to let you know these fixes were not on the Magnolia 5 branch. I back ported them today.

      I might need to move some other fixes back as well. I hope to release a 2.9.1 soon. 

      1. Thanks Richard, we will indeed soon start using it. Appreciated! (wink)

        Please keep us informed so we can have a smooth experience!

  6. Hello Richard Gange,

    Small question, I am trying to install CTSX module just for trial purposes, I am on MGNL: 5.7.6.

    So I am trying with version 2.9.1 and “magnolia-content-translation-support-ext-core” is well picked from nexus but the same version for “magnolia-content-translation-support-ext-apps” is not found.

    Is there a different version for ext-apps as I was expecting “${CTSExtendedVersion}” to be the same(2.9.1) for both maven dependencies on 5.7.*.  


    1. Hello-

      We reworked the module in version 2.9 so the apps module is not required as a separate dependency. Therefore you can remove that from the pom. Just the core module and a service module are required.