Info: Get the latest version of the connector from the Maven central repository.

Version 5.9.75

Release date: October 26, 2026

Improvement

Smartling job names now match the AEM translation project title
When you request a translation outside the Smartling dialog (for example, from the References panel), the connector now names the Smartling job after the AEM translation project. A project titled "Spring Campaign" creates a job named "Spring Campaign - 1234567890123". The connector appends a number to keep job names unique.

Version 5.9.74

Release date: October 16, 2026

Improvement

A new optional feature lets you control access to the connector’s Translate button through a dedicated permission. The connector introduces the permission smartling:translationButton, which only manages the visibility of the button. Users can still request translation through the Reference Panel. By default, the permission is set to allow on the path /content for the Smartling Project Owner group.

How to use the feature
First, your AEM administrator must enable the feature in OSGi. It is off by default. com.smartling.aem.connector.automation.impl.visibility.TranslationButtonVisibilityService.cfg.json:
```
{   
  "restrict.translation.button": true 
}
```
After that, an administrator can assign the permission to a specific user or group. For example:

In this example, the Translate button will not be available for Magazine page.
This feature works for Sites, DAM, Forms, and Page Editor UIs.

Version 5.9.73

Release date: September 22, 2026

Improvement

The connector has a new OSGi configuration option, pseudo.download.locales. Here you can specify a list of Smartling locales for pseudo translation. This can be specified in the config file com.smartling.aem.connector.core.impl.PseudoContentDownloadManager.cfg.json:

{
  // Smartling locale codes. When every target language selected in the Smartling dialog maps to a
  // locale from this list, the dialog pre-selects the "Pseudo translation" option. The author can still
  // turn it off; this list never overrides that choice
  "pseudo.download.locales" : [ "es" ],
  // Cancel job files after delivery option (true by default)
  // Causes connector to cancel an empty job (without source files) after pseudo translation was downloaded
  "pseudo.download.cancel.job": true,
  // Remove a file after delivery option (true by default)
  // Causes connector to remove a file after pseudo translation was already downloaded for them
  "pseudo.download.remove.file": true
}

This option turns on the Pseudo translation option in the Smartling dialog if the set of target languages matches the list of languages in the OSGi configuration.

It only works if you haven't manually changed the Pseudo translation option.

Version 5.9.72

Release date: September 14, 2026

Internal improvements released

Version 5.9.71

Release date: August 31, 2026

Improvement

Introduced support for Simplified Index Management. See Simplified Index Management using the diff index. The connector no longer provides indices by itself. You must add the connector's index definitions to your AEM customization project using diff.json. The AEM Cloud Connector's diff.json file can be downloaded here.

Version 5.9.70

Release date: August 11, 2026

Improvement

The connector shows a dialog with a message on every failed validation, meaning that when content is submitted for translation and there is nothing new to translate, it will block the translation request.
Also, the Smartling dialog prevents submitting content that is already up to date with the latest translations.

Version 5.9.69

Release date: July 31, 2026

Internal improvements released

Version 5.9.68

Release date: July 6, 2026

Bug fix

The connector resolves translation rules and property mappings the same way AEM does. It prioritizes specific-component property mappings over general/child-node mappings. See details below.

Property mapping: what to review after this upgrade

This release improves how the Smartling AEM connector decides which parser (Auto, Html, Text, or Markdown) to apply to each property you send for translation.

What changed

The connector now applies the parser you configured for a component more consistently, including for properties inside multi-value or nested components (carousels, lists, tabs, and similar), and follows the same inheritance behavior as AEM's translation rules. In some setups this means a property that was previously treated as plain Text may now be treated as HTML (or the other way around), so that it matches what you configured.

Do I need to do anything?

Only if you use a property-mapping configuration file (property_mappings.json). If you don't, nothing changes for you.

What to review

If you use property mapping, review these cases — they are the ones most likely to be affected:

Properties inside multi-value or nested components (carousels, lists, tabs, accordions, etc.). Confirm the parser configured for those component properties is the one you want.
A property configured in two places — both "generally" and on a specific component. The specific component's setting now takes precedence.
Nested content-path scopes with inheritance. A setting inherited from a higher-level scope now applies even when a more specific scope opted out of inheritance.

