With the "User Event Dispatcher" module enabled, event subscribers for HookEventDispatcherInterface::USER_CANCEL do not get invoked if the deletion method is "user_cancel_delete". This appears to be because core does not invoke hook_user_cancel for this deletion method, per the docs for that hook; looks like this was changed in
#705306: user_cancel_delete method calls into a "standard" user_delete_multiple API →
. Though this explains the root cause of the behavior, it's a bit counter-intuitive if you intend to fire something when an account is canceled by any means.
HookEventDispatcherInterface::USER_CANCEL.I would recommend either:
HookEventDispatcherInterface::USER_CANCEL gets called for a "user_cancel_delete" cancellation method by implementing hook_user_delete to synthetically trigger the event;HookEventDispatcherInterface::USER_CANCEL_DELETE that is invoked for this particular event so that an implementer can choose to listen to that event separately from the normal cancellation hook.
Closed: works as designed
4.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
/**
* This hook is NOT invoked for the 'user_cancel_delete' account cancellation
* method. To react to that method, implement hook_ENTITY_TYPE_predelete() or
* hook_ENTITY_TYPE_delete() for user entities instead.
*/
This can be achieved by subscribing to:
\Drupal\core_event_dispatcher\EntityHookEvents::ENTITY_PRE_DELETE\Drupal\core_event_dispatcher\EntityHookEvents::ENTITY_DELETE