[buddypress-trac] [BuddyPress] #5148: Make notifications a separate component

buddypress-trac noreply at wordpress.org
Wed Nov 6 18:43:19 UTC 2013

#5148: Make notifications a separate component
 Reporter:  johnjamesjacoby       |       Owner:  johnjamesjacoby
     Type:  defect (bug)          |      Status:  new
 Priority:  normal                |   Milestone:  1.9
Component:  Notifications         |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  needs-patch needs-ui  |

Comment (by johnjamesjacoby):


 Because there's no full-text of the notification itself, bp-notifications
 should be responsible for putting the item_id, secondary_item_id,
 component_name, component_action, and date_notiified into real words.

 In the current implementation, `notification_callback` is used as a
 singlular/cumulative catch-all; `bp_activity_format_notifications()` is a
 good example. `bp_core_get_notifications_for_user()` will be used as a
 foundation to loop through active notifications, and build the full-text
 strings for each line item, without grouping all similar notifications
 into 1 to be acknowledged.

 We'll also need to change the behavior from `delete` to `mark read` and
 make sure `bp_core_get_notifications_for_user()` only shows unread
 notifications. This won't be difficult, but will likely touch each
 component, since they are individually responsible for knowing when their
 notifications are no longer new.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5148#comment:13>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list