[buddypress-trac] [BuddyPress] #3622: bp_get_sitewide_activity_feed_link()

[buddypress-trac at lists.automattic.com]

#3622: bp_get_sitewide_activity_feed_link()
-------------------------------------+--------------------
 Reporter:  webraket                 |       Owner:
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:  1.5.1
Component:  Activity                 |     Version:  1.5
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+--------------------

Comment (by webraket):

 I agree to keep bp_init hooked to init at the default priority.
 Plugins that should also work without BP can simply hook to both.

 BP should however never hook to the default priority of it's own bp_init.
 Or at least never when do_action() or apply_filters() is called at those
 points.

 If a developper only tests his plugin in /plugins, it leads to unexpected
 results when the plugin is used in /mu-plugins.

 Maybe it's even better to move all core functions currently hooked to
 bp_init to something like bp_init_core, then hook bp_init_core to bp_init
 with priority 0.
 That way all priority's for bp_init are keep left for plugins.
 If someone wants to hook to bp_init and do something before BP is actually
 loaded, they can use a negative priority I suppose.

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