Recommendation

There are four parser options: Auto, Html, Text, and Markdown. Auto is the default — it guesses the parser from the content, which can vary. For any property where the parser matters, set it explicitly instead of leaving it on Auto; an explicit value is predictable and stable. Set the parser in either place:

In the Translation Rules configuration UI (component / property editor): choose the value from the Parser dropdown — Auto, Html, Text, or Markdown. The UI saves the selected value.
In the property_mappings.json file (if you edit it directly): use the exact lowercase value — "auto", "html", "text", or "markdown".

{ "propertyName": "description", "smartlingParser": "html", "inherit": true }

What to expect

For any property whose parser changes as a result of this upgrade, the next translation job may re-send that content. Because the content is now parsed differently, it may create new strings that can't fully leverage your existing translation memory. As a result, some strings may not SmartMatch and may need to be translated again. Translate these in your normal translation workflow.

Version 5.9.67

Release date: July 3, 2026

Internal improvement released

Version 5.9.66

[6/10/26]

Improvement

NEW: Automatic Request Translation on Republish Setting

Once a file is fully published, the AEM connector delivers translations to AEM, but any subsequent edits to those published translations are not automatically sent back. Previously, to push updated translations from Smartling back to AEM, you would need to use the Force Resubmission option to create a new AEM Translation Project. With this new setting enabled, the connector automatically resubmits content when published translations are edited and republished after the original AEM job completed, eliminating manual resubmission when translators fix content post-delivery.

How it works

The feature is managed by the OSGi configuration

com.smartling.aem.connector.automation.impl.republish.AutoRepublishPollingJob.cfg.json:

{
  "enabled": true,
  "cronExpression": "0 0 8 1/1 * ? *",
  "lockTtlMinutes": 30,
  "recentlyPublishedWindowDays": 1,
  "metadataRetentionDays": 30
}

The connector runs a background job on a configurable schedule. At each interval, it checks whether any translation updates have been made to previously submitted content, using metadata saved at the time of the original upload. If updates are detected, the connector automatically resubmits the content to the same Smartling job using the original request parameters: job, target language, and custom fields.

If the original job no longer exists, the connector creates a new job.

Limitations

Applies to pages, Experience Fragments (XFs), and Content Fragments (CFs) only.
Automatic resubmission only applies to content that was originally requested after this setting was enabled.

Version 5.9.65

[5/15/26]

Improvement

Introduced a new option for the Move strings setting. It can be specified in the OSGi configuration
com.smartling.aem.connector.core.impl.integration.SynchronousSmartlingFacade.cfg.json:
```
{
  "auto.authorize": true,
  "move.strings.mode":"NONE"
}
```
Three options are available:
- NONE – only add new strings from the file to the job
- IN_PROGRESS – also move existing untranslated strings in the file from other jobs
- ALL – move every string in the file, including already published ones
It replaces the legacy move.strings configuration property. If no mode is specified, the connector uses this property as a fallback for backward compatibility.

Version 5.9.64

[5/7/26]

Improvement & Bug Fix

Add to Job tab displays up to 100 jobs. This limit can be adjusted in the OSGi configuration.

{
  "respect.content.observing.language.roots": true,
  "only.sibling.language.roots": false,
  "translation.project.enable.legacy.config.validation": true,
  "target.content.existence.validation": false,
  "translation.pseudo.default": false,
  "check.dam.folder.descendants": false,
  "max.jobs.limit": 100
 }

User is now added to the smartling-projects-owners group as a project owner/observer when a workflow error occurs or the polling limit is exceeded during translation request processing.

Version 5.9.63

[4/24/26]

Improvement & Bug Fix

The connector now uses an updated approach to preprocessing source XML files. The property mapping algorithm recreates XML nodes rather than renaming them, avoiding XML namespace validation entirely.
Fixed an issue where the connector was incorrectly detecting the AEM version when multiple products are installed on the same AEM instance.

Version 5.9.62

[4/09/26]

Improvement

It is now possible to select multiple Experience Fragments and create a translation request for them.

Bug fixes

Smartling's AUTO parser option now detects and parses markdown.
When requesting context information for non-content entries (such as ASSETMETADATA, TAGMETADATA, or I18NDICTIOARY), no error is shown.

