Experience Fragments cq:allowedTemplates is not restricting the static page templates in 6.4.7 | Community
Skip to main content
Kishore_Kumar_
Kishore_Kumar_
Level 9
Jul 28, 2020 3:20 PM UTC
Solved

Experience Fragments cq:allowedTemplates is not restricting the static page templates in 6.4.7

hi team,

 

Can anyone confirm on this please. Thanks in advance.

 

From the XF Console http://localhost:4508/aem/experience-fragments.html/content/experience-fragments created one folder and added cq:allowedTemplates-String[]-/conf/we-retail/settings/wcm/templates/experience-fragment-web-variation Property to it, and from that folder tried to create one XF. On clicking Create -> Experience Fragments, ideally it should show only Experience Fragment Web Variation template but it is showing static page templates as well which has allowedPaths property ( allowedPaths-String[]-/content(/.*)?). 

This issue didn't occur in 6.4.0 but occurring in 6.4.7 SP.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Nupur_Jain
Nupur_JainAccepted solution
Employee
Jul 28, 2020 5:31 PM UTC

Hi @kishore_kumar_ 

 

If you look in the release notes from https://docs.adobe.com/content/help/en/experience-manager-64/release-notes/sp-release-notes.html for 6.4 service pack. There is some fix included related to cq:allowedPaths. This might be the reason that you are encountering different functionality.

 

Hope it helps!

Thanks!

Nupur

View reply

6 replies

Shashi_Mulugu
Shashi_Mulugu
New Participant
Jul 28, 2020 5:35 PM UTC

Seems like a product bug. Please follow the below community post.

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/while-creating-an-experience-fragment-other-templates-not-only/qaq-p/366231

Translate
    Nupur_Jain
    Nupur_JainAccepted solution
    Employee
    Jul 28, 2020 5:31 PM UTC

    Hi @kishore_kumar_ 

     

    If you look in the release notes from https://docs.adobe.com/content/help/en/experience-manager-64/release-notes/sp-release-notes.html for 6.4 service pack. There is some fix included related to cq:allowedPaths. This might be the reason that you are encountering different functionality.

     

    Hope it helps!

    Thanks!

    Nupur

    Translate
      kautuk_sahni
      kautuk_sahni
      Employee
      Jul 29, 2020 1:48 PM UTC
      To double check on this, I would recommend creating a support ticket.
      Translate
      Kautuk Sahni
      Shashi_Mulugu
      Shashi_Mulugu
      New Participant
      Jul 28, 2020 5:11 PM UTC

      @kishore_kumar_ Based on data you provided, issue should occur nevertheless of AEM version since allowedPaths-String[]-/content(/.*)?) This itself means to show/allowed to create page/xf any where inside /content .

       

      Can you please confirm?

      Translate
        ishore1494kumar
        New Participant
        Jul 28, 2020 5:17 PM UTC

        .

        Translate
        Terms & ConditionsAccessibility statement

        Loading footer...