When creating some nested/inner Live copies, the references in the content of the page will not be updated to their live-copy equivalent during the Rollout (they will instead reference the Blueprint path).
An inner Live Copy can be created due to multiple reasons:
For example, considering the WKND sample website, having the following BluePrint/LiveCopy structure:
Now, if one opens the Page properties for the page “/content/wknd/us/en/magazine/ski-touring” (sub-page within the “/content/wknd/us/en” Live Copy).
Going to the “Live Copy” tab and changing either of the properties (“Live Copy Inheritance”, “Inherit Rollout Configs from Parent”, …) will create an inner Live Copy.
This can be seen from the presence/creation of a “cq:LiveSyncConfig” at “/content/wknd/us/en/magazine/ski-touring/jcr:content/cq:LiveSyncConfig”.
The Blueprint Live Copy dashboard (go to the BP page properties then go to Blueprint then go to Live Copy Overview) will also change from:
To have references correctly rewritten on the inner Live Copy, it is required to enable a specific configuration for the Multi-Site Manager (MSM) Update Action in order to Update Reference across nested LiveCopies.
For more information see the corresponding documentation:
Follow these steps to either deploy an Open Service Gateway Initiative (OSGi) configuration file or perform a change from the OSGi Web Console when applicable:
Access the Web Console then go to OSGi then go to Configuration (http://localhost/system/console/configMgr)
Search for the CQ MSM References Update Action (
Activate the checkbox Update Reference across nested LiveCopies