I see all my static templates while creating experience fragment. Checked the property cq:allowedTemplates on /content/experience-fragments, it contains
Only conf and libs templates should be shown while creating template as per the above config but I am seeing all the static template that resides inside /apps folder. Basically I would want to stop showing static templates that resides on /apps folder. Is there any other config to make this happen?
Try to use allowedPath property-
Thanks for your reply. allowedPath is not working at /content/experience-fragments level but it worked when I change regulr expression at the static tempalte level. making this change at 20+ template may not be a correct approach. Why cq:allowedTemplates & allowedPath props are not working at ef level? Is this a bug?
@Anderson_Hamer - I am also facing the similar issue. Can you please let me know if making the changes at static template level fix the issues with the allowed Templates policy at /content/experience-fragments level? if so, can you tell me what should I use in static template allowedPath (Regular Expression)?
I guess it is a product bug. Issue exists since 6.4.4. Adobe had made some changes in 6.4.4 as per SP release notes and it would have impacted.
Ideally it should show only the XF templates which is configured in cq:allowedTemplates not the static page templates which is mentioned with allowedPaths-String-/content(/.*)? property