#26709 closed enhancement (fixed)
Deleting users makes it unclear that pages will be deleted
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.9 | Priority: | normal |
Severity: | normal | Version: | 3.8 |
Component: | Text Changes | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
When deleting a user, you are warned that "all posts" from this user will be deleted. While this is accurate, I've had two clients now that have deleted the user and lost pages because "they weren't posts". Clearing up that language would be helpful for users.
Attachments (2)
Change History (11)
#1
@
11 years ago
- Component changed from Users to Text Changes
- Keywords has-patch added
- Milestone changed from Awaiting Review to 3.9
#2
@
11 years ago
Should it be 'content' instead of 'posts and pages' since Custom Post Types could be in use?
#3
@
11 years ago
I tested this patch and it worked but I suggest an additional text change (in the attached patch/diff) that catered for multiple users.
I've gone for the "content" approach as when you do delete a user and their custom post type content then it is more than "posts and pages".
#5
follow-up:
↓ 7
@
11 years ago
I just came to submit a bug+patch for exactly this issue.
One change I would recommend, though, to seanchayes patch would be to have the prompt text give examples of content that would be deleted.
For example: What should be done with content (such as pages, posts, and media) owned by this user?
This ticket was mentioned in IRC in #wordpress-dev by helen. View the logs.
11 years ago
#7
in reply to:
↑ 5
@
11 years ago
Replying to jwhyatt:
One change I would recommend, though, to seanchayes patch would be to have the prompt text give examples of content that would be deleted.
For example: What should be done with content (such as pages, posts, and media) owned by this user?
I usually prefer more detail, but even with the "such as" that's probably getting a little too specific. It's completely plausible for a site to be using none of those post types.
Bringing the changes into multisite and help, then getting it in.
This patch should resolve the issue