Hi @renan_rsy, thanks for the extra info Short answerNo, unfortunately what you want to do is not possible.Long answerIf you observe the node structure of your template policy definitions, you can see how the existing design of template policies makes extending them impossible. In order to illustra...

Hi,I'd like to help you but I'm not sure I understand the problem. What do you mean by:"component policies" - Policies are note defined at the component-level but are assigned to components at the template-level, so I'm a bit confused."App Container" - Is this a Layout Container that accepts only on...

Hi,What did you do to try and activate Scaffolding mode?Making the Scaffolding mode appearGo to the Classic UI: http://localhost:4502/libs/cq/core/content/welcome.htmlIn the menu on the left select ToolsIn the node tree to the left select Default Page Scaffolding > Default Page ScaffoldingClick on N...

Hi, I also strongly suggest using LDAP to synchronize all your users and groups (you could apply this to your Author instances and your Publishers).Just one question though: you need to sync your users and groups but what about their access rights? Is that also a concern?

Delegation is not inheritanceHTL can only access value exposed by conventionally named getters and setters. If your PageHeadLine does not expose those one way or another, then you will not be able to access those properties in your HTL template (same principle for the JSON export).Since your PageHea...

For anyone who comes across this in the future:Apparently this is the desired behaviour of the component, according to an answer I got to an Adobe DayCare ticket

Hi all, I've been asked by business to fix the AEM Forms Document Fragment component. The issue is the following:@As long as the component is not given an assetPath (in the Document Fragment Reference field), it displays as a single line of red text reading "There was an error resolving Document Fra...