Hi there,
I am trying to customise the authoring experience of child components in my component by adding a _cq_childEditConfig.xml file to it with the following XML:
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root
xmlns:cq="http://www.day.com/jcr/cq/1.0"
xmlns:jcr="http://www.jcp.org/jcr/1.0"
jcr:primaryType="cq:EditConfig"
cq:actions="[]"/>
The presence of this config doesn't appear to affect the authoring experience of child components in any way; I am trying to remove all actions from them with no success.
In addition to that, it also removes all actions and the blue border from my component. Even if I remove the cq:actions attribute from the config this is still the case.
Can anyone tell me if this is broken? Or am I simply using it incorrectly? Any suggested workarounds for having different behaviour for child components would be very well recieved indeed.
Many thanks,
Dave
Views
Replies
Total Likes
If childconfig missing actions it will inherit from parent component config. Out of the box no option to disable for childconfig. It is working as designed and need some customization at project level to work as per your requirement. Or file an official request for product enhancement.
Views
Replies
Total Likes
foundation/components/iparsys would be a good reference to identify any configuration miss. It has childEditConfig node through which it inherits cq:actions to child component dragged in iparsys container.
Views
Replies
Total Likes