Problems after removing methods to cancel accounts

[dxvargas]

This module is removing methods to cancel accounts for most users in a hook. The super user (uid 1) can still chose one of these removed methods.

If the selected method is one of the forbidden ones and users have the permission "Cancel own user account", when a user tries to cancel its account we'll see a PHP error (notice) in dblog reports:

Notice: Undefined index: user_cancel_reassign in Drupal\user\Form\UserCancelForm->getDescription() (line 70 of /var/www/html/build/core/modules/user/src/Form/UserCancelForm.php)

Removing options to cancel accounts like this, in a hook, is already a problem because in some cases sites will want one of them. In ECIF there is an example where this hook was removed in a local patch. In another project we'll need to do this too now.

I don't know the requirements to remove methods and only allow them to the super user.
I can only suggest to rethink the all approach here.

[dhamaris]

Hello, I have a similar problem, I would like to be able to delete a user account, why was this hook implemented? I think deleting a user account should be an option for the following reasons:

1. We are testing a module that performs some operations at registration of users but we cannot delete our user afterwards, which makes testing very difficult.
2. Blocking a user's account is very different to removing them, they won't be able to access again unless an admin unblocks them.
3. What happens if our privacy policy says that we only keep users data for 4 years? How do we do it? Are we keeping user's email and data indefinitely or until the site is decommissioned?