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
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

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

kishorekumar14
Level 8
Level 8

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.

AEM 6.4 AEM 6.4.7 allowedpaths allowedtemplates Experience Fragments Templates
1 Accepted Solution
Nupur_Jain
Correct answer by
Community Advisor
Community Advisor

Hi @kishorekumar14 

 

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 solution in original post

6 Replies
Shashi_Mulugu
Community Advisor
Community Advisor

@kishorekumar14 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?

ishore1494kumar
Level 1
Level 1
No. It is working fine in 6.4.0 instance. Issue is happening only from 6.4.4.
Nupur_Jain
Correct answer by
Community Advisor
Community Advisor

Hi @kishorekumar14 

 

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 solution in original post

kautuk_sahni
Community Manager
Community Manager
To double check on this, I would recommend creating a support ticket.