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

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

Avatar

Avatar
Validate 1
Level 2
kishorek1264980
Level 2

Likes

6 likes

Total Posts

44 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back
Boost 5
View profile

Avatar
Validate 1
Level 2
kishorek1264980
Level 2

Likes

6 likes

Total Posts

44 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back
Boost 5
View profile
kishorek1264980
Level 2

28-07-2020

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
Nupur_Jain
MVP

Likes

165 likes

Total Posts

186 posts

Correct Reply

76 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Establish
MVP
Nupur_Jain
MVP

Likes

165 likes

Total Posts

186 posts

Correct Reply

76 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 25
View profile
Nupur_Jain
MVP

28-07-2020

Hi @kishorek1264980 

 

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

Answers (2)

Answers (2)

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

232 likes

Total Posts

294 posts

Correct Reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

232 likes

Total Posts

294 posts

Correct Reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

28-07-2020

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

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/while-creating-an-experien...

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

232 likes

Total Posts

294 posts

Correct Reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

232 likes

Total Posts

294 posts

Correct Reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

28-07-2020

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