Restrict components inside components - Touch UI
Are you referring to container components like a grid. Typically a parsy is the component where you drop other components.
The best way to handle which components are allowed to be dropped on a page is use of an editable templates and setting policies. When you set a policy in an editable template - you can define which components are allowed there. See this AEM Article and see how policies are set.
Creating an Adobe Experience Manager project using Lazybones
For example, notice you can select the components that are allowed in the policy.
I solved it.
Sorry for NOT writing out the problem in the way it is required.
version used is 6.2 - so I am not sure what do you mean by static templates or non editable templates. anyways my question was more around the design level config that we write for each templates in etc/designs.
In our application, this particular property "components" was not working and only the "components" property set at the top most level of the template was working. The question was not about template level restriction of components and policies; it was about what components need to be allowed inside another component across the application. In this case it is a custom component and yes something like a container component like parsys heaving used across application.
I was able to fix this by rearranging nodes in the order that the rules for all the components (that could be part of the template potentially) falls under the node that represents the template. (Pretty dirty fundamental flaw; i admit it. but I wonder how this was working in local and not in stage. ideally it should not have worked in local too.)
Yes maven build filter is set in a way that these changes are cascaded thru builds.
I solved it.
Sorry for NOT writing out the problem in the way it is required.
version used is 6.2 - so I am not sure what do you mean by static templates or non editable templates. anyways my question was more around the design level config that we write for each templates in etc/designs.
In our application, this particular property "components" was not working and only the "components" property set at the top most level of the template was working. The question was not about template level restriction of components and policies; it was about what components need to be allowed inside another component across the application. In this case it is a custom component and yes something like a container component like parsys heaving used across application.
I was able to fix this by rearranging nodes in the order that the rules for all the components (that could be part of the template potentially) falls under the node that represents the template. (Pretty dirty fundamental flaw; i admit it. but I wonder how this was working in local and not in stage. ideally it should not have worked in local too.)
Yes maven build filter is set in a way that these changes are cascaded thru builds.
Related Conversations
