[buddypress-trac] [BuddyPress] #3579: Issues with legacy plugin directory page and wordpress Standard

buddypress-trac at lists.automattic.com buddypress-trac at lists.automattic.com
Thu Sep 15 18:38:54 UTC 2011

#3579: Issues with legacy plugin directory page and wordpress Standard
 Reporter:  sbrajesh     |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Core         |    Version:  1.5
 Severity:  trivial      |   Keywords:
 Just came across this weird issue, though It's not a big deal. Posting
 here to make sure if someone else has the same trouble can get the

 It seems some load order has changed in bp 1.5 beta1 to bp 1.5 rc1.

 Earlier, if you registered globals on "bp_init" action with priority 6(In
 fact I have been using 6 for many plugins), The bp_is_current_component
 used to return correct value on directory page.

 In bp 1.5 Rc1, this works for wordpress multisite but not for wordpress
 standard. Just tested and it seems the function bp_core_set_uri_globals is
 unable to set(as It is called on bp_init with priority 2) the
 $current_component if you register it late. I could not understand why It
 worked for Multisite though.

 Looking at the loading orders, I switched the registering of plugin
 globals to bp_loaded and it worked for both wordpress standard as well as
 wordpress multisite.

 I haven't modeled any of my component based on the skeleton component, so
 I may be using the wrong loading order.

 Any thoughts on why there is inconsistency in wp/wpms.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/3579>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list