[buddypress-trac] [BuddyPress] #5259: Single notifications are deleted instead of being marked as read for plugins

[buddypress-trac]

#5259: Single notifications are deleted instead of being marked as read for
plugins
---------------------------+------------------
 Reporter:  henrywright    |       Owner:
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  1.9
Component:  Notifications  |     Version:
 Severity:  major          |  Resolution:
 Keywords:  dev-feedback   |
---------------------------+------------------

Comment (by boonebgorges):

 I'm generally the backwards compatibility stickler, but in this case I'm
 tempted to agree with johnjamesjacoby. Using `_delete_` functions to refer
 to marking read is going to cause headaches down the line. And the
 following considerations make me think that this is going to be a very
 minor case of breaking backpat:

 - Very few plugins are registering their own notifications. My computer
 with a checkout of plugins.svn.wordpress.org is in a box somewhere in my
 unpacked apartment :) but I'm pretty confident we're talking a very small
 number
 - Notifications are a secondary impression of the original content. So, if
 in some cases they are deleted, we're not really deleting anything of
 primary importance. Keep in mind that *all* notifications are being
 deleted pre-1.9 - this issue will only become visible because the display
 behavior is being changed/augmented by the new Notifications panel. But
 the point remains that sites can't really be relying on persistent
 notifications as it is, because currently notifications are *not*
 persistent.

 So, on balance, I think it's best to move forward with a system that is
 more internally coherent, and let plugin authors catch up. If others
 agree, this is worth putting a brief post up onto bpdevel before beta2.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5259#comment:5>
BuddyPress <http://buddypress.org/>
BuddyPress