Adobe Experience Manager Connector
Overview Key features Update notes Release notes Installation guide Package installation Deployment to AEMaaCS Connector configuration Custom content types Additional settings Custom language mapping Create user group Grant user permissions Share access to projects Auto replace hyperlinks User guide Create new language copy Update language copy Component translation Translation Project template Avilinga Translations console Manual translation retrieval Manual Launch promotion i18n dictionary translation Audit translations Share a project Maintenance Troubleshooting Remote Log service Solve issues

Troubleshooting

Remote Log service

The Remote Log service is running on the Adobe Experience Manager instance to collect anonymous data from using Avilinga Translation Connector with possible issues if any to help quickly solve any usage problems. When Send anonymous usage log data to help in resolving issues is ON, the Remote Log service is sending a pack with the log of Avilinga plugin usage to Avilinga servers every 30 minutes using a secure connection.

Note: we store only technical data of Avilinga Translation Connector usage and do not have access to any private or content data in the log.

When Send anonymous usage log data to help in resolving issues is OFF user can force sending Remote Log technical data to Avilinga to help solve any problem with the Force send log button in the Avilinga Translation Connector configuration screen:

1. In Tools, Cloud Services, go to Translation Cloud Services.

2. Navigate to conf/global/Avilinga Translation Connector.

3. Select the Avilinga configuration you have set up on your AEM instance and click the Edit button.

4. Select the Service tab and click Send log data to Avilinga.

To adjust time interval for automatic sending log data by Avilinga Translation Connector when Send anonymous usage log data to help in resolving issues is ON follow the next steps:

- Navigate to /system/console/configMgr to open Adobe Experience Manager Web Console Configuration.

- Search for Avilinga Remote Log Service.

- Click Edit button.

- Set cron expression according to cron expression rules. Default setting: every 30 minutes.

Note: if the log is empty it will not be sent.

Solve issues

This section contains possible issues which can be solved by setting specific configuration settings. 

Some job languages are not launched while creating Update Translation job with the References sidebar.

It means there are no data to update, the original page was not changed since the last translation. To force the creating translation check the Force page timestamp checkbox at the Service tab on the Avilinga Translation Connector configuration page.

The page contains no visible properties which are not translating.

To translate non-standard page properties please add them to the General section of the /content context in Translation Rules Editor. 

Avilinga get untranslatable content  when submitting i18n dictionaries for translation

We recommend using the custom Avilinga i18n translation workflow which supports JSON and sling dictionaries with i18n IDs as keys and as source language items. Please refer i18n translation manual.

Create translation project takes too long.

The most resource consumption part of creating a translation project in AEM Translation Integration Framework is preparing reference files for content to translate. You can disable this feature to speed up creating translation projects process.

Please contact us if you have any issues not listed above.

Page Title and Description are not updating

By default, AEM does not update page Title and Description on updating page translation. This issue can be solved by changing the exclude property for updating content. Please follow the next steps to change it:

1. Open CRXDE | Lite of your AEM instance and navigate to the /libs/msm/launches/rolloutconfigs/launch/contentUpdate node.

2. Double click on the cq.wcm.msm.action.excludedprops property to edit its value.

3. Replace jcr:.* value with jcr:(?!(title|description)$).*

4. Confirm by clicking on OK button and click Save All button at the top left corner of the screen.

Note: This property set initially to exclude all properties with names that start with jcr: from updating on Promoting page Launch. Changing this to recommended value will exclude all properties with names that start with jcr: but will leave jcr:title and jcr:description.Note: Best practice in AEM is to define customizations under /apps and to not change anything in the /libs path. But overlaying the /libs/msm/launches/rolloutconfigs/launch/contentUpdate node does not solve the problem with not updating Title and Description of the page. Therefore Avilinga Translation Connector provides option to force using /apps/msm/launches/rolloutconfigs/launch/contentUpdate node on Launch promotion.Note: If you have translated the page and figured out that Title and Description of the page are not updated, it is not necessary to create another update type job. After applying the changes described above, you can promote the latest Launch of the target language page and the fields will be updated.