The problem we faced is that when you use rollout config with the "modification" cq:trigger, for example, default "Push On Modify", delete page action stops working correctly when you create Live Copy of a master page. It stops producing "contentDelete" LiveSync action (page event) and does not roll out anything if there is at least one separate ad-hoc Live Copy page of this changed blueprint page.
It behaves the same for default We-Retail installation. You can test it with the default "Push On Modify" Rollout Config or create a new one with cq:trigger="modification" and "contentDelete" LiveSync action.
Actually, we use "modification" -> "contentDelete", because we need to delete all Live Copy pages after a blueprint page was removed.
Automatical removing (rolling out) of live copies with such config works until you click on a master page and use "Create" -> "Live Copy" button. Then it stopped working and didn't work even if you remove that newly created live copy page.
Log output is: "MSM does only deal with Blueprint Resource /path/to/my/page/resource: ignore". But the resource was actually a blueprint !!!
This functionality worked perfectly in AEM 6.2 and stopped working after it was upgraded to 6.4.
Removing of pages using "Standard Rollout Config" and "Rollout with children" button is working, but we can't use it because we have a huge lot of pages.
I tried to debug the process and found out that after you create ad-hoc Live Copy, event processed by MSMEventProcessor class contains a path with a changed (deleted) page, and this change is already saved into a repository (if there are no ad-hoc live copies, the event points to an existing resource). And it stays the same even if you delete those live copies. But, if you delete Live Copy and then restart AEM, the rollout configuration starts working, event resource becomes existing then there.
Does somebody know which way it can be fixed or what we can use instead of these rollout configs for deleting pages in 6.4?
(Updated. Other LiveSync actions except deletion should work because resource exists there). Message was edited by: Yuriy Shestakov
Ok, here is a copy from my DayCare ticket. Here I am using "Publish on Modify" rollout config, but, as I said previously, you can create your own or delete all actions from this config (leave only contentDelete) - and it will work the same.
Hope it will help you reproduce it.
Upd: It is not like test content, but you can reproduce the problem using AEM OOB installed with sample content, so don't need any custom package.