Unexpected behaviour when trying to delete a user that is already deleted

Created on 13 January 2020, almost 5 years ago
Updated 29 August 2024, 3 months ago

Problem

If you try to delete a user that is already deleted (via steps below), the page just reloads with no indication of what happened.

Steps to reproduce:

  1. Create a user
  2. Go to admin/people
  3. Edit the user in a new tab
  4. Cancel the user account in the new tab, delete the account and its content
  5. Go back to the admin/people tab where the deleted user is still listed
  6. Select the user and cancel it using the bulk upload actions
  7. See the page reloads without the deleted user but there is no indication of what happened
🐛 Bug report
Status

Closed: works as designed

Version

11.0 🔥

Component
User system 

Last updated about 19 hours ago

Created by

🇮🇳India Hardik_Patel_12 India

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇦🇺Australia pameeela

    I've tried to reproduce this, but I'm not getting the error that was originally reported. In the screencast provided, there is no error visible but I'm not seeing an error in the logs either. It does just fail silently but I don't see why this is a use case to support? Can we close this if there is no error?

  • 🇦🇺Australia pameeela

    Updating title to reflect that there is no error from what I can see. Not sure if I have missed something.

  • 🇬🇧United Kingdom catch

    The silent failure accounts for a potential real race condition.

    e.g. if two users are trying to delete a user at the same time, and one deletes the user individually, and the other users the bulk actions from admin permissions, and the bulk action runs last, then there is just nothing to do because the user is already deleted.

    However it's also not particularly helpful to show a message because e.g. if you want to delete 10 users, and one of them gets deleted between selecting them and submitting the form, and then after the form was submitted, all 10 are deleted (even if one was deleted by someone else), what should be reported? That a user couldn't be deleted because they were already deleted?

    Probably we could log something like that, but it doesn't seem useful to show to users- they could think something has gone wrong when it hasn't.

  • Status changed to Closed: works as designed 3 months ago
  • 🇦🇺Australia pameeela

    Thanks for confirming, I'll close this then since there was no further comment after it was marked as postponed.

Production build 0.71.5 2024