Hi,
We are using AEM 6.1 with SP2.
When cancelling inheritance on a component, the child nodes are not being cancelled, which ends up overriding data during rollout. According to the documentation - https://docs.adobe.com/docs/en/aem/6-1/develop/platform/custom-nodetypes.html#cq:LiveSyncCancelled - there is an additional boolean property called cq:isCancelledForChildren. Looking at the form that is posted to Sling when cancelling inheritance this form data is being sent:
Where is this property being set/read from? How can we change that property?
When adding cq:isCancelledForChildren = true manually to the component jcr:content node and then rolling out, the changes are NOT being overwritten. But when re-enabling inheritance or cancelling this property is being removed.
Any help with why this is happening and how we can avoid this, is greatly appreciated.
Thanks, Alex
Views
Replies
Total Likes
Hi,
Have you seen the below thread?
please check if you found the same issue.
- Prince
Views
Replies
Total Likes
@Prince Shivhare, the link is broken
Views
Replies
Total Likes
Can someone provide the correct link for the above?
Views
Replies
Total Likes
So it works when you manually set the cq:isCancelledForChildren property?
Views
Replies
Total Likes
yes smacdonald2008, it works after manually breaking the inheritance of the parent component and then child components and then deleting the child components which sets the cq:isCancelledForChildren property, but why do we need to do this manual work? Shouldn't the canceling the inheritance from a parent should also automatically cancel the inheritance for the child nodes as well? Is this is a bug in the system or is there a reason for it?
Views
Likes
Replies
Views
Likes
Replies