allowedTemplates property is not working as expected (Experience Fragment) | Community
Skip to main content
V
v1101
New Participant
August 25, 2020
Solved

allowedTemplates property is not working as expected (Experience Fragment)

  • August 25, 2020
  • 2 replies
  • 2421 views

Hello Community - It looks like cq:allowedTemplates is not working in 6.5.x as expected. We are trying to restrict the templates for experience fragments. Tried updating the property in /content/experience-fragments folder but no luck. We see all static templates as well after updating the property. We just wanted to restrict all other templates while creating experience fragments. Can someone assist on this issue?

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 vish.dhaliwal

Hello,

 

You should set property inside /content/experience-fragments/<customer_folder>/cq:allowedTemplates instead of /content/experience-fragments/, otherwise the values will get overridden on SP upgrade.

Check section "Creating and Configuring a Folder for your Experience Fragments" here [1]

[1] https://docs.adobe.com/content/help/en/experience-manager-64/authoring/authoring/experience-fragments.html#configure-allowed-templates-instance

Regards,

Vishu

2 replies

vanegi
vanegi
Employee
August 25, 2020

Hello @v1101,

Allowed templates for experienced fragments should be set for XF root folder, for example at /content/experience-fragments.

You need to define cq:allowedTemplates property as String[] and set all available templates there, example:

/libs/cq/experience-fragments/components/experiencefragment/template

/conf/we-retail/settings/wcm/templates/experience-fragment(.*)?

 

You need to add experience fragment template in the allowed templates (cq:allowedTemplates = /conf/test-project/settings/wcm/templates/experience-fragment) instead of allowedPaths on the /content/experience-fragments/<project>.

 

Thanks!!

    V
    vish.dhaliwalAccepted solution
    Employee
    August 25, 2020

    Hello,

     

    You should set property inside /content/experience-fragments/<customer_folder>/cq:allowedTemplates instead of /content/experience-fragments/, otherwise the values will get overridden on SP upgrade.

    Check section "Creating and Configuring a Folder for your Experience Fragments" here [1]

    [1] https://docs.adobe.com/content/help/en/experience-manager-64/authoring/authoring/experience-fragments.html#configure-allowed-templates-instance

    Regards,

    Vishu

      V
      v1101Author
      New Participant
      August 25, 2020
      @vish.dhaliwal - Thanks for the inputs.I have already tried this suggestion but it is not working. Do you think of any other solution ?
      Terms & ConditionsAccessibility statement

      Loading footer...