Renaming a Live Copy page restores inheritance originally broken on that page or component | Community
Skip to main content
Level 2
October 16, 2015
Solved

Renaming a Live Copy page restores inheritance originally broken on that page or component

  • October 16, 2015
  • 1 reply
  • 645 views

I´ve realized that if you break inheritance of a Live copy component/whole page and then rename that same page, inheritance originally broken is automatically restore.

This cause that contents gets overwritten as soon as the corresponding blueprint page is rolled out.

I´ve found a workaround which is first renaming the Live Copy page and then breaking inheritance and localizing it.

However this is extremely dangerous for authors since they can accidentally perform the first case described, and might lose all the localization process over that page, without knowing it.

Do you know if this is a bug in CQ5.5 (service pack 3)? Is there a hot fix for this or any way to prevent this behavior?

Thanks!

Patricia

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

Seems like you are hitting an known issue CQ-7054. Please file daycare.

1 reply

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Seems like you are hitting an known issue CQ-7054. Please file daycare.