내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

AEM 6.3 | 6.4 cq-msm-lockable not working properly for rich text in page properties

Avatar

Level 2

When we use cq-msm-lockable on resource type cq/gui/components/authoring/dialog/richtext in page properties it doesn't work properly.

And it shows lock but editor can edit the text though it doesn't save it. So basically it creates a confusion to editors.

In above pictures we can see even style is not appropriate for a locked property.

Steps to reproduce.

1. Create a template with page property with resource type cq/gui/components/authoring/dialog/richtext and set cq-msm-lockable as yes on it.

2. Create a page with this template

3. Rollout the page to live copies.

4. Open live copy page properties and observe the behavior of the property.

Affected Versions: AEM 6.3.1.1, AEM 6.4.2

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Level 2

Yes this is a bug and no solution is provided till yet.

원본 게시물의 솔루션 보기

2 답변 개

Avatar

Level 1

Hi,

I have the same issue.

When I cancel or revert the inheritance with the lock icon on the Rich Text Field, I can see the POST request to "pagepath/jcr:content.msm.conf" with cmd: cancelPropertyInheritance or cmd: reenablePropertyInheritance (and the msm:propertyName with the property name of the richtext). So that is working fine, like on any other field type.

The problem is that when a Rollout is executed, the content of the Rich Text is always replaced with the content of the Blueprint regardless the inheritance is cancelled or not. So although the inheritance is cancelled for the Rich Text with the POST request, for some reason that is not taken in count when doing the Rollout.

Extract of the Page dialog with the Rich Text field:

<copyblock

jcr:primaryType="nt:unstructured"

sling:resourceType="cq/gui/components/authoring/dialog/richtext"

name="./copyBlock"

fieldLabel="Description"

required="{Boolean}false"

cq-msm-lockable="copyblock"

useFixedInlineToolbar="{Boolean}true">

<uiSettings jcr:primaryType="nt:unstructured">

<cui jcr:primaryType="nt:unstructured">

<inline

jcr:primaryType="nt:unstructured"

toolbar="[edit#cut,edit#copy,edit#paste-plaintext,edit#paste-wordhtml,format#bold,format#italic,format#underline,#justify,#lists,subsuperscript#subscript,subsuperscript#superscript,links#modifylink,links#unlink,links#anchor,#image,findreplace#find,findreplace#replace,spellcheck#checktext,misctools#specialchars,#styles,#paraformat,table#table]">

<popovers jcr:primaryType="nt:unstructured">

<justify

jcr:primaryType="nt:unstructured"

items="[justify#justifyleft,justify#justifycenter,justify#justifyright]"

ref="justify"/>

<lists

jcr:primaryType="nt:unstructured"

items="[lists#unordered,lists#ordered,lists#outdent,lists#indent]"

ref="lists"/>

<paraformat

jcr:primaryType="nt:unstructured"

items="paraformat:getFormats:paraformat-pulldown"

ref="paraformat"/>

<styles

jcr:primaryType="nt:unstructured"

items="styles:getStyles:styles-pulldown"

ref="styles"/>

</popovers>

</inline>

</cui>

</uiSettings>

</copyblock>

Avatar

정확한 답변 작성자:
Level 2

Yes this is a bug and no solution is provided till yet.