Content fragment references on translation | Community
Skip to main content
R
randomtune
Level 2
October 21, 2021
Solved

Content fragment references on translation

  • October 21, 2021
  • 1 reply
  • 1483 views

Hello everyone, 

We are facing an issue while creating a language copy via a translation project with a page which references two different content fragments.

Scenario:

AEM 6.5.8

In Page C properties there are two references to two different content fragments.

Content Fragment A and Content Fragment B. The later references also Content Fragment A.

 

 

 

 

 

 

 

 

 


Added the following reference in the translation rules for the Content Fragment A reference:

 

assetNode with resource type resourceTypeC referenced as fragmentAReference

 

When a translation project is created, for example from en to de, and Page C is added, Page C and ContentFragment A are cloned under de and fragmentAReference in Page C properties gets updated. Working as expected.


Then add the next reference for Content Fragment B reference:

assetNode with resource type resourceTypeC referenced as fragmentBReference

 

Repeating the same translation process, now the previous rule for fragmentAReference is ignored.
Page C and Content Fragment B are cloned and fragmentBReference in Page C properties gets updated.

Does any one else run into this?
Is there any workaround?


Thanks in advance

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

Hi @randomtune ,

      Could you please raise the daycare for this issue.

  Its OOTB translation framework issue.

Kr,

Sanjay

1 reply

Sanjay_Bangar
Community Advisor
Sanjay_BangarCommunity Advisor
Community Advisor
October 21, 2021

Hi @randomtune ,

    Could you please try to create translation rule as template level means you need to add your page path.

Ex:

 <Node resource type =  /Content/testproject>

Content fragment translation true </nod>

 

 

 

 

 

    R
    randomtuneAuthor
    Level 2
    October 22, 2021

    Hello @sanjay_bangar,

    Thanks for your response

    Although I'm not sure I follow, do you mean to put those rules into a specific path context?

    The rules I was referring to are the following:

    <assetNode assetReferenceAttribute="fragmentAReference" resourceType="resourceTypeC"/>
<assetNode assetReferenceAttribute="fragmentBReference" resourceType="resourceTypeC"/>

    It doesn't look like it is possible to define them into a specific path context, it seems to be ignored.

    I tried also the following, but with the same result as in the original post:

     

    <node path="/content/testproject">
    <node resourceType="resourceTypeC">
        <property inherit="true" name="fragmentAReference" translate="true" updateDestinationLanguage="true"/>
        <property inherit="true" name="fragmentBReference" translate="true" updateDestinationLanguage="true"/>
    </node>
</node>
<assetNode assetReferenceAttribute="fragmentAReference" resourceType="resourceTypeC"/>
<assetNode assetReferenceAttribute="fragmentBReference" resourceType="resourceTypeC"/>

    Thanks

     

     

     

     

      Sanjay_Bangar
      Community Advisor
      Sanjay_BangarCommunity AdvisorAccepted solution
      Community Advisor
      October 22, 2021

      Hi @randomtune ,

            Could you please raise the daycare for this issue.

        Its OOTB translation framework issue.

      Kr,

      Sanjay

        Terms & ConditionsAccessibility statement

        Loading footer...