Skip to:

Opened 14 years ago

Closed 6 years ago

#2130 closed enhancement (maybelater)

Content deletion

Reported by: johnjamesjacoby's profile johnjamesjacoby Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: Priority: minor
Severity: normal Version:
Component: Core Keywords: trac-tidy-2018


It might be worth adopting the WordPress method of deleting data, and simply marking it as deleted rather than actually deleting the data from the DB.

Adding an is_deleted column to most of the tables, and adjusting the logic in the queries is all it should take.

I'm open to patching this if we think it's worth doing.

Change History (8)

#1 @boonebgorges
14 years ago

  • Component set to Core

A big +1 to this

#2 @DJPaul
14 years ago

  • Milestone changed from 1.3 to 1.4

I assume we can get this "for free" with custom post types, so bumping to 1.4.

#3 @boonebgorges
14 years ago

Cool. Though items like activities that might not be mapped into a CPT might still need something custom built. That's a bridge we can cross when we get to it.

#4 @boonebgorges
13 years ago

  • Severity set to normal

DJPaul - If you're going to be adding Akismet support to BP core by modding the activity table schema, it would be a good time to implement this (at least for activity). Once the schema has been modded, the rest of the work is very straightforward. We'll just (probably) need a new piece of UI for emptying the trash, or for *really* deleting an activity item. Definitely puntable in terms of priorities, but something to keep in mind if you will be messing with the schema anyway.

#5 @boonebgorges
12 years ago

I think we should do this (it's increasingly important, given the increased focus on admin screens), but it's too late for this cycle. Let's do it next time around.

#6 @boonebgorges
12 years ago

  • Milestone changed from 1.6 to Future Release

#7 @DJPaul
6 years ago

  • Keywords trac-tidy-2018 added

We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.

Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.

If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.

For more information, see
or find us on Slack, in the #buddypress channel:

#8 @DJPaul
6 years ago

  • Milestone Awaiting Contributions deleted
  • Resolution set to maybelater
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.