In the edit screen for user #1 (user/1/edit), you can click block, and then save, you will be instantly kicked out of your superuser account, and not be able to login without manipulating the database directly... (setting status back to 1 in the user table)

Why would one want to do this...? You wouldn't... and it should be fixed. I can't imagine any use for this behavior...

I'm willing to bet it works the same in Drupal 5 and 7... Anybody want to test those versions...?

Comments

dddave’s picture

dddave commented
Status: Active » Closed (works as designed)

For D7: #472074: Don't let the all administrator accounts get blocked

For D6 exists http://drupal.org/project/userprotect

I agree that blocking UID1 shouldn't be possible (same for cancellation of UID1 which is prevented in D7) but this would be a massive change that won't be made for D6.