I was under the impression that the "inactive" flag for a User-Id was used solely for the registration process. That is, the User-Id is created with the user being inactive and when the user completes the registration process, the User-Id is set to active.
Also, that the "blocked" flag was used to handle things such as multiple failed login attempts.
Am I wrong? Is there somewhere in the system where User-Ids are automatically set to inactive (after they have been set-up and the user has successfully login)?
__________________
JRG
-
☆ A M B ☆
- 24,524 Posts
Your impression is correct. In general, by default newly created users are inactive and must explicitly (manually in the Manager or in code) be set to active.
Blocked is used automatically to block after a specified number of failed login attempts, but it can also be set manually (in the Manager) or in code. The main thing to keep in mind about blocked is that it has a timestamp associated with it, and the user will automatically be unblocked after the amount of time specified in the System Settings.
Am I wrong? Is there somewhere in the system where User-Ids are automatically set to inactive (after they have been set-up and the user has successfully login)?
I don't know of anything that would do this. I've never seen it happen, though I have seen users created through the register process (via Subscribe) who can't log in because they weren't set to active. It's fairly rare. I think I've only seen it twice an all the time I've been having users register. They email me and I set them to active.
-
☆ A M B ☆
- 24,524 Posts
Could be a database corruption. Or some other Manager user doing something?
