AEM Editable Templates, how to add properties such as allowedChildren, allowedParents, allowedPaths | Community
Skip to main content
Level 6
March 7, 2020
Solved

AEM Editable Templates, how to add properties such as allowedChildren, allowedParents, allowedPaths

  • March 7, 2020
  • 1 reply
  • 6414 views

I have seen documentation that only explains allowedChildren, allowedParents, allowedPaths as properties can be set on STATIC templates. How about editable templates. Where can I add these properties? Can it be done in Touch UI?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by BrianKasingli

Hey @supportmember,

I've tested this out myself, and It seems like the "allowedChildren" property is the only respected rule for editable templates, with templates that exist under the default repository structure of /conf/my-site/settings/wcm/templates/* (cq:template) nodes. Even the latest service pack 6.4.3.7, "allowedParents" and "allowedPaths" is not working as expected.

What does the "allowedChildren" property under the cq:Template node do? The value set should be the paths of a template that is allowed to be a child of this template.

If you wish to use editable templates with the "allowedChildren", follow the instructions below. 

  1. Configure cq:allowedTemplates:
    Within CRX/DE, In your site content structure of /content/my-site/jcr:content, add property of String[] cq:allowedTemplates to "/conf/my-site/settings/wcm/templates/.*". This will enable and allow all editable templates under the set path to be used on page creation under the path of /content/my-site. Since "allowedParents" and "allowedPaths" are not working as expected for editable templates, this may be the only way to enable editable templates for your site structure.
  2. Configure "allowedChildren":
    Within CRX/DE under /conf/my-site/settings/wcm/templates/templateA (should be a cq:Template), add the property of String[] allowedChildren to "PATH_OF_YOUR_TEMPLATE". The value set should be the paths of a template that is allowed to be a child of this template.

I hope this helps.

1 reply

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
March 8, 2020

Hey @supportmember,

I've tested this out myself, and It seems like the "allowedChildren" property is the only respected rule for editable templates, with templates that exist under the default repository structure of /conf/my-site/settings/wcm/templates/* (cq:template) nodes. Even the latest service pack 6.4.3.7, "allowedParents" and "allowedPaths" is not working as expected.

What does the "allowedChildren" property under the cq:Template node do? The value set should be the paths of a template that is allowed to be a child of this template.

If you wish to use editable templates with the "allowedChildren", follow the instructions below. 

  1. Configure cq:allowedTemplates:
    Within CRX/DE, In your site content structure of /content/my-site/jcr:content, add property of String[] cq:allowedTemplates to "/conf/my-site/settings/wcm/templates/.*". This will enable and allow all editable templates under the set path to be used on page creation under the path of /content/my-site. Since "allowedParents" and "allowedPaths" are not working as expected for editable templates, this may be the only way to enable editable templates for your site structure.
  2. Configure "allowedChildren":
    Within CRX/DE under /conf/my-site/settings/wcm/templates/templateA (should be a cq:Template), add the property of String[] allowedChildren to "PATH_OF_YOUR_TEMPLATE". The value set should be the paths of a template that is allowed to be a child of this template.

I hope this helps.

arunpatidar
Community Advisor
Community Advisor
March 9, 2020

@briankasingli  can you please try to add properties in initial instead of structure

Arun Patidar