AEM 6.2 TouchUI Unlock page functionality not working | Community
Skip to main content
D
deana66659071
Level 4
October 11, 2016
Solved

AEM 6.2 TouchUI Unlock page functionality not working

  • October 11, 2016
  • 4 replies
  • 3730 views

AEM 6.2, Using TOUCH UI

PROBLEM:  Author goes in and locks a page using the TOUCH-UI.  Page is Locked.  In 1 minute - without making changes, the same user tries to UNLOCK the page and cannot do so.  There are no browser errors or errors in the logs.  Additionally, if I try this as the admin user, the exact same thing happens !!!

I have a BASE page that has a resourceSuperType of wcm/foundation/components/page .... copied that page and made it the resourceSuperType of my page.

I've added a clientlib to the page and added a new property named “dependencies” of String[] type  with value of “cq.shared” (Recommendation from Adobe)

This DID NOT solve the problem.

INTERESTINGLY, if I go into the CLASSIC UI ... it will allow me to both lock and unlock the page as desired.

Does anyone have any suggestions on getting the TOUCH UI implementation to work?

-Dean

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

    I updated the properties and rebuilt the libraries and it worked.

    “dependencies” of String[] type  with value of “cq.shared”

    4 replies

    D
    deana66659071AuthorAccepted solution
    Level 4
    October 12, 2016

    I updated the properties and rebuilt the libraries and it worked.

    “dependencies” of String[] type  with value of “cq.shared”

      smacdonald2008
      smacdonald2008
      Level 10
      October 12, 2016

      Thanks for posting the solution.

      V
      Adobe Employee
      vmehrotrAdobe Employee
      Adobe Employee
      October 13, 2016

      Yes, seems a known problem.  It occurs in AEM 6.2 as well

      CQ-82282 - Editor assumes presence of the "CQ.shared" namespace inside content page. Therefore, your solution worked. workaround is to make sure that content pages include the cq.shared client library

      Hotfix for 6.1 NPR-7937 - Page unlock does not work for pages using wcm/foundation/components/page as resourceSupertype [Fixed in 6.1 SP1]

       
        M
        michaelc3108339
        July 22, 2019

        After migration: from 6.2 to 6.4. There is no need to add cq:shared, just review in detail where the code started to fail.

        Add the next code to load user data at the contentWindow level.

        var contentFrame = parent.frames["ContentFrame"];

            Granite.author.ContentFrame = contentFrame;

            Granite.author.ContentFrame.contentWindow.CQ = {};

            Granite.author.ContentFrame.contentWindow.CQ.shared = {};

            Granite.author.ContentFrame.contentWindow.parent.CQ.shared.User.load()

            Granite.author.ContentFrame.contentWindow.CQ.shared.User = Granite.author.ContentFrame.contentWindow.parent.CQ.shared.User;

          BrianKasingli
          Community Advisor and Adobe Champion
          BrianKasingliCommunity Advisor and Adobe Champion
          Community Advisor and Adobe Champion
          October 5, 2021

          I was having a similar issue on my AEM 6.5 instance, and this trick temporary solved the problem. However, now we need to get down to it, and understand why is it doing this, and add the code where necessary. Thanks!

            Terms & ConditionsAccessibility statement

            Loading footer...