I have contaner component, for that container I need allow few list of components, for that I have created a component with cq:designDialog with allowed component. in html I added parsys below are the files.
cd:designDialog
HTML
component.xml
cq:policy of my component
but whenever try to add allowed components components on page through that parsys, I didn't see any allowed components
any help to fix this
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @Anilkumar9
You need to reference the policy in the template
Example:
Above Policy used in Template :https://github.com/arunpatidar02/aemaacs-aemlab/blob/e31fc62bfd147e56ecaca740c6e2739c66c75f75/ui.con...
Hi @Anilkumar9,
It’s possible the policies haven't been properly deployed or linked.
Please try the following steps:
Verify if the policies are deployed on your instance via CRXDE Lite at /conf/your-site/settings/wcm/policies/....
Check if your container component's policy exists.
Make sure the policy path is correctly referenced in the component via cq:policy.
If the policy is missing or not working:
Delete all the policies under your site config (/conf/your-site/settings/wcm/policies/...).
Rebuild or redeploy the template/policy structure to reset them.
Also ensure your filter.xml includes the policies and template-types nodes so they're deployed from your codebase to AEM.
Sometimes, even if everything looks correct, the UI won’t show allowed components unless the policy linkage is established properly in CRX.
Hi @Anilkumar9
You need to reference the policy in the template
Example:
Above Policy used in Template :https://github.com/arunpatidar02/aemaacs-aemlab/blob/e31fc62bfd147e56ecaca740c6e2739c66c75f75/ui.con...
Hi @Anilkumar9 ,
According to my understanding, In Editable Templates, cq:designDialog is ignored, so your allowed-components setup won’t work. Instead, you must define allowed components via the Template Editor's policies. I think you can try to configure allowed components using the Editable Template’s policy editor.
@Anilkumar9 Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!
Views
Replies
Total Likes
Views
Likes
Replies