Hi,
We are using MSM for managing multiple regional websites, we have 9 websites in total with respect to blueprint and we are using "push on modify", "activate on blueprint activation", "deactivate on blueprint deactivation". push on modify is very inconsistent over the pages, some times it sync with some of child pages and some times it doesn't(I am trying over same page again and again). We are using OOTB rollout configs.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Unrelated to your issue: I consider "push on modify" dangerous, because it can lead to a lot of rollouts, plus its associated overhead and performance impact.
That means especially if follow some strict authoring process, where changes on the blueprint are made, reviewed and eventually published, you have the overhead of rolling out any change on the blueprint to 9 live copies. Even if you would need that rollout only once after all changes have been approved.
Given your description, it might be related to the issue discussed in my blog post on resyncing a live copy language root to a blueprint.
Here are some steps and considerations that might help resolve your issue:
cq:LiveSyncConfig
Node ConfigurationOne common cause for the inconsistency in the synchronization is the missing or misconfigured cq:LiveSyncConfig
node. This node is crucial for managing the synchronization between the blueprint and live copies.
Check the cq:LiveSyncConfig
Node:
/content/<your-site>/jcr:content
.cq:LiveSyncConfig
node exists.Verify OOTB Rollout Configurations:
Manual Resync:
Review Logs:
Testing and Validation:
cq:LiveSyncConfig
Node:
For a detailed guide on resyncing a live copy language root to a blueprint, please refer to our blog post: How to Re-Sync a Live Copy Language Root to a Blueprint in AEM MSM.
If you follow these steps and ensure the cq:LiveSyncConfig
node is correctly set up, it may possibly help in resolving the inconsistencies you are facing.
Is there any pattern in terms of which type of modifications are successful/unsuccessful. Any info in logs when it fails?
Hi @BrianKasingli , there is nothing as such, it is very uncertain, I am just adding "." and removing them to test over same text again and again, some times it worked and some times it is not working, and I have not seen anything specific to msm in logs
Unrelated to your issue: I consider "push on modify" dangerous, because it can lead to a lot of rollouts, plus its associated overhead and performance impact.
That means especially if follow some strict authoring process, where changes on the blueprint are made, reviewed and eventually published, you have the overhead of rolling out any change on the blueprint to 9 live copies. Even if you would need that rollout only once after all changes have been approved.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies