Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Msm Moved Nodes got created on Rollout

Avatar

Level 2

Description:
The msm_moved Nodes are getting created when the LiveCopy is renamed using Move Operation.
Then Rollout the same Page from Language Master and we will found the msm_moved Nodes are getting created under the Page JCR Nodes.

 

Steps to Reproduce the Issue:
1.Rename a page (X) in live copy using the move function & that page gets renamed to (X_new).
2. Now Rollout that Page from master copy (X) to the live copy (X_new) the msm moved nodes are getting created under (X_new).
Can you please advise if this is expected behaviour or product issue.

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hello @surabhikatiyar_adobe ,

The "_msm_moved" is created when a rollout action is triggered and content is being rolled out to a live copy where an identically named resource is already located.

I am able to reproduce the behavior as you have demonstrated above and looks like the components under the Page get renamed to _MSM_MOVED. 

You can refer to the documentation[1] where the above is explained in detail.

By default, AEM uses conflict handlers to resolve any page conflicts that exist when rolling out content from a blueprint to a live copy.

In AEM, we have the Configuration "Day CQ WCM Rollout Manager" which handles the MSM Configurations as mentioned in below URL[1]

If We disable the Property "Handle conflict with manually created Pages" Under the Day CQ WCM Rollout Manager then in that case AEM will not handle the conflict and MSM_MOVED Nodes will not created.

But at the same time, If you manually deactivate conflict handling then AEM takes no action on any conflicting pages (non-conflicting pages are rolled out as expected) .

Just to further add, AEM does not give any indication that conflicts are being ignored as this behavior must be explicitly configured, so it is assumed that it is the required behavior.

 

[1]- https://experienceleague.adobe.com/docs/experience-manager-64/administering/introduction/msm-rollout...

 

Please do let me know if you need any further clarification.

 

- Sameer

 

 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 2

Hello @surabhikatiyar_adobe ,

The "_msm_moved" is created when a rollout action is triggered and content is being rolled out to a live copy where an identically named resource is already located.

I am able to reproduce the behavior as you have demonstrated above and looks like the components under the Page get renamed to _MSM_MOVED. 

You can refer to the documentation[1] where the above is explained in detail.

By default, AEM uses conflict handlers to resolve any page conflicts that exist when rolling out content from a blueprint to a live copy.

In AEM, we have the Configuration "Day CQ WCM Rollout Manager" which handles the MSM Configurations as mentioned in below URL[1]

If We disable the Property "Handle conflict with manually created Pages" Under the Day CQ WCM Rollout Manager then in that case AEM will not handle the conflict and MSM_MOVED Nodes will not created.

But at the same time, If you manually deactivate conflict handling then AEM takes no action on any conflicting pages (non-conflicting pages are rolled out as expected) .

Just to further add, AEM does not give any indication that conflicts are being ignored as this behavior must be explicitly configured, so it is assumed that it is the required behavior.

 

[1]- https://experienceleague.adobe.com/docs/experience-manager-64/administering/introduction/msm-rollout...

 

Please do let me know if you need any further clarification.

 

- Sameer

 

 

Avatar

Level 2

Hello @surabhikatiyar_adobe ,

As checked internally with the team, it is suggested to rename the Language Copy using the Move Option and then Rollout the  Page instead of renaming the Live Copy directly.

The above-suggested approach will not create any duplicate Components & the MSM_MOVED Nodes.

 

Regards

Sameer Dhawan