<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Regex for allowedPaths to hide template after some levels level in Adobe Experience Manager Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462654#M133546</link>
    <description>&lt;P&gt;Template Availability -&amp;nbsp;&lt;/P&gt;
&lt;P&gt;AEM offers multiple properties to control the templates allowed under&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Sites&lt;/STRONG&gt;. However, combining them can lead to very complex rules that are difficult to track and manage.&lt;/P&gt;
&lt;P&gt;Therefore, Adobe recommends that you start simple, by defining:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;only the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;property&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;only on the site root&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For an example, see We.Retail:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;/content/we-retail/jcr:content&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;The properties&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;allowedPaths&lt;/CODE&gt;,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;allowedParents&lt;/CODE&gt;, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;allowedChildren&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;can also be placed on the templates to define more sophisticated rules. However, when possible, it is&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;much&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;simpler to define further&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;properties on sub-sections of the site if there is a need to further restrict the allowed templates.&lt;/P&gt;
&lt;P&gt;An additional advantage is that the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;properties can be updated by an author in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;tab of the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Page Properties&lt;/STRONG&gt;. 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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The following properties determine whether a template&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;T&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;is allowed to be used for a new page to be placed as a child of page&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;P&lt;/CODE&gt;. Each of these properties is a multi-value string holding zero or more Regular Expressions that are used for matching with paths:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;property of the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;jcr:content&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;subnode of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;P&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or an ancestor of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;P&lt;/CODE&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Refer fore more details -&amp;nbsp;&lt;A href="https://experienceleague.adobe.com/docs/experience-manager-64/developing/platform/templates/templates.html?lang=en" target="_blank"&gt;https://experienceleague.adobe.com/docs/experience-manager-64/developing/platform/templates/templates.html?lang=en&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jul 2022 06:08:36 GMT</pubDate>
    <dc:creator>tusharbias</dc:creator>
    <dc:date>2022-07-26T06:08:36Z</dc:date>
    <item>
      <title>Regex for allowedPaths to hide template after some levels level</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462619#M133530</link>
      <description>&lt;P&gt;Hi Team,I have a template&amp;nbsp;&lt;STRONG&gt;(xyz),&lt;/STRONG&gt;&amp;nbsp;I want to hide this template after 4 levels from my project root content (mysite). let's say /content/mysite/dynamicvalue/dynamicvalue/dynamicvalue/dynamicvalue/&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please provide me regex for allowedPaths.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;bit urgent requirement, Thanks in advance&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2022 19:47:23 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462619#M133530</guid>
      <dc:creator>gskittu</dc:creator>
      <dc:date>2022-07-25T19:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: Regex for allowedPaths to hide template after some levels level</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462627#M133535</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="17557040"&gt;&lt;/LI-USER&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Try this,&lt;/P&gt;
&lt;PRE&gt;/content/mysite/([^/]*)/([^/]*)/([^/]*)/([^/]*)&lt;/PRE&gt;
&lt;P&gt;OR&lt;/P&gt;
&lt;PRE&gt;&lt;SPAN&gt;/content/mysite/(.*)/(.*)/(.*)/(.*)&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Santosh&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2022 20:52:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462627#M133535</guid>
      <dc:creator>SantoshSai</dc:creator>
      <dc:date>2022-07-25T20:52:07Z</dc:date>
    </item>
    <item>
      <title>Re: Regex for allowedPaths to hide template after some levels level</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462654#M133546</link>
      <description>&lt;P&gt;Template Availability -&amp;nbsp;&lt;/P&gt;
&lt;P&gt;AEM offers multiple properties to control the templates allowed under&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Sites&lt;/STRONG&gt;. However, combining them can lead to very complex rules that are difficult to track and manage.&lt;/P&gt;
&lt;P&gt;Therefore, Adobe recommends that you start simple, by defining:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;only the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;property&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;only on the site root&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For an example, see We.Retail:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;/content/we-retail/jcr:content&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;The properties&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;allowedPaths&lt;/CODE&gt;,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;allowedParents&lt;/CODE&gt;, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;allowedChildren&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;can also be placed on the templates to define more sophisticated rules. However, when possible, it is&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;much&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;simpler to define further&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;properties on sub-sections of the site if there is a need to further restrict the allowed templates.&lt;/P&gt;
&lt;P&gt;An additional advantage is that the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;properties can be updated by an author in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;tab of the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Page Properties&lt;/STRONG&gt;. 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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The following properties determine whether a template&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;T&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;is allowed to be used for a new page to be placed as a child of page&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;P&lt;/CODE&gt;. Each of these properties is a multi-value string holding zero or more Regular Expressions that are used for matching with paths:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;cq:allowedTemplates&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;property of the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;jcr:content&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;subnode of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;P&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or an ancestor of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;P&lt;/CODE&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Refer fore more details -&amp;nbsp;&lt;A href="https://experienceleague.adobe.com/docs/experience-manager-64/developing/platform/templates/templates.html?lang=en" target="_blank"&gt;https://experienceleague.adobe.com/docs/experience-manager-64/developing/platform/templates/templates.html?lang=en&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2022 06:08:36 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462654#M133546</guid>
      <dc:creator>tusharbias</dc:creator>
      <dc:date>2022-07-26T06:08:36Z</dc:date>
    </item>
    <item>
      <title>Re: Regex for allowedPaths to hide template after some levels level</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462657#M133549</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="11813833"&gt;&lt;/LI-USER&gt;&amp;nbsp;, Thanks for your reply, Your both regex are enabling template after 4 levels, but in my case I want to enable till 4th level and hide after 4th level&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2022 06:24:21 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/regex-for-allowedpaths-to-hide-template-after-some-levels-level/m-p/462657#M133549</guid>
      <dc:creator>gskittu</dc:creator>
      <dc:date>2022-07-26T06:24:21Z</dc:date>
    </item>
  </channel>
</rss>

