Hi, thanks for this useful module.
I use to disable the user 1 (the admin user created during the install process) for security reasons, after creating another user under the same role ("Administrator") which is what I use for regular administrative tasks. When I first installed this module on a new site I'm working on, I was unable to find the administrative options screen. Also tried the dev version without results. Then I just forget about it and went on with other development tasks. A couple of days later I had to enable the user 1, in order to export a view (for some reason this task requires the PHP filter module or be logged as user 1) and to my surprise the administrative options of the module popped up in the config screen. Logged out and relogged as user 2, and they vanish again.
I wonder whether this is the intended behavior or just a bug. If it happens to be a feature, it would be a good idea to add some information about this in the project page.
Best regards.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2107945-2.patch | 593 bytes | john cook |
Comments
Comment #1
svipsa commentedModule used "administer access control" permission.
If your user has it he should see settings page.
Can't reproduce.
Comment #2
john cook commentedI've been able to replicate the issue that @Proteo had.
I'm currently using Drupal 7.54 with Node "Authored by" select 7.x-1.4 and the permission "administer access control" does not exist on the system. This means that only user 1 can access the configuration page.
I've created a patch file to add that permission, although a better fix would be to add dependencies if the permission is provided by another module or create a permission for use just by this module.