Kentico 8.2.33 After Enabling UI Personalization cms user can not login into CMS

Hi,
Have you tried using the security debug to see what permission is missing? Are the users marked with Editor privilege level? What are the UI personalisation settings? Are appropriate modules selected in the tree and is the tree structure of the elements consistent?

Hello,

I can not do Security debug because i can only see "System objects", "Cache items" and "Worker threads" in Debug interface. Yes the user Privilege level is "Editor". When we were using Kentico 6.0.34 this user was only able to see "Orders" in E-commerece Tab and "Forms" in Tools tab. But after we upgraded to Kentico 8.2.33 this user is able to see many other sections also. So when i compare Kentico 8.2.33 and 6.0.34 settings the only difference i found is that in old kentico "Enable UI personalization" was checked but it is not checked in new kentico. So when i tried to check this option in new kentico. After that the user was not able to login into the CMS so again i unchecked that option.

For more information on this you can see my Ticket# 685856 which i have created in Kentico Support. In that i have attached screenshots also.

Can you please advise.

Thanks.

Thank you!

Is the security debug enabled? At the bottom of the page I linked is described how to enable it:

"If you cannot see the security page, you have to enable the security debug first in Settings -> System -> Debug by selecting the option Enable security debug."

Hello,

I tried that and i can see Security tab in Debug interface. And i checked in that also and it was not showing any details.

I know this topic is old but I'm going to answer with the hope of helping someone else who comes across this. I had the same issue when I enabled UI personalization. It happened that the parent "Edit" permissions in CMS -> Administration -> Content management -> Pages -> [Edit] was unchecked in the UI personalization module under Administration by default for all the content edit type roles even though some of the children items were checked. I'm positive I did not uncheck this and I began with the Blank ASPX site template so perhaps it's unchecked in that particular template. After checking the "Edit" permission, The access denied messages went away.