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?
EM offers multiple properties to control the templates allowed underSites. However, combining them can lead to very complex rules that are difficult to track and manage.
Therefore, Adobe recommends that you start simple, by defining:
only on the site root
For an example, see We.Retail:/content/we-retail/jcr:content
The propertiesallowedPaths,allowedParents, andallowedChildrencan also be placed on the templates to define more sophisticated rules. However, when possible, it ismuchsimpler to define furthercq:allowedTemplatesproperties on sub-sections of the site if there is a need to further restrict the allowed templates.
An additional advantage is that thecq:allowedTemplatesproperties can be updated by an author in theAdvancedtab of thePage Properties. The other template properties cannot be updated using the (standard) UI, so would need a developer to maintain the rules and a code deployment for every change.
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)?