Last updated November 2, 2008. Created by ams on November 2, 2008.
Log in to edit this page.
Say you accidentally 'block' your admin account (user 1) by an access rule (for example "%admin%") and cannot log in. You can undo this by accessing the table access and deleting the row where the mask field contains the access rule (in our example "%admin%".)
Using phpMyAdmin this is done by:
- Clicking on the name of the drupal database in the left menu (e.g. "_Drupal")
- Beside the table name (access) and under the Action column click on the Browse icon.
- Find the row in the table with the mask field (e.g. "%admin%") and click on the delete icon beside it.
- Press OK on the confirmation message.
- Now login normally from the frontpage...
Comments
Thanks
... I just did exactly this- %admin% . I was trying to prevent anyone from registering with a username like "administrator" and posing. So how would I go about this? I want to make sure that my unique usernames of special privileges are not wolves in sheep's clothing.
Login after blocking user
Hi
I followed this procedure but when I got to the Browse Icon, it was grayed out and I was unable to click and find the %admin%.
I am pretty new to Drupal so that's unfortunately as technical as I get.
Thanks in advance
Must be disable this option when login with user 1
I thing in the next release of Drupal, it must fix this ridiculous thing. I ask to the developer to make change that the user cannot block himself at access rule administer (especially to user 1).
Sorry for my bad english.
http://seratus-persen.com
NOT the same as blocking user 1's status
Ok, just wasted the last hour thinking I had permission problems in phpmyadmin. This is not correct if you accidentally block yourself the normal way through /admin/user/user
The way to fix this is phpmyadmin > your database > users > edit uid 1 > set status to "1" > thank god you didn't waste as much time as I did
I can't believe drupal lets me block user 1 when I'm logged in as user 1 with no warning! Just clicked the check all box and blocked a few admin accounts to make sure they're logged out for a backup/update.. never thought drupal would let me block user 1, especially without warning!