


hi ,
I have a component which uses an reference component embedded inside the main component. I am using AEM 6.5 .
<sly data-sly-resource="${'experiencefragment' @ resourceType='cq/experience-fragments/editor/components/experiencefragment'}"></sly>
I need to define default values to the fragmentPath inside the experience fragment. I tried using the approach provided under
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/default-value-in-reference... , i.e using cq:template and cq:templatePath approach and it fails .
STEPS :
1. Created a node inside the component of type nt:unstructured called cq:template. Added a property called fragmentPath of type String to it with default value for XF path.
2. Created a sling:folder outside the component called templateConfigs, created node of type nt:unstructured inside it called experienceFragment . Added a property to it called fragmentPath of type String. Then added a property to component called cq:templateType (String) and added path of the new config as its value.
Both above approaches did not work. Please help.
Thanks,
Samiksha,
Views
Replies
Sign in to like this content
Total Likes
Hi @samikshaa223429,
@arunpatidar beat me to the punch 😉 But his answer is correct! One thing to know is that the value is cq:template are set when a component is created. That means if you placed your component on the page, then modified the cq:template values, you would have to remove and add the component again to see the changes, maybe that is your problem? 🙂
Other things to look out for:
Here's a quick GIF to prove it works:
Create a node inside the component of type nt:unstructured called cq:template. Add a child node experiencefragment type of nt:unstructured and add a property called fragmentPath of type String to it with the default value for XF path.
hi Arun ,
The solution shared by you didnt work . XF is still not picking up the default value.
Views
Replies
Sign in to like this content
Total Likes
Hi @samikshaa223429,
@arunpatidar beat me to the punch 😉 But his answer is correct! One thing to know is that the value is cq:template are set when a component is created. That means if you placed your component on the page, then modified the cq:template values, you would have to remove and add the component again to see the changes, maybe that is your problem? 🙂
Other things to look out for:
Here's a quick GIF to prove it works:
Views
Replies
Sign in to like this content
Total Likes
Views
Replies
Sign in to like this content
Total Likes
Views
Replies
Sign in to like this content
Total Likes
Views
Replies
Sign in to like this content
Total Likes