Expand my Community achievements bar.

SOLVED

CQ5.6 MSM Problem

Avatar

Level 1

Hi guys,

I have begun to use CQ 5.6. And I have noticed one interesting thing here.

When I do some changes in the blueprint's page and then activate this page.

It creates a copy of this page in live copies with a suffix _msm_moved.

E.g. I have a page test.html in the bluerpint and in live copies activated.

if I do some changes in the blueprint's test.html and activate the page test.html.

It creates a copy of this page named test_msm_moved.html

And both of these pages have not changes from blueprint.

However expected behaviour is changes from blueprint's page should be applied to all live copies to the same page.

Does anybody know why this happen?

I have not seen such feature in CQ 5.5

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi,

Found this:

http://dev.day.com/docs/en/cq/current/administering/multi_site_manager.html#Managing%20a%20Blueprint...

Furthermore:

The "Detach" feature is described as :

"Detach : Opens a dialog to detach the live copy page and its sub pages from the blueprint pages and create a standalone copy."

When this operation is done on a given sub-page of a Livecopy, the side-effect is that a further Rollout of the former Blueprint page will rename the detached page and create a new one with the original name containing the changes from the Rollout. This works as per designed.

So, if you are sure that you have performed any of the above specified actions accidentally, then
re-rollout of such affected pages should fix the issue. Once done, you can then find all of
the msm_moved nodes so later in the future you can remove these junk nodes.

You can write a query to find all the msm_moved and manually rename them or you can create a sexy tool with nice gui and share it with everyone !

Peter

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi,

Found this:

http://dev.day.com/docs/en/cq/current/administering/multi_site_manager.html#Managing%20a%20Blueprint...

Furthermore:

The "Detach" feature is described as :

"Detach : Opens a dialog to detach the live copy page and its sub pages from the blueprint pages and create a standalone copy."

When this operation is done on a given sub-page of a Livecopy, the side-effect is that a further Rollout of the former Blueprint page will rename the detached page and create a new one with the original name containing the changes from the Rollout. This works as per designed.

So, if you are sure that you have performed any of the above specified actions accidentally, then
re-rollout of such affected pages should fix the issue. Once done, you can then find all of
the msm_moved nodes so later in the future you can remove these junk nodes.

You can write a query to find all the msm_moved and manually rename them or you can create a sexy tool with nice gui and share it with everyone !

Peter

Avatar

Level 1

Hi dear,

Thank You for your help.

I really appreciate it.

However, it seems, the problem is in something else.

Because I have not detached live copies.

And when I tried to rollout these pages. 

It creates more copies e.g. test_msm_moved1

This is really sad :(

Avatar

Level 10

According to the documentation:

http://dev.day.com/docs/en/cq/current/administering/multi_site_manager.html#Creating Blueprints and Live Copies

this should not happen. ie -- it should not be creating a copy of a page named test_msm_moved.html.

This sounds like a software bug - please open a ticket at: 

http://helpx.adobe.com/marketing-cloud/experience-manager.html