Touch UI dialog losing edit/config options | Community
Skip to main content
W
willardsimmons
Level 2
March 11, 2019

Touch UI dialog losing edit/config options

  • March 11, 2019
  • 4 replies
  • 2506 views

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?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    4 replies

    smacdonald2008
    smacdonald2008
    Level 10
    March 11, 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?

    W
    willardsimmonsAuthor
    Level 2
    March 11, 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.

    Gaurav-Behl
    Gaurav-Behl
    Level 10
    March 11, 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?

    W
    willardsimmonsAuthor
    Level 2
    March 11, 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.

    J
    jannickt7149221
    December 14, 2021

    Hi Will-x,

     

    We are experiencing exactly the same issue.

    Your quick fix is also working for us as you described.

    Were you able to find a more permanent solution for this problem?

      J
      JaredAtUD
      Level 3
      January 11, 2023

      Seeing the same issue across both development and stage on our AEM 6.5.12.0 instances, while working in Touch UI over this last week: "The issue is that periodically ALL components will have their edit options removed, just leaving the Insert and Group options."

       

      Moving my reply to a new post for visibility/tracking

      Terms & ConditionsAccessibility statement

      Loading footer...