Module lacks some very basic thinking into a complete system failure/destruction; why should it block EXISTING users WITHOUT ASKING ADMIN FIRST, especially for admin accounts, or user1 ? Only for new accounts + sometimes there needs to be an exception. I don't like other users with names like Admin_One, or so.

Deleting modules directory doesn't work.

OpenID doesn't work either to get in.

Gone a month work, because in a few hours I have to travel for some time in areas without internet and still no site.

.

Comments

ClearXS’s picture

Finally found an old post somwhere:

"Go into your database and change the name of your admin user. This is very easy to do with phpMyAdmin: browse your users table, edit uid 1 (which I assume is your admin account) and change the name to something else. You can then log in."

ClearXS’s picture

Priority: Critical » Normal

Ofcourse one can still administer blocks for similar names using wildcards, but one then for sure has to "allow" specific names, in this case the admin/user1 (other admins for example) BEFORE LOGGING OUT

taldy’s picture

Status: Active » Postponed (maintainer needs more info)

Sorry, but we didn't understand what you said at all. Could you please send a clear scenario of the problem you were trying to explain? We need this scenario to understand the problem.

Thank you.

anshuman’s picture

The problem is as follows -

I have the main account with username as admin. This is the user1 account - the first account of my drupal installation.

I then go and set rules that usernames with the word admin is not allowed.

When i try to login next, i notice that my 'admin' account is locked out due to this.

I am effectively locked out, although I am the admin.

salamancavip’s picture

Status: Postponed (maintainer needs more info) » Needs review

I have a very similar problem, went through a number of posts but still can't fix my admin access issue. Failure to login.
I have set a new rule that certain username(s) are not allowed, using only % no other key or sign.
As a result, I cannot login and any of my admin user name is rejected.
I have tried other username e.g xxxx, whatever login is used is a "reserved username".
I have tried to change username (uid 1 and 2) through PHPmyAdmin, no positive result
What is the procedure to follow with PHPmyadmin to unlock this.

Help welcomed. Thx.
Pierre

salamancavip’s picture

Status: Needs review » Fixed

My issue is fixed.

Found the answer with appropriate action on last post of http://drupal.org/node/212175
Go to access, edit admin user 1 and remove the %. Simple with these instructions.
Thank you anyway

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mcarman’s picture

Is this a design flaw? The rule should be processed during registration, NOT during normal user login. I have the same issue with Drupal 6.17. Admin can no longer login after creating rule %admin%.

The point is to have an admin, named 'admin' (and be able to login as admin), without allowing users to have the word 'admin' in their username.

Is there some reason why the rules are processed at normal login, and not just at registration?