You have to create your own (`nt:unstructured`) nodes tree somewhere in the repo, for example, `/apps/my-migration-project/rules`, and create there all the rule definitions you need as children. The OSGi configuration file for the ComponentRewriteRuleServiceImpl I believe should be placed somewhere ...
Hi! If I am not mistaken, there's nothing that you can do with the translation projects However, you can archive old translation jobs.So you can create one translation project, then always add new jobs to it instead of creating a new project, then archive those jobs once the translation work is fi...
Hi guys! The Adobe public repo (http://repo.adobe.com/) isn't accessible since yesterday (04.Feb.2020).Could you please address the problem or provide an ETA when it will be resolved? Thank you!
Daycare accepted this behavior as somehow unexpected and answered that this problem can be a result of already known AEM bug CQ-4258705, waiting for fixing it.
The problem here is when you have two rollout configs "On Modification" -> "ContentDelete" and "On Rollout" -> "Content Update" manual (standard) rollout process doesn't work because "On Modification" -> "ContentDelete" marks all pages as synchronized after any update. And when you try to do manual ...
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 ...
They said if we use "modification" trigger, the result of the action is not determined. So, they suggested not using it. Don't know what to do.And nothing like this noticed in the official documentation
When we tested default "Push on Modify" - we didn't change anything in it,when we created our new one, we used just one element - "contentDelete".So, the order doesn't matter.Or are you saying about other elements? Please clarify, what order do you mean?
Hello everybody!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) a...