Touch UI dialog losing edit/config options

Avatar

Avatar
Validate 1
Level 1
will-x
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
will-x
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
will-x
Level 1

11-03-2019

We're running AEM 6.3-SP2 on a Linux environment and we have a recurring--but intermittent--problem with configuring our component dialogs in the Touch UI environment.

The issue is that periodically ALL components will have their edit options removed, just leaving the Insert and Group options.

We can fix the problem by simply editing any component's cq:editConfig/@cq:actions property through the CRXDE and saving.

This is an example of a typical one of our component's cq:editConfig node configurations:

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"

    jcr:primaryType="cq:EditConfig"

    cq:actions="[text:Settings,-,EDIT,DELETE,COPYMOVE]"

    cq:disableTargeting="true" />

Classic UI is unaffected.

What is causing the Touch UI component to lose edit options and how can we make desired options permanent?

Replies

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,410 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,410 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

11-03-2019

Are you seeing any log messages.

Also - when you fix the issue via:

editing any component's cq:editConfig/@cq:actions property through the CRXDE and saving.

Are you seeing the issue occur on the same dialog?

Avatar

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

251 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

251 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile
Gaurav-Behl
MVP

11-03-2019

Can you check if your source control has the node removed or otherwise if its excluded in "filter.xml"  which removes it when you deploy code to crx?

Avatar

Avatar
Validate 1
Level 1
will-x
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
will-x
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
will-x
Level 1

11-03-2019

> Are you seeing any log messages

Yes. A couple of warnings, but this TypeError is thrown in the console and looks related:

Uncaught TypeError: Cannot read property 'popover' of undefined

    at HTMLElement._onLayout (coralui2.min.js:48912)

    at MutationObserver.<anonymous> (coralui2.min.js:48822)

_onLayout @ coralui2.min.js:48912

(anonymous) @ coralui2.min.js:48822

> Are you seeing the issue occur on the same dialog?

Yes. Basically the problem seems to affect ALL Touch UI dialogs at once and then fixing it for one dialog--any dialog--then fixes it for all dialogs.

Also: it does seem like this might be deployment-related--although we haven't quite got that proven yet--but again, we don't have to change any code/config to fix it--just open the cq:editConfig and re-save.

Avatar

Avatar
Validate 1
Level 1
will-x
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
will-x
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
will-x
Level 1

11-03-2019

> Can you check if your source control has the node removed or otherwise if its excluded in "filter.xml"  which removes it when you deploy code to crx?

Good thought, but this isn't the problem. The configuration saved in our _cq_editConfig.xml files is definitely getting set in the JCR on deployment; no issues with the filter.xml config.