AEM Touch/Cloud Connector FAQ

We haven't seen such configuration. So, it is assumed creating groups is hard-coded or hidden.

You can configure that in AEM UI /security/groups.html or can open Project Summary tile and manage Users

Groups can be automatically deleted by deleting a project. There are no other configuration found.

There is a built-in AEM feature to purge projects. It is a part of Maintenance. You must add a purge project task here, for example: 

1. Smartling - Context Preview Settings not configured: Test connection will fail if context is not configured correctly. Ask the client to check that the Server URL, User and password configured are all correct under: <aem-instance>/system/console/configMgr
   • This is the most common cause for Test Connection failure and does not prevent content from being submitted for translation.
2. Client firewall blocking traffic: Ensure api.smartling.com and cms.smartling.com (Port 443) are allowed by the client's network configuration.
3. Incorrect API credentials: Test the client credentials using Smartling's API Authentication endpoint. Example cURL: curl -X POST https://api.smartling.com/auth-api/v2/authenticate -H 'content-type: application/json' -d '{"userIdentifier": "{USER_IDENTIFIER}", "userSecret": "{TOKEN_SECRET}"}'

When a single page is submitted, the Smartling connector may upload more than one file. This is a result of tags/dictionaries/assets being included. If you wish to exclude these types of strings from files such as these:

070b0946-9ca3-447b-8f2b-405553141cd0:ASSETMETADATA
f74a06e0-e211-4fc8-ab89-a757c43835e0:TAGMETADATA
ac2ddc50-2fa4-4cd1-b4c5-acc10ea02c4c:/apps/i18n/en.json

Yes, this can be done in the Web Console Configuration (<aem-instance>/system/console/configMgr)

AEM submits one file per language for translation. This results in the creation of one file per locale in Smartling, which is why you will see multiple files with the same source text. For example, if you submit one AEM page for translation into four languages, you will see four different files in the Smartling job. Each file name contains a reference to the target locale code. A file with “fr” in the filename is for translating into French, a file with “es” in the filename is for translating into Spanish, etc. You can ignore all other strings in the awaiting authorization queue that are not in a job. There is no way to remove them, as they are the result of the unique nature of AEM and Smartling TMS. 

Example:

Yes, Smartling supports translating content in Adobe AEM Guides as part of the localization framework.

In general, there are three possible reasons why your job has "No Content". Please see Troubleshooting "No Content" in Jobs.

For AEM connector projects, the most common reason for "No Content" is that the content is already in another Smartling job. The status "No Content" essentially means "no new content detected for translation." You can ignore these empty jobs, as they will be automatically canceled after 7 days. You can also cancel and delete them manually if you prefer.

When creating a Smartling configuration, make sure that you set the configuration for the page that is the parent to your sites (original and localized).

Yes, as outlined here. You will need to add an alias for the pages and ensure that sling:alias is added to the translation rules. You may also need to update some AEM settings as outlined in the answer to the question "Why is the title not translated?".

This is a known issue in AEM, special characters in the URL are "double escaped" and cause a 404 error. Apache should be configured to allow encoded slashes in URLs: AllowEncodedSlashes On

If you need specific sub-pages submitted, you will need to complete page submissions separately. There is no way to do a bulk submission for specific subpages.

Two ways:

In multiple ways, the main ones being:

In CRX/DE, find the content fragment under the page tree and locate the sling:resourceType:

You can make edits to translations in Smartling, then use the Force resubmission option (Required if page is unchanged) to create a new AEM Translation Project to pull back updated translations.

Please note this will generate an empty job in Smartling showing “No Content”. If you have configured callbacks, AEM will automatically download the updated translations. Otherwise, AEM will download the updated translations in accordance with the Scheduler cron.

Yes. If a page is re-requested for translation after changes are made to non-translatable content, it will result in an empty job in Smartling showing “No Content” (since there are no changes to the translatable content). AEM will create a new launch from the source page which will include all changes. The connector will deliver existing translations and the launch will be promoted to the existing language version. The updates made to non-translatable content will be reflected in AEM.  

Tags are not applied on a target page by default. If you want to copy tags from the source page (original) to the target page (translated), you should add/change excluded property for `cq:tags`. For example, the appropriate value is:

cq:(?!(designPath|template|translationStatus|lastTranslationUpdate|tags)$).*

Although you may have submitted a page and translated all content, including the title of the page, ("jcr:title" property), you may notice that the title didn't translate properly. This is because the Smartling Touch Connector is responsible for submitting original content to Smartling, and it pulls translations back. However, applying translations to page properties is handled by AEM.

• Navigate to the Translation Project in AEM.
• Under Translation Job, click the 3 dots:
• This will show the pages/assets in the Job.
• Select the pages/assets and click Accept Translation:
• A modal window will pop up, click Accept:
  
• This will accept the translations, but the launch containing translations still needs to be promoted to the target page.
• Click the page/asset again and click Preview in Sites:
• Once the page opens, select Promote Launch from the middle menu:
  
• Select Promote full launch, you can also select Delete launch after promotion to delete the launch.
  
• Finally, on the Review step, click Promote.