Get the latest version of the connector from the Maven central repository.
Version 5.9.55
[12/30/25]
Internal improvement released
Version 5.9.54
[12/29/25]
Improvement
- The connector now supports the directive
<characterLimit>none</characterLimit>for XML properties that should not inherit the character limit from a previous string in the file. - Fixed an issue related to saving property mappings.
Version 5.9.53
[12/15/25]
Improvement
-
A new Smartling workflow parameter,
localeWorkflows, has been added. It stores associations between a SmartlingtargetLocaleand aworkflowUid, for example:[ { "targetLocale": "fr", "workflowUid": "42478ed22598" }, { "targetLocale": "de", "workflowUid": "04ec4daa5daf" } ]The specified workflow will be used for content sent for translation in the corresponding target language. For additional context, please see AEM Touch/Cloud Connectors Technical Resources.
Version 5.9.52
[11/18/25]
Bug fix
- When requesting additional locales for Experience Fragments, files are no longer duplicated.
Version 5.9.51
[11/7/25]
Bug fix
- Character limit feature now works with
Autoparser option.
Version 5.9.50
[10/31/25]
Improvement
-
You can now set a character limit for a property mapping. We recommend using this feature with plain text strings. The limit will be shown to the translator/linguist working on the translation in the CAT Tool.
Alternatively, you can specify the limit in the
property_mappings.jsonfile. For example:{ "contexts": [ { "path": "/content", "components": [ { "type": "General", "mappings": [ { "propertyName": "text", "smartlingParser": "text", "characterLimit": "255", "inherit": true } ] } ] } ] }
Version 5.9.49
[10/27/25]
Bug fix
- Several fixes have been implemented for the context feature. The connector now respects the language set for a language root and takes the language into account for resolving source content for taking context. The native context renderer composes proper URL for the context. This URL is then displayed in the Smartling dashboard within the Context tab of your AEM project.
Version 5.9.48
[10/23/25]
Bug fix
- Previously, ambiguous language mapping could cause the connector to generate an incorrect namespace for uploaded files. This issue has been resolved. The connector does not use language mappings for file namespaces.
Version 5.9.47
[10/20/25]
Improvement
-
Context for a page or an experience fragment can be taken from the source page/fragment. Use this OSGi configuration file:
com.smartling.aem.connector.context.impl.resources.http.HttpResourceLoader.cfg.jsonto enable this feature by settingpreview.from.sourceon (true).{
// Causes connector to take context from AEM directly
"direct.rendering": true,
// AEM Author Instance URL, required
"server.url": "https://author-p15353-e35406.adobeaemcloud.com",
// Username for local AEM Cloud user, required
"user.name": "<user>",
// Password for local AEM Cloud user, required
"user.password": "<password>",
// Connection timeout for loading context from AEM instance in ms. Min 2000ms,
Max 10000ms. Optional, 2000ms is default
"connection.timeout": 2000,
// Socket timeout for loading context from AEM instance in ms. Min 10000ms,
Max 20000ms. Optional, 10000ms is default
"socket.timeout": 10000,
// Preview WCMMODE. This mode is used for requesting context. Optional, 'disabled'
is default
"request.wcmmode": "disabled",
// Enables or disables taking the context preview from the source. For pages and
experience fragments, the context preview is taken from associated launches by
default.
"preview.from.source": true
}
Version 5.9.46
[10/20/25]
Internal improvement released
Version 5.9.45
[10/3/25]
Improvement
- Multiple pages can be sent for translation. Users should open the Sites view, select several pages, and click the Translate button in the action bar. The Smartling Dialog will appear.
Bug fix
- Fixed the connector's validation for strings sent for translation. It now validates all strings for a text and/or for valid XML subnodes.
Internal improvement
- Additional internal improvement released in this version.
Version 5.9.44
[9/12/25]
Improvement
- The connector now supports the Markdown content type. A property can be mapped to Markdown either through the Translation Rules UI or in the
property_mappings.jsonfile.
Version 5.9.43
[8/11/25]
Internal improvement released
Version 5.9.42
[8/11/25]
Bug fix
- A temporary validation issue on the Smartling dialog has been fixed.
Version 5.9.41
[8/1/25]
Bug fix
- The connector now matches properties to translation rules for nodes and all subnodes. Components in AEM may store their data in subnodes and descendant nodes in the repository. The AEM Translation framework matches translation rules not with the component itself, but with all subnodes. The connector can now match the Smartling parser in the same manner.
Version 5.9.40
[6/26/25]
Improvements
- In the event of a rendering error, the context image will be taken from the repository.
-
The connector makes HTTP connection to Smartling with socket timeout set to 40000 milliseconds by default. If you experience errors related to
SocketTimeoutException, you can adjust this value in the OSGi configuration file:com.smartling.aem.connector.core.impl.integration.platform.ApiInstanceBuilder.cfg.json
api.socket.timeoutdefines the timeout for requests sent to Smartling, in milliseconds. The minimum value is 10000 ms, the maximum is 60000 ms, and the default is 40000 ms.
Version 5.9.39
[6/10/25]
Internal improvement released
Version 5.9.38
[5/29/25]
Bug fixes
- The connector waits until AEM has fully prepared a translation project. Once AEM completes this process, the connector overwrites the
Auto *project options. - The connector can now work with the AEM Translation Framework's upload call, even when the source language parameter is not provided.
Version 5.9.37
[5/23/25]
Improvement
-
Autooption for Smartling parser was introduced in the Translation Rules UI.
Bug fix
- Fixed missing MIME type for an asset retrieved directly from AEM for context.
Version 5.9.36
[4/29/25]
Improvement
- Added check for existing locale mapping for the source locale in the Smartling Dialog.
Version 5.9.35
[4/24/25]
Improvement
-
The connector captures context directly from AEM in a native way using
SlingRequestProcessor. This is the default behavior.
To switch back to HTTP based rendering, use thedirect.renderingoption incom.smartling.aem.connector.context.impl.resources.http.HttpResourceLoader.cfg.jsonOSGi config.
{
// Causes connector to take context from AEM directly
"direct.rendering": true,
// AEM Author Instance URL, required
"server.url": "<server_url>",
// Username for local AEM Cloud user, required
"user.name": "<user_name>",
// Password for local AEM Cloud user, required
"user.password": "<password>",
// Connection timeout for loading context from AEM instance in ms. Min 2000ms, Max 10000ms. Optional, 2000ms is default
"connection.timeout": 2000,
// Socket timeout for loading context from AEM instance in ms. Min 10000ms, Max 20000ms. Optional, 10000ms is default
"socket.timeout": 10000,
// Preview WCMMODE. This mode is used for requesting a context. Optional, 'disabled' is default
"request.wcmmode": "disabled"
}Version 5.9.34
[4/14/25]
Improvement
- Added support of
Repeat translationAEM feature.
Version 5.9.33
[2/27/25]
Improvement
- Smartling Dialog validates translation method and provider applied to the content.
Version 5.9.32
[2/19/25]
Improvement
- If the user does not specify a parser, the connector will detect a Smartling parser (Text or HTML) for the property content. If the property string does not contain an HTML tag, &, or ", the connector assumes it is just text and not HTML.
Version 5.9.31
[2/10/25]
Improvement
- Connector checks
/conf/global/settings/smartling/configuration/languageMappingfor language mappings first. Usage of this path avoids a warning in AEM Cloud deployment log about overriding/apps/granite/translation/connector/configuration/smartlingby customer package. - The connector takes context from the target page/XF/DAM, not from the source. It ensures that the context matches the styles and JavaScript set for the target content.
Version 5.9.30
[1/30/25]
Improvement
- Smartling credentials can be set in OSGi configuration
com.smartling.aem.connector.core.SmartlingCredentialsConfiguration.cfg.jsonCredentials cannot be changed in the UI in this case.
Bug Fix
- Fixed updating
payloadof workflow form on page editor.
Version 5.9.29
[1/24/25]
Improvement
- Connector allows you to request a DAM folder and all its descendants. By default, it includes the folder’s children. Update
com.smartling.aem.connector.automation.ui.SmartlingDialogConfiguration.cfg.jsonto request descendants of the folder. - Connector has a limitation: it processes only the first 100 assets it finds.
Version 5.9.28
[1/21/25]
Improvement
- Pseudo translation default option was added to OSGi configuration
com.smartling.aem.connector.automation.ui.SmartlingDialogConfiguration.cfg.json
Bug Fix
- AEM Translation Configuration UI correctly displays the Smartling parser for context with inherited rules.
Version 5.9.27
[1/13/25]
Bug Fix
- Connector applies Smartling parser (HTML/Text) according to inheritance of translation rules context.
Version 5.9.26
[12/27/24]
Bug Fix
- The validator for AEM-created XML files was updated to allow XML string as a property value.
Version 5.9.25
[12/25/24]
Internal improvement
Version 5.9.24
[12/20/24]
Improvement
- Minor refactoring to fix AEM warnings. Changed the main package's type to
container.
Version 5.9.23
[12/2/24]
Bug Fix
- Connector checks translation rules for AEM components taking into account inheritance between them.
Version 5.9.22
[11/22/24]
Bug Fix
- Connector trims whitespaces in Smartling job name and page/experience fragment title before initiating the translation flow. This ensures that registered AEM repository namespaces are not used as job or page names.
Version 5.9.21
[11/1/24]
Improvement
- Context is taken from source content.
- Connector uses the latest Smartling Java API.
- Connector checks if target content prepared (exists) for translation request.
Version 5.9.20
[10/11/24]
Improvement
- AEM
translation job Idwas shortened to 12 alphanumeric symbols ([a-zA-Z0-9]). You will see a shorter file name in the Smartling dashboard.
Example:62f1a6b0-eb31-4cb5-9ac5-c2b7b70b3a4e:/content/launches/2021/08/26/men2/content/we-retail/language-masters/de/menwill bed4p56Lsew2m9:/content/launches/2021/08/26/men2/content/we-retail/language-masters/de/men - Updated storage layout under
/content/projects/smartling-metadata. Smartling now stores upload metadata in theyyyy/mm/ddfolder structure. - All new Smartling metadata nodes now include two additional fields:
jcr:createdandjcr:lastModified
Version 5.9.19
[09/18/24]
Internal improvement released
Version 5.9.18
[09/16/24]
Internal improvement released
Version 5.9.17
[08/21/24]
Improvement
- Pseudo option is added to
Create Jobin Smartling Dialog. IfPseudo translationcheckbox is checked, connector will retrieve pseudo translation for the content
Bug Fix
- Fixed reset of UI form after closing the dialog.
Version 5.9.16
[07/31/24]
Bug Fix
- DOM mutation events are replaced with JS Observer.
Version 5.9.15
[07/19/24]
Bug Fix
- Fixed language options set in Smartling Dialog for cases where dialog is reopened on one Experience Fragment and then on another Experience Fragment later.
Improvement
- Target content validator is added. Can be turned on in OSGi configuration. com.smartling.aem.connector.automation.ui.SmartlingDialogConfiguration.cfg.json
Version 5.9.14
[07/10/24]
Internal improvement released
Version 5.9.13
[04/22/24]
Improvement
- Bug fix: It is now possible to select the current date ("today") as the Job due date.
Version 5.9.12
[04/15/24]
Improvement
- The Connector now trims any extra spaces that a user may accidentally add to their Smartling credentials while configuring the Connector.
Version 5.9.11
[03/29/24]
Internal improvement released
Version 5.9.10
[03/20/24]
Improvement
-
A new OSGi
Enable Legacy Config Validationoption has been introduced. It allows you to disable or enable validation for a legacy configuration applied for a page.
OSGi configuration can be specified as com.smartling.aem.connector.automation.impl.wcm.project.TranslationProjectResourceManager.cfg.json:{ "polling.retry.count": 60, "polling.retry.sleep": 600, "polling.upload.complete": 30, "translation.project.enable.approve": true, "translation.project.enable.delete": true, "translation.project.enable.promote.launch": true, "translation.project.enable.legacy.config.validation": false }
Version 5.9.9
[03/11/24]
Improvement released
-
The
Callback Host URLoption is replaced with aCallback URLoption. Customers should specify the full callback URL, e.g. http://my-aem.host.com/services/smartling/sync-translation. For backward compatibility, the previously specified optionCallback Host URLis used if noCallback URLoption has been specified.
Here is an example of OSGi config file com.smartling.aem.connector.core.impl.config.CallbackUriProviderConfig.cfg.json{ "callback.url" : "https://my.domain.com/some/path/for/callback", // This property is used by default. "callback.host.url":"https://my.domain.com", // If there is no callback.url, then https://my.domain.com/services/smartling/sync-translation will be used. "callback.shared.secret":"MySecret" }
Version 5.9.8
[02/28/24]
Internal improvement released
Version 5.9.7
[02/15/24]
Improvement
- Context is enabled for Author AEM instance only.
Version 5.9.6
[02/09/24]
Bug Fix
- Languages are visible on the Dialog after reopen and selecting a job on Add to job tab.
- Fixed validators for proper processing of several assets or content fragments.
- Removed logging into a separate file. It is prohibited in AEM Cloud.
Improvement
- Connector allows you to configure AEM Translation project automatic options.
-
OSGi configuration can be specified as com.smartling.aem.connector.automation.impl.wcm.project.TranslationProjectResourceManager.cfg.json:
{
"polling.retry.count": 60,
"polling.retry.sleep": 600,
"polling.upload.complete": 30,
"translation.project.enable.approve": true,
"translation.project.enable.delete": true,
"translation.project.enable.promote.launch": true
}
-
- Connector doesn't validate missed languages after selecting a job in Smartling Dialog.
- Now, if there is no match for available languages and languages taken from selected job - no languages are selected.
- Updated Auto Authorize option in OSGi config.
- It can be used as a default value for Authorize Job option in the Smartling Dialog. OSGi configuration file is com.smartling.aem.connector.core.impl.integration.SynchronousSmartlingFacade.cfg.json:
{
"auto.authorize": true,
"move.strings": false
}Version 5.9.5
[01/30/24]
Bug Fix
- Languages are visible on the Dialog after reopening.
- Fixed Translation rules Reference UI, Check child nodes from asset reference and create language copy checkboxes are visible.
Version 5.9.4
[12/05/23]
Internal improvement released
Version 5.9.3
[10/20/23]
Internal improvement released
Version 5.9.2
[10/06/23]
Bug Fix
- Fixed processing of translation rules for resolving related assets.
Version 5.9.1
[09/26/23]
Bug Fix
- Fixed bug with DITAMAP files.
- Added a new index under '/content/projects' for Smartling properties. This may result in AEM re-indexing, which may take some time.
Version 5.9.0
[09/15/23]
Improvement
- The Connector uploads content using additional metadata saved in the translation project folder. It avoids an AEM issue in Prepare Translation Step for content sent for translation from Smartling Dialog.
Version 5.8.4
[08/31/23]
Improvement
- Added validation for unchecked of
Translation Component Stringsoption in Translation Integration configuration.
Version 5.8.3
[07/26/23]
Bug Fix
- Fixed bug with polling AEM for translation project being created.
Improvements
- Added support of buckets in translation project's job.
Version 5.8.2
[07/26/23]
Bug Fix
- Fixed error for loading projects on non-content or service pages.
Improvements
-
Siblings languages onlyoption specified forSmartling - Page language copy manager (Touch)configuration works for assets too.com.smartling.aem.connector.automation.impl.wcm.localization.PageLanguageCopyManagerImpl.cfg.json{ "respect.content.observing.language.roots": true, "only.sibling.language.roots": true }
-
Added support of web callbacks. When translation of a file is completed, Smartling side will sent an HTTP request to AEM Touch Connector. Connector will ask AEM to sync the translation with Smartling side.
Some AEM options should be configured to have this feature work properly. First of all be sure that proper AEM host URL is specified in Smartling - Callback URL (Touch) OSGi configuration. The connector can validate the signature of an incoming callback request, see documentation. To enable this feature, the customer should contact their Smartling CSM to enable signed callbacks for your account.com.smartling.aem.connector.core.impl.config.CallbackUriProviderConfig.cfg.json{ "callback.host.url":"https://aem.public.host.com", "callback.shared.secret":"secretSharedString" }org.apache.sling.engine.impl.auth.SlingAuthenticator.cfg.json{ "sling.auth.requirements":[ "+/", "-/libs/granite/core/content/login", "-/etc.clientlibs", "-/etc/clientlibs/granite", "-/libs/dam/remoteassets/content/loginerror", "-/aem/update.theme", "-/linkexpired", "-/services/smartling/sync-translation" ] }
Version 5.8.1
[04/20/23]
Bug Fix
- Smartling job locale validator checks locales available for the current page/XF/CF only.
Improvements
-
Added a toggle
Only sibling language rootsfor narrowing a list of languages on Smartling dialog. This option can be set as a part ofcom.smartling.aem.connector.automation.impl.wcm.localization.PageLanguageCopyManagerImpl.cfg.jsonOSGi configuration{ "respect.content.observing.language.roots": true, "only.sibling.language.roots": true }
Version 5.8.0
[03/21/23]
Bug Fix
- Fixed processing of blank fields that are sent for translation.
Improvements
- Added
Move stringsoption. Usemove.stringsboolean option incom.smartling.aem.connector.core.impl.integration.SynchronousSmartlingFacadeOSGi configuration. - Variants for i18n dictionary are set from i18n-keys/property names.
- The language selector shows country and locale for a language option.
- Smartling dialog allows searching by a language contained a term (e.g. locale code).
- Connector installs a new security group
smartling-projects-owners. Every user assigned to the group getsOwnerandObserverroles for every translation project created via Smartling Dialog.
CAUTION! The user assigned to the group should have appropriate permissions for managing a translation job. In another case, AEM may encounter issues with applying translations under the user permissions. It is recommended the user should be assigned to theAuthorsandProjects Administratorssecurity groups along with thesmartling-projects-ownersgroup at least.
Version 5.7.4
[12/29/22]
Internal Bug Fix
Version 5.7.3
[12/29/22]
What's New
- Added permissions to the connector for reading custom languages
Version 5.7.2
[12/26/22]
What's New
-
Language selector shows languages in alphabetic order.
Bug Fix
- Translation project folder name is created properly from long page title.
Version 5.7.1
[12/22/22]
What's New
-
Connector supports Smartling Job Long text custom fields.
Bug Fix
- Fixed showing a validation failed message on the Smartling Dialog.
- Fixed scroll of language selector showed many languages.
Version 5.7.0
[12/06/22]
What's New
- Metadata in images and documents (DOM assets) can be sent for translation via Smartling dialog.
- You can now select the Smartling project to send AEM content to in the translation dialog
- Updated success message for Smartling translation dialog to
Page was queued into AEM Translation Workflow.
Bug Fix
- Fixed error on taking Smartling custom fields for a page without any language assigned.
Version 5.6.17
Internal Enhancement Released
Version 5.6.16
What's New
- Smartling Job now shows language display name provided by AEM instead of ISO 3166.
Bug Fix
- Fixed Force resubmission option for Content fragment translation request.
-
Removed wrong information message about missed locale mappings for duplicate languages, e.g. [fr, de, fr, de, fr]
Version 5.6.15
What's New
- Added new Smartling Dialog validator. The validator checks is there any updates on a content after last translation.
Bug Fix
- Full reconnection on error in context connection. Test connection checks context for the whole multi-configuration.
- Fixed error in traversing over cycle of referenced content.
Version 5.6.14
What's New
- AEM Cloud Connector now supports the translation of attached Microsoft Office Documents
Version 5.6.13
Bug Fix
- Fixed multi-configuration authentication for context upload
Version 5.6.12
What's New
- Added a new content uploading configuration option in com.smartling.aem.connector.automation.impl.wcm.project.TranslationProjectResourceManager:
polling.upload.complete="{Long}20"This manages the waiting period of connector for upload, in minutes. 10 mins is minimum, 20 mins is default, 30 mins is maximum. Content upload should be done in this period after translation request started.
Bug Fix
- Fixed caching context connection with incorrect user credentials.
Version 5.6.11
Bug Fix
-
Index declarations are moved to APP package
Version 5.6.10
Bug Fix
-
Adjusted error message for missed service user mapping. We made OSGi configuration in a standard format. OSGi configs are applied for all modes: author and publish. We made a log to be written into standard error.log. We made indices to be merged upon deployment.
Version 5.6.9
Bug Fix
-
Removed unnecessary check for overridden language properties for a source root page
Version 5.6.8
What's New
- Improved search for a Smartling configuration
Bug Fix
-
Fixed error message about missed language mapping
Version 5.6.7
Bug Fix
-
Introduced a hotfix for this AEM Cloud issue
Version 5.6.6
Bug Fix
- Fixed processing bug when a custom field UID started with a digit