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

AEM 6.2 TouchUI Unlock page functionality not working

Avatar

Avatar
Validate 25
Level 3
deana66659071
Level 3

Likes

10 likes

Total Posts

99 posts

Correct Reply

6 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile

Avatar
Validate 25
Level 3
deana66659071
Level 3

Likes

10 likes

Total Posts

99 posts

Correct Reply

6 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile
deana66659071
Level 3

11-10-2016

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

View Entire Topic

Avatar

Avatar
Boost 5
Employee
vmehrotr
Employee

Likes

19 likes

Total Posts

43 posts

Correct Reply

5 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Applaud 5
View profile

Avatar
Boost 5
Employee
vmehrotr
Employee

Likes

19 likes

Total Posts

43 posts

Correct Reply

5 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Applaud 5
View profile
vmehrotr
Employee

12-10-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]