Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

CF Not getting attached For Translation

RG_AEM
Level 2
Level 2

I have a Custom Component with a path browser to the CF's . However when I send this component for Translation the content Fragment that is being referred does not attach to the project for Translation. I have defined the rules in the below in the config file but it does not seem to work. Any pointer on how this can be resolved.

<assetNode assetReferenceAttribute="component node property reference to CF " resourceType="path to custom component"/>
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

4 Replies
RG_AEM
Level 2
Level 2
Hi @ammbra, Hi , This seems be working when using the OOTB component but I have a custom component which has a path browser to CF's and this fragment does not get attached. The article mentions to you the resourceType of my custom Component but I don't have one defined since this is custom component and does not inherit OOTB CF through sling:resourceType
AkAgarwal
Level 1
Level 1

Hi @RG_AEM ,


Can you try by adding this translation rule in "/libs/cq/translation/translationrules/contextproperties.html?context=/content" so that it will unblock CFs for translation.

Resource Type : core/wcm/components/contentfragment/v1/contentfragment
Reference as : fragmentPath

As per this article there are some translation rules which can be edited..

"https://experienceleague.adobe.com/docs/experience-manager-learn/sites/content-fragments/content-fra...

Please check if it helps!

Regards,
Ak$hit Agarwal


RG_AEM
Level 2
Level 2

Hi , @AkAgarwal  This seems be working when using the OOTB component but I have a custom component which has a path browser to CF's and this fragment does not get attached.