Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

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

Avatar

Community Advisor

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.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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

6 Replies

Avatar

Community Advisor

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

Avatar

Level 1
No. It is working fine in 6.4.0 instance. Issue is happening only from 6.4.4.

Avatar

Correct answer by
Community Advisor

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

Avatar

Administrator
To double check on this, I would recommend creating a support ticket.


Kautuk Sahni