CF references in Content Fragments do not automatically adjust to match the language of the copy

This article explains how to solve the issue where CF (Content Fragments) references in Content Fragments do not automatically adjust to match the language of the copy. This can be resolved by changing the Translate Content Fragment Assets option from Do not translate  to Inline Media Assets and Associated Collections.

Description description

Environment

Adobe Experience Manager (AEM)

Issue/Symptoms

CF references in Content Fragments do not automatically adjust to match the language of the copy.

For Example:

Here is a Content Fragment: https://author-pXXXXX-eYYYYYYY.adobeaemcloud.com/ui#/aem/editor.html/content/dam/wknd-shared/en/test_1, which references CF /content/dam/wknd-shared/en/contributors/richard-roe.

A language copy of the first Content Fragment (CF) created under this link must be made. However, the referenced CF is still pointing to /content/dam/wknd-shared/en/contributors/richard-roe instead of the correct path, which should be /content/dam/wknd-shared/nl/contributors/richard-roe.

Resolution resolution

After reviewing the translation configurations, it was found that the error was caused by the global translation configuration, which for assets had the Translate Content Fragment Assets option set to Do not translate.

Refer to the image below to see that after changing the option to Inline Media Assets and Associated Collections, the referenced CFs were correctly updated to the appropriate language folder.

Related reading

Configuring a Translation Integration Framework in the AEM as a Cloud Service (AEMaaCS) User Guide.