Version 5.9.61

[3/30/26]

Bug fix

Connector does not check AEM content for XML errors.

Version 5.9.60

[3/13/26]

Bug fix

Namespace resolution algorithm compares AEM and ISO 639 language codes regardless of whether a hyphen or underscore is used.

Version 5.9.59

[2/27/26]

Bug fix

Fixed issue where the Include Subpages option did not appear in the translation request dialog.

Version 5.9.58

[2/19/26]

Improvements

Upgraded Apache Commons Collections to version 4.4.

Version 5.9.57

[2/13/26]

Improvements

Removed usage of deprecated packages ch.qos.logback, org.slf4j.spi,
com.day.cq.contentsync.handler.util and com.google.common.

Version 5.9.56

[2/10/26]

Improvements

The connector now supports an instant translation option, allowing you to generate translations without creating a translation job or routing content through a translation workflow. Instead, content is translated immediately using Smartling’s Instant MT service. This option can be selected as a translation method.

The Instant Translation dialog was introduced to support this feature. It appears if the translation provider is set to smartling-instant in the Cloud configuration for the selected content.

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 Smartling targetLocale and a workflowUid, 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 Auto parser 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.json file. 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.json to enable this feature by setting preview.from.source on (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.json file.

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.timeout defines 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

Auto option 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 the direct.rendering option in com.smartling.aem.connector.context.impl.resources.http.HttpResourceLoader.cfg.json OSGi 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 translation AEM 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/languageMapping for language mappings first. Usage of this path avoids a warning in AEM Cloud deployment log about overriding /apps/granite/translation/connector/configuration/smartling by 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 payload of 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.json to 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 Id was 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/men will be d4p56Lsew2m9:/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 the yyyy/mm/dd folder structure.
All new Smartling metadata nodes now include two additional fields: jcr:created and jcr: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 Job in Smartling Dialog. If Pseudo translation checkbox 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 Validation option 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 URL option is replaced with a Callback URL option. Customers should specify the full callback URL, e.g. http://my-aem.host.com/services/smartling/sync-translation. For backward compatibility, the previously specified option Callback Host URL is used if no Callback URL option 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 Strings option 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 only option specified for Smartling - 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

Version 5.8.0

[03/21/23]

Bug Fix

Fixed processing of blank fields that are sent for translation.

Improvements

Added Move strings option. Use move.strings boolean option in com.smartling.aem.connector.core.impl.integration.SynchronousSmartlingFacade OSGi 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 gets Owner and Observer roles 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 the Authors and Projects Administrators security groups along with the smartling-projects-owners group 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 toPage 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

AEM Cloud Connector Version History

Version 5.9.75

Improvement

Version 5.9.74

Improvement

Version 5.9.73

Improvement

Version 5.9.72

Internal improvements released

Version 5.9.71

Improvement

Version 5.9.70

Improvement

Version 5.9.69

Internal improvements released

Version 5.9.68

Bug fix

Property mapping: what to review after this upgrade

What changed

Do I need to do anything?

What to review

Recommendation

What to expect

Version 5.9.67

Internal improvement released

Version 5.9.66

[6/10/26]

Improvement

Version 5.9.65

[5/15/26]

Improvement

Version 5.9.64

[5/7/26]

Improvement & Bug Fix

Version 5.9.63

[4/24/26]

Improvement & Bug Fix

Version 5.9.62

[4/09/26]

Improvement

Bug fixes

Version 5.9.61

[3/30/26]

Bug fix

Version 5.9.60

[3/13/26]

Bug fix

Version 5.9.59

[2/27/26]

Bug fix

Version 5.9.58

[2/19/26]

Improvements

Version 5.9.57

[2/13/26]

Improvements

Version 5.9.56

[2/10/26]

Improvements

Version 5.9.55

[12/30/25]

Internal improvement released

Version 5.9.54

[12/29/25]

Improvement

Version 5.9.53

[12/15/25]

Improvement

Version 5.9.52

[11/18/25]

Bug fix

Version 5.9.51

[11/7/25]

Bug fix

Version 5.9.50

[10/31/25]

Improvement

Version 5.9.49

[10/27/25]

Bug fix