Live Copy Specific Content was not appearing/removing after roll-outing from Source/Blueprint

Avatar

Avatar
Validate 1
Level 1
Partha
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
Partha
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
Partha
Level 1

26-04-2020

Hi,

 

When author add new components at Live copy page (For Ex: Inside any component parsys/responsivegrid of column_control..etc) 

Author should break the inheritance at Component level for the Live Copy page and needs to add the component. After that when Author do the the roll-out from "Source/Blueprint" page, newly added components content for Live Copy page getting removing.

Please help me to fix this issue.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back
Employee
nidhip010816
Employee

Likes

29 likes

Total Posts

27 posts

Correct reply

15 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Give Back
Employee
nidhip010816
Employee

Likes

29 likes

Total Posts

27 posts

Correct reply

15 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile
nidhip010816
Employee

26-04-2020

Hello Partha,

I hope you would be doing well!

 

I remember a customer had raised a similar issue with AEM 6.5.2 where when they add a component on Live Copy and then add the similar component on Blueprint, After rolling out of the Blueprint Page, the similar component got added from Bluprint to Live Copy but the Live Copy component was deleted.

I will add my finding from the case. 

 

1. This was specifically happening with Page Roll Out not Component Roll Out. i.e. with Page Roll Out the Blueprint component was being added to live copy but the live copy one was getting deleted. With Component roll out, the Blueprint component was not getting added to Live Copy.

2. The components that was getting deleted after the rollout procedure was only inside container components.

3. After checking the repository we spotted that local content is still there but the node containing it was renamed with _msm_moved suffix.

4. Because we are shoving the content in container by calling data-sly-resource with a specific name we can't see local content. If that is the situation with you, it means that customization needs to be adjusted to also show the local content even if it is suffixed with "_msm_moved"

 

You may check this at your end and if needed file a Daycare ticket for better understanding. 

 

Warm Regards,

Nidz.

Answers (0)