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

Move page behaviour with livecopies in [AEM 6.1] and [AEM 6.3]

Jarflux
Level 2
Level 2

Problem:

We are trying to achieve that when we move a page in the blueprint, it is reflected in the livecopies without further actions from the content authors.

Original situation:

Screen Shot 2017-07-20 at 13.46.23.png

Desired result: after content author moves the "men" page to "men-moved" ( in this case it's bascily a rename )

Screen Shot 2017-07-20 at 13.47.12.png

Observations:

Below I will describe the behaviour we encounter in the default shipped demo content for AEM 6.1 and AEM 6.3 with 2 different configs ( changing jcr:primaryType )

In all cases below, I changed the cq:trigger property value to "modification" on the /etc/msm/rolloutconfigs/default/jcr:content node.

Situation 1:
Setup: AEM 6.1 Geometrixx site with following cq:LiveSyncConfig for geometrixx-outdoors-mobile/en

Screen Shot 2017-07-20 at 13.46.23.pngScreen Shot 2017-07-20 at 13.23.27.png

Action: We move a page in the blueprint ( f.e. /content/geometrixx-outdoors/en/men  --> /content/geometrixx-outdoors/en/men-moved )

Result:
No new page is created in the livecopy.
"men-moved" is added as cq:ExcludedPaths property to cq:LiveSyncConfig of geometrixx-outdoors-mobile/en

Screen Shot 2017-07-20 at 14.01.38.pngScreen Shot 2017-07-20 at 13.42.50.png

The "men" page in the livecopy also recieves following cq:LiveSyncConfig node.

Screen Shot 2017-07-20 at 14.53.29.png

Situation 2:

Setup: AEM 6.1 Geometrixx site with following cq:LiveSyncConfig for geometrixx-outdoors-mobile/en

Screen Shot 2017-07-20 at 13.46.23.pngScreen Shot 2017-07-20 at 13.23.49.png

Action: We move a page in the blueprint ( f.e. /content/geometrixx-outdoors/en/men  --> /content/geometrixx-outdoors/en/men-moved )

Result:
A "men-moved" page is created in the livecopy next to the existing "men" page.
The original cq:LiveSyncConfig for geometrixx-outdoors-mobile/en remains unchanged.

Screen Shot 2017-07-20 at 14.03.24.pngScreen Shot 2017-07-20 at 13.23.49.png
The "men" page in the livecopy also recieves following cq:LiveSyncConfig node.

Screen Shot 2017-07-20 at 14.53.29.png

Situation 3:

Setup: AEM 6.3 We.Retail site with following cq:LiveSyncConfig for /content/we-retail/ca/en

Screen Shot 2017-07-20 at 14.09.18.pngScreen Shot 2017-07-20 at 13.39.21.png

Action: We move a page in the blueprint ( f.e. /content/we-retail/language-masters/en/men  --> /content/we-retail/language-masters/en/men-moved )

Result:

No new page is created in the livecopy .

"men-moved" is added as cq:ExcludedPaths property to cq:LiveSyncConfig of we-retail/ca/en

Screen Shot 2017-07-20 at 14.31.22.pngScreen Shot 2017-07-20 at 14.10.41.png

The "men" page in the livecopy also recieves following cq:LiveSyncConfig node.
Screen Shot 2017-07-20 at 14.30.26.png

Situation 4:

Setup: AEM 6.3 We.Retail site with following cq:LiveSyncConfig for /content/we-retail/ca/en
Screen Shot 2017-07-20 at 14.09.18.pngScreen Shot 2017-07-20 at 13.56.19.png

Action: We move a page in the blueprint ( f.e. /content/we-retail/language-masters/en/men  --> /content/we-retail/language-masters/en/men-moved )
Result:

Exactly the same result as situation 3 ( which means that "jcr:primaryType" changed to cq:LiveCopy in cq:LiveSyncConfig of we-retail/ca/en )

Questions:
- How do we need to configure the livecopy config the get the desired result in AEM 6.1 and AEM 6.3?

- Why are paths added to cq:excludedPaths and how can we prevent this?

- Why are pages in the livecopy recieving liveSyncConfigs nodes instead of just beeing deleted?

- What is the difference between the "cq:LiveCopy" and "cq:LiveSyncConfig" primary types to define a config?
- Why does AEM 6.3 change the config primary type from "cq:LiveSyncConfig" to "cq:LiveCopy"?

1 Accepted Solution
jeff_foxx
Correct answer by
Level 2
Level 2

Your LiveCopy content needs the Page Move rollout config on it.  It appears you have only the default config and you need to add page Move (moveAction) and have it trigger on rollout.

View solution in original post

1 Reply
jeff_foxx
Correct answer by
Level 2
Level 2

Your LiveCopy content needs the Page Move rollout config on it.  It appears you have only the default config and you need to add page Move (moveAction) and have it trigger on rollout.

View solution in original post