This is just a general feature request to improve admin user interface. Not quite sure where it best goes or if feature requests are still in consideration for D7 or how this is handled in D8..

I think the nomenclature of "blocking" a user is ambiguous and the default is not necessarily what I or the average site admin would expect and it's confusing at first glance the difference between blocking and cancelling.

I might suggest something like the following
- change "blocked" to "blocked from logging in" because that seems to be the only restriction that a simple "blocked" does
- add a user status category "cancelled" or "disabled" to help distinguish. (eg in the case of "Disable the account and unpublish its content." ) that would show up on the admin/people page.
- add "cancel account" option other places like the user edit page under "status" user/XYZ/edit to help make it clearer that there are multiple ways to block/cancel accounts in order to get the behavior you intend as an admin.

Use case: came across this ambiguity when I "blocked" a user on my site, and then was surprised that their content and comments was still visible to other users. "blocked" did not unpublish the content, which is what I wanted and expected to happen. then i realized i had to go through the cancel process instead. #2092441: Don't send commons_notify mails to blocked users

Comments

Version: 7.24 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

AaronMcHale’s picture

Status: Active » Closed (outdated)
Related issues: +#3229136: Rationalise our use of "block" and "disable" relating to users