The myPage page was created using the author environment.The mySubPage content on myPage is the result of adding a custom component from the sidekick to the myPage parsys, also using the author environment.

Good day,I've come across a rather "odd" structure in the content tree of my current project. One of the pages under /content has another page in it's jcr:content node. This child page has it's own jcr:content node. So it looks like this:/content/myPage (jcr:primaryType: cq:Page)/content/myPage/pars...

Ignore my previous comment. It turns out we have a custom piece of code that is responsible for this functionality.I now understand how it works and am able to use it properly.Thanks for the help!

I've found that if I disable CUG roots and remove ACL's, yet keep the "cq:cugEnabled" set to true and "cq:cugPrincipals" set to an array of roles, that the page for which those CUG's are set is still only accessible for who have the roles specified in "cq:cugPrincipals". How is it possible that even...

I have now disabled the CUG roots, but I don't notice any change in functionality. I can still configure closed user groups for pages and still only users with the roles described in the "cq:cugPrincipals" have access. Shouldn't this stop working?Sven

Good day,While figuring out the right way to configure closed user groups for my AEM 6.0 publisher, I came across the option to enable/disable CUG roots (in the OSGI configuration of component com.day.cq.auth.impl.cug.CugSupportImpl). At the moment, the CUG roots option is enabled.I'm having trouble...

Good day,I'm experiencing a "problem" with the AEM publisher, that I can't figure out. Every time the AEM 6.0 publisher is restarted, rep:policy nodes are created for all parsys nodes in the /content/* directory with properties "cq:cugEnabled" set to true and "cq:cugPrincipals" containing a string a...