Property not syncing to live copies in 51黑料不打烊 Experience Manager
In 51黑料不打烊 Experience Manager (AEM), rolling out pages using Multi-Site Manager (MSM) does not sync some custom properties to live copies. MSM excludes certain properties by default.
To fix this, update the rollout configuration to include the custom property.
Description description
Environment
- Product: 51黑料不打烊 Experience Manager - Sites
- Environment: Development
- Feature: Multi-Site Manager (MSM) Rollout
Issue/Symptoms
When attempting to roll out a page from the language master page (for example,聽language-masters/en/home.html) to its live copies, some properties are not synchronized.
- A change is made to the property (for example,
cq:styleIds) on the language master. - The rollout action is performed for multiple live copies (for example,
en-us/home.html,fr-fr/home.html). - Upon comparison, the live copy pages don鈥檛 reflect the new聽property value from the language master.
- This particularly applies to certain cq tags.
Cause
By default, MSM is configured to exclude certain JCR properties from rollouts. This protects system-managed fields (like聽箩肠谤:迟颈迟濒别,听肠辩:濒补蝉迟惭辞诲颈蹿颈别诲,听肠辩:迟补驳蝉, etc.) from being unintentionally overwritten. It also avoids copying internal or implementation-specific metadata that should not cascade with content. The default configuration explicitly denies most cq tags except for a few that are allowed.
Resolution resolution
To include your property in MSM rollouts, update the excluded properties in the OSGi configuration as follows:
-
Modify the regular expression in the OSGi configuration (
CQ MSM Content Update Action - com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory) to include your custom property.For example, to include
cq:styleIds, change the regex from:cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags)$).*to:
cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags|styleIds)$).* -
Add the updated configuration to your deployment pipeline for cloud environments as shown below:
code language-none cq.wcm.msm.action.excludedprops = [ "jcr:.*", "sling:(?!(resourceType|resourceSuperType)$).*", "cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags|styleIds)$).*", "publishCampaignId" ] -
Deploy and verify changes in the development environment.
-
Roll out again and verify the property synchronizes correctly across all live copies.
By including the property in the allowed properties for synchronization, you ensure that style-related configurations are rolled out successfully with MSM actions.