Skip to:
Content

BuddyPress.org


Ignore:
Timestamp:
07/04/2011 03:25:38 PM (15 years ago)
Author:
boonebgorges
Message:

Ensures that changes to bp_core_new_subnav_item() introduced in r4599 do not apply to broadly to the groups component.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/bp-core/bp-core-buddybar.php

    r4599 r4600  
    215215         *           and this subnav item is the default for the parent item (which we check by
    216216         *           comparing this subnav item's screen function with the screen function of the
    217          *           parent nav item in $bp->bp_nav).
     217         *           parent nav item in $bp->bp_nav). This condition only arises when viewing a
     218         *           user, since groups should always have an action set.
    218219         */
    219220       
     
    223224               
    224225        // If we *do* meet condition (2), then the added subnav item is currently being requested
    225         if ( ( !empty( $bp->current_action ) && $slug == $bp->current_action ) || ( empty( $bp->current_action ) && $screen_function == $bp->bp_nav[$parent_slug]['screen_function'] ) ) {
     226        if ( ( !empty( $bp->current_action ) && $slug == $bp->current_action ) || ( bp_is_user() && empty( $bp->current_action ) && $screen_function == $bp->bp_nav[$parent_slug]['screen_function'] ) ) {
     227       
    226228                // Before hooking the screen function, check user access
    227229                if ( $user_has_access ) {
Note: See TracChangeset for help on using the changeset viewer.