Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I installed the latest version of Admin Role (6.x-1.2) in a clean Drupal 6.16 installation. It's the very first module to be installed, and I have added no other roles or users, or done any site configuration. The administrator role was created, but it had no permissions assigned. Has anyone else seen this?
Comments
Comment #1
deggertsen CreditAttribution: deggertsen commentedYes, normally I have to go into the user settings and click save before it gives that admin role all of the permissions. Kind of annoying but yeah...
Comment #2
Peacog CreditAttribution: Peacog commentedHmmm. I don't remember if I saved User settings or not. I'll have to wait til next time I do a clean install. Either way, this seems like a bug. I'm pretty sure it used to work prior to version 6.x-1.2.
Comment #3
jessmagz CreditAttribution: jessmagz commentedI encountered the same scenario on two drupal sites and admin role module behaves similarly on both installation. After enabling the module, administrator role was created but no permission was ever checked.
I was about to uninstall it, so I disabled it first (by unchecking the Admin Role in the list of modules) but after disabling, I noticed that the administrator role then had all the permissions checked.
So on my other sites, I just did the same. After installing admin role module, the administrator role has no permissions checked. I just disabled it, and then re-enabled it and there it worked fine with the administrator role having all the permissions checked.
Is this a bug? Well, perhaps...
Comment #4
james.kujawa CreditAttribution: james.kujawa commentedSame issue happening with me on a fresh Drupal 6.16 install and adminrole-6.x-1.2. Only solution was disabling and re-enabling the module.
Comment #5
Dave ReidI think I already fixed this with the development version in 6.x-1.x-dev.
Comment #6
Dave ReidThis was fixed with http://drupal.org/cvs?commit=311094