What AEM version are you using. Also what multifield granite type are you using.
I can only imagine the case that you have a strange MSM rollout config, which is triggered by any change. Do this happen only on MSM livecopies? What happens if you author MSM blueprints?
These properties are populating after rollout, so blueprint page it self do not have these properties.
ok, this behavior is affecting only the livecopies? Have you broken the MSM inheritance to perform changes via UI? Or are you just doing the changes via CRXDE?
I agree with Jorg. I also feel this is caused due to something in the MSM configurations. Do you have any custom roll out configs which might be affecting this ?
Hey @Jörg Hoh
We have hierarchy like Blueprint > Source Pages > LiveCopies , and this behaviour is for both source pages and livecopies. As "jcr:mixinTypes" property is getting added after rollout from blueprint to source pages or from source pages to livecopies, so "jcr:mixinTypes" only exist on source pages or livecopies, not on blueprint page.
Yes we are broking the msm inheritance to perform changes via UI.
Do I understand you right that you have a 2-level MSM Inheritance
Level 1: blueprint 1 -> Livecopy 1 (you call it "source pages")
Level 2: Livecopy 1 -> Livecopy 2
Is that correct? Can you reproduce this behavior on both Level 1 and Level 2? Or only on a single one of them?
I experienced some weirdness when you use multiple inheritance levels and combine it with "unusal" rollout actions and triggers (maybe even custom ones). There might be assumptions made in an rollout action which cannot handle the case that a livecopy is also a blueprint.
For this case I would be good if you check the triggers and rollout actions on both Level 1 and Level 2 (see above).