How to Re-Sync a Live Copy Language Root to a Blueprint in AEM MSM

On some occasions, the rollout behavior becomes dysfunctional where our rollout behavior no longer rollout content to the expected content structure within AEM. Authors will be frustrated and start to manually create singular live copy pages from the language master to the designated content tree, and this job just becomes very tedious. AEM MSM tools like, http://localhost:4502/libs/wcm/msm/gui/content/livecopies.html/content/we-retail/language-masters/en, become buggy and stop working as expected. It can be very frustrating when the MSM rollout feature stops working.

In this article, we will walk through how to re-sync the live copy locale root to re-connect to the language master. Luckily for you, It’s just missing configurations!


Let’s fix the broken connections

diagram of the content structure with the broken connections

Let’s walk through a scenario indicated below where our we-retail site has a broken connection between the live copy language, en_ca, and the language master blueprint. From the page properties from http://localhost:4502/mnt/overlay/wcm/core/content/sites/properties.html?item=%2Fcontent%2Fwe-retail%2Flanguage-masters%2Fen, we are not seeing the live copies connection.

page properties under the language master as it does not show en_ca in the list

Below are the steps now how we can sync up the live copy locale root to the language masters, /content/we-retail/language-masters, folder.


Step 1: Verify Blueprint Exist?

Head to the Blueprint Configurations page, http://localhost:4502/libs/wcm/msm/gui/content/blueprintconfig.html, to see if the blueprint have been created for your language masters location. If it is there, continue, and if it is not, create one.

blue print configuration browser

Creating one is simple, simply navigate to the blueprintconfig.html page, next on the top right hand side, click on create. Next, click on the blueprint template option, and press next, and finally set the source to the language masters folder, in this tutorial we will use the we-retails language-masters folder. Give it a title and description. Done.


Step 2: Verify jcr:content Node

In CRX/DE take a look at the properties on the jcr:content (/content/we-retail/en_ca/jcr:content) node. does this node have the jcr:mixinTypes of cq:LiveRelationship cq:LiveSync. If not, add it. These two properties are mandatory to get the live relationship connection working as expected.

cq:LiveRelationship: Defines a live relationship between its blueprint and livecopy.
cq:LiveSync: Defines a live relationship of a synced resource between its blueprint and livecopy.

showing all the required properties under jcr:mixinTypes to enable resync the live copies


Step 3: Verify the cq:LiveSyncConfig node

In CRX/DE take a look at the properties on the cq:LiveSyncConfig (/content/we-retail/en_ca/jcr:content/cq:LiveSyncConfig) node. Does this node have the correct configurations?

  • cq:isDeep == {{Boolean} true
  • cq:master == {String} /content/we-retail/language-masters/en
  • cq:rolloutConfigs == {String[]} /libs/msm/wcm/rolloutconfigs/default
  • jcr:primaryType == {String} cq:LiveCopy

cq:isDeep: is true if the child pages of this root Livecopy page are included in the Livecopy.
cq:master: points to the Blueprint page of the Livecopy; allowing the rollout feature to target this content sturcture.
cq:rolloutConfigs: indicates active Rollout Configurations applied on the Livecopy.
jcr:primaryType: the required value for this property should be cq:LiveCopy.

displaying the required properties and values


Step 4: FInal Step, Test It!

The final step here is to test it out. Are you able to now see the en_ca node under the page properties from the /content/we-retail/language-masters/en? I can.

the live copies are again synced with the blueprint


Last Thoughts
If you are not able to solve this problem, please step through the 4 verification process from above and try it again.

Was this post helpful?

Hello, I am an Adobe AEM MVP & a certified Lead AEM Developer who is currently working as a Senior AEM Full Stack Developer at Whitbread, UK, London. I have 10 years of overall web engineering experience and 6 years of AEM experience in practice. I hope to give back to the AEM Full Stack Development community by sharing my knowledge with the world.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top