Sometimes you might encounter the issue that your projects are not created properly on the XTM Cloud side. The following error is displayed in the AEM CMS:

Open

One of the possible reasons for this is an invalid tree structure. This article provides a detailed explanation of such behavior and suggests a solution.

In most cases, the content of the translation language you are attempting to send is a LIVE Copy.

When you create a Live Copy, its configuration is saved on the root page of the copied pages (a Live Copy can contain more than one page). All child pages of the root page inherit the Live Copy configuration. The components (content) on the Live Copy pages also inherit the Live Copy configuration from their original source (the file from which the Live Copy page was created, in the relevant <language-master sub-folder> (identified by a language code). More information here: Reusing Content: Multi Site Manager and Live Copy | Adobe Experience Manager.

When you create a language copy for a Live Copy, you use so-called “Launches” for translation.

However, when you create a project from the Live Copy, it is necessary to point to every page individually. If you only pick a parent path and include children, this will not work correctly, meaning that a language copy will not be created.

When the project is created (but not yet sent to XTM Cloud), it creates the path to that language copy already. When the content is translated, this updates the pages that were sent with the correct target language.

If the language copy exists, the project will be sent through references because you are updating it: Managing Translation Projects | Adobe Experience Manager.

AEM detects whether an XTM Cloud project is created for initial translation of the content OR for update of already-translated language copies. When you create the project for a page and specify the language copies for which you are translating, AEM detects whether the source page already exists in the target language copies:

• Language copy DOES NOT include the page: AEM treats this situation as an initial translation. The page is immediately copied to the language copy and included in the XTM Cloud project. When the translated page is imported back into AEM, the CMS copies it directly to the language copy.

• Language copy INCLUDES the page: AEM treats this situation as an updated translation. A Launch is created and a copy of the page is added to the Launch and included in the project. Launches enable you to review updated translations before committing them to their language copy:

  • When a translated page is imported back into AEM, it overwrites the page in the Launch.

  • The translated page only overwrites the language copy when the Launch is promoted.

Either way, when you update the language copy, you should choose the original source language page. You can later select Language Copies and then select the language copies for which you are translating the source pages.

Open