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.Hi guys,
I have the following case for my website. I have alot of users, and sometimes a user wants to cancel it's account. I have choosen the option 'Disable the account and keep its content.'. This is because they can pay for their account, and I don't want to delete the account when they have payed for it (can get messy). But now there is another problem. As the account is still there and disabled, the user might think that he wants to create an account again. But he can't use the same username (obviously) and email. He will get the following errors on creating the account:
The name *** is already taken
The e-mail address **** is already registered. Have you forgotten your password?
And when he wants to ask for his password, entering his email:
Sorry, *** is not recognized as a username or an e-mail address.
Whatever the solution should be, this can be done better. As for me, re-enabling would be best.
blocked is a bad state. it should consist of:
- Active
- Disabled (An user cancelled his account, or a user didn't confirmed his account yet, this can be undone by the user itself.)
- Banned (An admin banned this user temporarily)
- Blocked (The user is permantly blocked)
Comments
Comment #1
GBurg CreditAttribution: GBurg commentedto be honest, I feel like that the current 2 states are not sufficient enough. I mean, blocked is a bad state. it should consist of:
Active
Disabled (An user cancelled his account, or a user didn't confirmed his account yet, this can be undone by the user itself.)
Banned (An admin banned this user temporarily)
Blocked (The user is permantly blocked)
Maybe banned and blocked look alto like each other. But you must recognize the difference between Disabled and Banned/Blocked. If you go and sit down for it, there might be even more states a user accoutn could be in.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedThis can be handled via a custom module (maybe one in contrib already).
Moving to D8 since all feature requests need to go to the developing version.
Comment #5
dpiFrom #1828914-1: Self disabled accounts should be possible to re-enable
The problem is there is no difference difference between 'active' and 'disabled'. Disabled doesn't mean anything..
Recording soft states like "disabled" or "temporarily blocked" can be managed externally by contrib.
Comment #6
dpi