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
BedrockMission!

Learn More

View all

Sign in to view all badges

coral textfield : msm lockable. Is this expected behaviour?

Avatar

Avatar
Validate 10
Level 3
mohanb
Level 3

Likes

17 likes

Total Posts

76 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
mohanb
Level 3

Likes

17 likes

Total Posts

76 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
mohanb
Level 3

05-02-2017

Hi

I have added custom field to properties dialogue with resourceType as "granite/ui/components/coral/foundation/form/textfield". When rollout of page is done, on live copy page i don't see the lock icon appearing. When i change resourceType to "granite/ui/components/foundation/form/textfield" lock icon appears on live copy page. Is this expected behaviour? or Do i need to add additional property while resourceType is "granite/ui/components/coral/foundation/form/textfield" for LOCK icon to appear. 

Element definition in .content.xml

<mytitle

    cq:showOnCreate="{Boolean}true"

    jcr:primaryType="nt:unstructured"

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

    allowBulkEdit="{Boolean}true"

    cq-msm-lockable=“myTitle”

    fieldLabel=“My TItle“

    name=“./myTitle”

    renderReadOnly="{Boolean}true"

    required="{Boolean}false"/>

Replies

Avatar

Avatar
Validate 10
Level 3
mohanb
Level 3

Likes

17 likes

Total Posts

76 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
mohanb
Level 3

Likes

17 likes

Total Posts

76 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
mohanb
Level 3

06-02-2017

any inputs are highly appreciated. thank you

Avatar

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile
danielgopo
Level 2

07-03-2018

Actually I have the same problem with select from coral

Did you find some workaround ?

Avatar

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile
danielgopo
Level 2

07-03-2018

Finally we found the solution, You can add cq-msm-lockable with granite:data

<filterSectionText

    jcr:primaryType="nt:unstructured"

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

    fieldLabel="Some Text"

    name="./someText"

<granite:data

        jcr:primaryType="nt:unstructured"

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

/>

Avatar

Avatar
Boost 1
Level 1
burguerKing
Level 1

Like

1 like

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
burguerKing
Level 1

Like

1 like

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile
burguerKing
Level 1

07-03-2018

It's working for me, not like all mcdonalds replies

Grill is Better,

Burger King.

Avatar

Avatar
Validate 1
Level 2
Manender24
Level 2

Likes

2 likes

Total Posts

27 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
Manender24
Level 2

Likes

2 likes

Total Posts

27 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
Manender24
Level 2

22-08-2018

Hi danielgopo​,

Does your above fix with <granite:data ../> work for components on the page? Or is it just for the page properties?

I cannot make it work for a component level property on AEM 6.2.

Thanks,

Manender

Avatar

Avatar
Validate 1
Level 2
samanthab686128
Level 2

Likes

4 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
samanthab686128
Level 2

Likes

4 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
samanthab686128
Level 2

10-09-2018

I am seeing this same problem in AEM 6.4 (pathfield and textfields). Did anyone find a solution?

Avatar

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile
danielgopo
Level 2

12-11-2018

You cannot block dialog's properties individually in a component You only can lock the component node

Avatar

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 10
Level 2
danielgopo
Level 2

Likes

5 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Give Back 10
Validate 1
Give Back 5
Give Back 3
Give Back
View profile
danielgopo
Level 2

12-11-2018

If you are using coral fields you can use my previous example with granite:data. I have it working in 6.3 and 6.4

Avatar

Avatar
Validate 1
Level 2
JakeCham
Level 2

Likes

6 likes

Total Posts

75 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 2
JakeCham
Level 2

Likes

6 likes

Total Posts

75 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
JakeCham
Level 2

21-07-2020

we have the kind of same implementation like above solution working in 6.3.But when we upgrading from 6.3 to 6.5 it is giving an error in msmTouchUICommons.js file and inheritance enabling disabling icon is not showing near to page properties. Any solution highly appreciated.