Unable to Translate Topics from AEM Guide: Missing Elements Node in jcr | Community
Skip to main content
S
SonaliSa3
October 25, 2024
Question

Unable to Translate Topics from AEM Guide: Missing Elements Node in jcr

  • October 25, 2024
  • 2 replies
  • 893 views

Hello All,

I’m facing an issue when attempting to send Topics created in AEM Guide for translation. Here’s a breakdown of the situation and the errors encountered, along with some observations:

 

Issue Summary:
When trying to translate Topics created directly in AEM Guide, the workflow fails, producing errors related to missing nodes and XML processing. Specifically, the Elements node is absent in the jcr:content of these Topics, which might be impacting the translation workflow.

Error Details:
During the translation process, these are some of the errors I’m seeing:

1. Error Loading Destination Language:

com.day.cq.dam.commons.util.DamLanguageUtil Failed to load destination language from payload

2. XML Processing Error:

com.adobe.fmdita.exception.ApplicationException: Failed to process XMLNode with path 
/content/dam/projects/translation_output/.../Training.dita/jcr:content/elements does not exist.

This `PathNotFoundException` suggests that the translation job is looking for an `elements` node that isn’t present in `jcr:content`.

 

Observations:

  • When I create Topics directly in AEM Guide, the Elements node is missing from jcr:content in CRX de.
  • Other content types or translated assets seem to include this node by default, which makes me suspect it’s required for the translation workflow (e.g., MergeXML) to process successfully.

 

Steps Taken:

 

  • I checked the source and target paths in the repository to confirm that other nodes are intact.
  • Manually adding the `Elements` node resolves part of the issue, suggesting this node may be necessary.
  • Reviewed workflow and translation job configurations, and they appear to be set up as expected.

 

 

Questions:
1. Is the Elements node mandatory in jcr:content for Topics to translate successfully in AEM Guide?
2. Has anyone encountered similar issues when translating Topics, and if so, what solutions or configurations worked for you?
3. Are there best practices to ensure the `Elements` node is automatically included for Topics created in AEM Guide?

 

Any insights, advice, or similar experiences would be much appreciated! Thank you in advance for your help.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

DivrajSingh
Adobe Employee
DivrajSinghAdobe Employee
Adobe Employee
October 28, 2024

@sonalisa3 : I assume you are trying translation with machine translation; and the destination/target language is from the list of available languages.

 

In order to confirm if your setup/configurations are right, I request you to go through this expert session video [check time duration 17:00 - 27:00]. 

You need following pre-requisites at a high level:

  1. A working translation cloud service config
  2. Language folders are setup
  3. Translation config is configured on the root language folder in AEM DAM
  4. component based translation configuration is setup to map to the translation type you are using (human/machine)

 

 

    S
    SonaliSa3Author
    November 15, 2024

    I have completed all the necessary setups, but the translation  is working intermittently. Additionally, the element node is missing for topics and maps, which might be causing issues. During the translation process, only the title of the topic gets translated, while the rest of the paragraphs remain untranslated.
    Wherever the elements node is present, the content gets translated.

    2/2
     

     

     

    .

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    July 2, 2025

    @sonalisa3 Just checking in — were you able to resolve your issue?
    We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...