Skip to:

Opened 12 years ago

Closed 10 years ago

Last modified 10 years ago

#1149 closed task (wontfix)

Ability to permanently delete posts

Reported by: grassrootspa Owned by:
Milestone: 1.1 Priority: low
Severity: normal Version:
Component: General - Administration Keywords:
Cc: kevinjohngallagher


The "Recently Moderated Items" list is great, but there are times when posts really shouldn't be moderated, but rather permanently deleted.

Example: Someone mistakenly posts the same thing twice (duplicate post)

While the admin can obviously "delete" the duplicate post it is still in the system, and shows up under "Recently Moderated Items".

How about the options of being able to permanently delete a post?

This will also make the "Recently Moderated Items" list much more useful since it won't be junked up by things like duplicate posts or mistaken posts!

It will also allow folks to keep their databases leaner ;)

Change History (5)

#1 @sambauers
12 years ago

  • Milestone changed from 1.0.1 to 1.1

#2 @kevinjohngallagher
11 years ago

  • Cc kevinjohngallagher added
  • Priority changed from normal to low
  • Type changed from enhancement to task

A permanent delete option in the backend would be nice, from the Recently Moderated Items list, but if we're going down that route its not really enough.

I feel a slightly better solution, and beyond the scope of 1.1, would be for the recently moderated posts have a reason (spam, double post, content etc) and listed on their own page. It also allows different roles to do differnt things, such as a moderator to mark as spam or delete + enter a reason - and then the key master to permanently delete or archive.

This solution also has the ability to incorporate different levels of "permanently delete", such as just agreeing with the original moderator & archiving but not removing from the database. I know from my own forums, that being able to see how many posts a user made that were removed for content violations has been invaluable, even if i dont want them staying in the Recently Moderated queue for ever.

It's the difference between building a single solution or building a module that you can adapt. - Sorry this is way too long for Trac.

#3 @kevinjohngallagher
11 years ago

  • Milestone changed from 1.1 to 1.5

#4 @johnjamesjacoby
10 years ago

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

This is handled in the bbPress plugin for WordPress, and will most likely not make it into the standalone. Closing as wontfix.

#5 @johnjamesjacoby
10 years ago

  • Keywords permanently delete posts removed
  • Milestone changed from Future Release to 1.1
  • Version 1.0 deleted
Note: See TracTickets for help on using tickets.