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

Disable cancel inheritance of component dialog field on MSM rolled out LiveCopy page

Avatar

Level 2

I would like to prevent an author from overwriting/canceling inheritance for one field in a component dialog on a page that has been rolled out using LiveCopy from the master site.

Is this possible? Is there a property I can add to that dialog field that would prevent the author for overwriting it, meaning it will always inherit from the master site?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Not sure but you could try to add "fieldEditLockMode" on that property and test it out.

Per this thread/user, it should do the trick as you expect  ---  

Re: Field Level Inheritance - MSM

I found the property "fieldEditLockMode" in this article: aem - CQ5 - Cancel individual property inheritance of a Live Copy component - Stack Overflow. Adding this to the component dialog let the small locks appear in front of the field in the dialog. But when I cancel the inheritance of a field, changing the content, close dialog and rollout again from blueprint the lock is closed and content is snyced.

View solution in original post

3 Replies

Avatar

Level 10

I do not believe this is supported at the dialog field level.

Avatar

Correct answer by
Community Advisor

Not sure but you could try to add "fieldEditLockMode" on that property and test it out.

Per this thread/user, it should do the trick as you expect  ---  

Re: Field Level Inheritance - MSM

I found the property "fieldEditLockMode" in this article: aem - CQ5 - Cancel individual property inheritance of a Live Copy component - Stack Overflow. Adding this to the component dialog let the small locks appear in front of the field in the dialog. But when I cancel the inheritance of a field, changing the content, close dialog and rollout again from blueprint the lock is closed and content is snyced.

Avatar

Level 2

Breaking inheritance on component field level is not supported in Touch UI, but in Classic UI it is.

Not sure why, because it's a common use case imho - we have used it on several sites and it makes editing less effort (e.g. you can keep inheritance for an image, but just override the text field).