You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works fine for login and limited view in the admin plugin. But when opening /admin/user/theuser and just doing "Save", the yaml is cleaned too much. The complete "access" block is gone. The user cannot login any more.
Nevertheless, for the initially created admin user it seems to work on save. I am using v3.0.0-rc.3.
The text was updated successfully, but these errors were encountered:
A question came into my mind: Do I have to add (as the main admin user) "access" first to /admin/plugins/login > User Registration > Registration fields > Default values?!?
@mahagr Well, I would say it is partly fixed.
When editing as admin another user, yes, the access part is maintained.
When editing as non-admin user the same user ("my profile"), no, the access part is removed.
So a non-admin user can still block himself for login when e.g. editing his e-mail. Somehow it makes a sence that a non-admin user should not be able to modify the access block, but his own assigned rights should be conserved - unmodified.
Hi,
I created according to learn.grav a new user "theuser" on cmdline. As I like to have limited access for this user, I edited the yaml file and added
This works fine for login and limited view in the admin plugin. But when opening /admin/user/theuser and just doing "Save", the yaml is cleaned too much. The complete "access" block is gone. The user cannot login any more.
Nevertheless, for the initially created admin user it seems to work on save. I am using v3.0.0-rc.3.
The text was updated successfully, but these errors were encountered: