#47851 closed enhancement (fixed)
When deleting a user, there is no need to consider whether the current user has content.
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 5.3 | Priority: | normal |
Severity: | normal | Version: | 5.2 |
Component: | Users | Keywords: | has-patch |
Focuses: | Cc: |
Description
For example, I try to delete two users: the current user with content and another user with no content.
In this case, the current user cannot be deleted, but the existence of the content is checked because $users_have_content
contains the current user.
As a result, the question “What should be done with content owned by this user?” Is displayed, but it is not actually processed.
Since it is not possible to delete the current user, how about omitting the current user ID from the user's owned content check process?
Attachments (3)
Change History (7)
#1
@
6 years ago
- Milestone changed from Awaiting Review to 5.3
- Owner set to SergeyBiryukov
- Status changed from new to reviewing
- Type changed from feature request to enhancement
#2
@
5 years ago
Thanks for the patch! Found a couple of issues:
- If only the current user is selected, there's a MySQL error:
[You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') LIMIT 1' at line 1
- There's no longer a message that the current user will not be deleted, it's just silently discarded.
47851.diff fixes that.
Note: See
TracTickets for help on using
tickets.
I'm sorry. Previous file is incorrect