Language copy reference updates issue with Experience Fragments associated on page during Translation job creation

[mayank-saxena1987]

For the thread -https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/language-copy-issue-with-e...
I see in replies section - This issue is resolved in the AEM 6.5 Service Pack 12 (NPR-37953).

We are using AEM version 6.5.16.0 but we still see the same issue.
No experience fragments associated on the pages are getting added/ or reference updating on the language copy pages.
Is there any else configuration is required to add? We have translation rules configured as well but still no luck.

Also I tried with adding one more process step to WCM: Translate Language Copy workflow to translated experience fragment links but this workflow never triggered while creating translation job and adding pages from Project Console and Create option under Sites console.

Please help.

[salamswapnil]

Hi @mayank-saxena1987 

To fix this issue you have to add below translation rule in your translation_rules.xml.

<node resourceType="myproject/components/content/experiencefragment">
    <property name="fragmentVariationPath" translate="true"/>
</node>

[mayank-saxena1987]

Even all rules are configured + Experience fragment component is added within rules. Still translation of fragment and reference updating is not working. Language copy showing English fragment reference.

Please suggest.

[aanchal-sikka · Accepted solution]

Hello @mayank-saxena1987 

Requesting you to please cross-check /libs/settings/translation/rules/translation_rules.xml. Does it have following?

<assetNode resourceType="cq/experience-fragments/editor/components/experiencefragment" assetReferenceAttribute="fragmentPath"/>

Also, please assure if any override is created at location  /conf/global/settings/translation/rules/translation_rules.xml

[Harwinder-singh]

@mayank-saxena1987  You can create a custom Experience fragment renderer that is able to read the language node of a content tree and re-adjust references at run time. 

We had a similar situation with Live copy rollouts where the XF references from language master page were not getting replaced with the XF country variation on roll out. In that case we created a custom rollout config that was able to update the link references at run time during rollout.

The below blog does something similar to what I mentioned for XF rollouts.

https://bimmisoi.blogspot.com/2021/07/update-link-reference-inside-experience.html