Make WordPress Core

Opened 18 years ago

Closed 17 years ago

Last modified 17 years ago

#7455 closed enhancement (invalid)

WordPress should confirm when doing a mass delete

Reported by: viper007bond's profile Viper007Bond Owned by: noel's profile noel
Milestone: Priority: normal
Severity: normal Version: 2.6
Component: Administration Keywords:
Focuses: Cc:

Description

If you mark some posts at Manage -> Posts and click "Delete", you should be asked "Are you sure?" for safety.

Attachments (2)

delete-confirm.patch (3.3 KB) - added by noel 17 years ago.
This is patched for 2.7 and the dropdown mechanism.
confirm-delete-updated.patch (4.1 KB) - added by noel 17 years ago.
Updated version of patch.

Download all attachments as: .zip

Change History (11)

@noel
17 years ago

This is patched for 2.7 and the dropdown mechanism.

#1 @noel
17 years ago

  • Owner changed from anonymous to noel

#2 @ryan
17 years ago

I'm not getting an AYS. Tested on FF. Updated forms.js version in the script loader and still nothing.

#3 @noel
17 years ago

  • Cc ryan@… added

Sorry, forgot to include the script-loader stuff. Seems to work for me in FF and Safari.

@noel
17 years ago

Updated version of patch.

#5 @noel
17 years ago

  • Keywords patched added; needs-patch removed

I believe this patch is a necessary first step, although I think that undo capability is a nice idea.

#6 follow-up: @Otto42
17 years ago

I don't like the confirmation idea for three reasons.

First, confirmations never work. People click OK buttons brainlessly.

Second, it still offers no way back if you do confirm.

Third, this particular instance seems to be javascript dependent in a big way.

For most cases like this, this sort of thing is already a solved problem. Instead of deleting, the first delete should mark the thing as deleted instead of actually deleting it. Then, we have a "Trash" or something which the user can manually empty or which auto-empties on some regular basis.

In the specific case of WordPress, we should have a "Trash" post_status or something, which has another tab on the Manage->Posts screen. Then users can go there to find accidentally deleted posts.

Note that in order to avoid confusion, the only things allowed to be done to a Trashed post should be to recover or view its contents. No editing, no nothing else. Also, recovery of a post should be allowed to be to either a published or to a draft status.

Only when the trash is emptied are all the posts and comments and such related to that post actually deleted from the DB.

#7 in reply to: ↑ 6 @caesarsgrunt
17 years ago

I completely agree with everything you say above, Otto.
I've made a first attempt at creating a "trash" status at #4529; have a look and let me know what you think...

#8 @noel
17 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Closing this ticket as it's invalid since the trash status will be taking over any confirmation.

#9 @jacobsantos
17 years ago

  • Keywords patched removed
  • Milestone 2.7 deleted
Note: See TracTickets for help on using tickets.