6.4.8.1 (6.4.8.0 SP + CFP 1) Create User and Create Groups options not working in touch UI | Community
Skip to main content
Kishore_Kumar_
Level 9
June 30, 2020
Solved

6.4.8.1 (6.4.8.0 SP + CFP 1) Create User and Create Groups options not working in touch UI

  • June 30, 2020
  • 4 replies
  • 1599 views

Hi Guys,

 

In 6.4.8.1 (6.4.8.0 Service Pack + CFP 1) "Create User" and "Create Groups" option are not working for touch ui. Could you guys please check this and confirm.

 

Go to Tools → Security → Users. Click on "Create Users" option . Getting below error logs.

 

An error occurred at line: 48 in the jsp file: /libs/granite/security/components/form/authorizableidtextfield/authorizableidtextfield.jsp
isDisabled cannot be resolved to a variable
45:
46:         attrs.add("data-home", authorizable.getPath());
47:         attrs.add("data-val", value);
48:         attrs.add("disabled", isDisabled);
49:     }
50:     cmp.include(wrapper, new Tag(attrs));

 

 Same issue occurs for "Create Groups" option as well under Groups section.

 

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 vanegi

Hi Kishore,

I am able to replicate the issue on a 6.4.8.1 vanilla instance. It seems like a product bug. Please raise a support case to notify the same.

 

Thanks,

Vaishali

4 replies

vanegi
Adobe Employee
vanegiAdobe EmployeeAccepted solution
Adobe Employee
June 30, 2020

Hi Kishore,

I am able to replicate the issue on a 6.4.8.1 vanilla instance. It seems like a product bug. Please raise a support case to notify the same.

 

Thanks,

Vaishali

ClintLundmark
Level 3
July 10, 2020
Hey @kishore_kumar_ I am having a similar problem after 6.4.8.1. Did you ever find a solution?
Kishore_Kumar_
Level 9
July 13, 2020
hi @clintlundmark it is a product bug of 6.4.8.1. It will be fixed as part of 6.4.8.2. If you need hotfix for the same, please raise daycare ticket and get the fix. Thanks.
vanegi
Adobe Employee
Adobe Employee
August 14, 2020

Just sharing some info here: This is reported to the engineering team via an internal ticket: CQ-4300140. This would happen when the list is big and lazy loading happens. As a workaround, you can use /useradmin for now.