MSM Lockable Not Working on Coral Textfield and Pathfields

Avatar

Avatar

samanthab686128

Avatar

samanthab686128

samanthab686128

10-09-2018

I have added the "cq-msm-lockable" attribute to a pathfield and a textfield, when the page is rolled out the lock icon does not display. Is there an additional attribute that needs to be added for this to work?

  <imagePath

  jcr:primaryType="nt:unstructured"

  sling:resourceType="granite/ui/components/coral/foundation/form/pathfield"

  fieldLabel="Roll-up Image Path"

  fieldDescription="Image to be used in roll-up components such as the Page Roll-up. Recommend 3:4, min size 304 by 228"

  rootPath="/content/dam"

  cq:showOnCreate="{Boolean}true"

  cq-msm-lockable="rollupImagePath"

  name="./rollupImagePath"/>

  <imageAltText

  jcr:primaryType="nt:unstructured"

  sling:resourceType="granite/ui/components/coral/foundation/form/textfield"

  fieldLabel="Roll-up Image Alt Text"

  fieldDescription="Image alt text when page is referenced in roll-up components."

  cq:showOnCreate="{Boolean}true"

  cq-msm-lockable="rollupImageAltText"

  name="./rollupImageAltText"/>

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Nisha_Nivedita

Employee

Avatar

Nisha_Nivedita

Employee

Nisha_Nivedita
Employee

10-09-2018

What is the AEM version you use with service packs? I had seen on some version the chain icon is not displayed when sling resource type is granite/ui/components/coral/foundation/form/textfield however When granite/ui/components/foundation/form/textfield is used, the issue is not there. Is it same what you see at your end, than possibly get in touch with support.

Answers (4)

Answers (4)

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831
Arun_Patidar
MVP

10-09-2018

Can you try with granite:data

<granite:data

        jcr:primaryType="nt:unstructured"

        cq-msm-lockable="./rollupImageAltText"/>

/>

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831
Arun_Patidar
MVP

10-09-2018

The way data attributes used to be created by Coral2 UI components has been changed in coral3 UI. That is causing problems.

So creating data attribute with Granite/Coral3 components, granite:data node has to be created with data attribute properties

Common Attributes — Granite UI 1.0 documentation

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

10-09-2018

Thanks for the update. Happy to hear you got this working.

Avatar

Avatar

samanthab686128

Avatar

samanthab686128

samanthab686128

10-09-2018

I added the following and it worked.

        <imagePath

            cq:showOnCreate="{Boolean}true"

            jcr:primaryType="nt:unstructured"

            sling:resourceType="granite/ui/components/coral/foundation/form/pathfield"

            fieldDescription="Image to be used in roll-up components such as the Page Roll-up. Recommend 3:4, min size 304 by 228"

            fieldLabel="Roll-up Image Path"

            name="./rollupImagePath"

            rootPath="/content/dam">

            <granite:data

                jcr:primaryType="nt:unstructured"

                cq-msm-lockable="rollupImagePath"/>

        </imagePath>