BuddyPress.org

@fearthemoose, @rezbiz,

Here “the best guarded secret” finally revealed !
But it’s not a secret, is part of Codex and a multi handled topic subject on this forum.

What we want to do: remove access possibility.
Where: on BuddyBar navigation menu (the one below the profile header).
Specifics: make the activity and forum tabs only visible to the logged in user.

NOTE: The activity tab is shown by default when you visit a profile.

As we are going to hide/remove this tab to visitors, we need to define as first another default tab. If we won’t do that, the visitor will get a Page not found error. Which is not exactly the case here, the page exist but the visitor can’t access it.

Let’s define arbitrary Profile as the new default tab. You can of course define what ever other existing tab on your BuddyBar as default.

Add this line to bp-custom.php
define( 'BP_DEFAULT_COMPONENT','profile' );

Now the mega “open secret” !

The folowing snippet contains almost any BP menu items you can have on a BuddyBar, and includes also the Forum item, in case you use bbPress.
You can remove or comment out those you don’t want to use.
Note also that it is only an example – you have to play with it to fit your need. But at least you have the right syntax to use.
Note also that some profile menu items are user only, such as message or notice. In other words, these are always private.

This function goes preferably to bp-custom.php

function bpfr_hide_tabs() {
global $bp;
	 /**
	 * class_exists() & bp_is_active are recommanded to avoid problems during updates 
	 * or when Component is deactivated
	 */

	if( class_exists( 'bbPress' ) || bp_is_active ( 'groups' ) ) :
        
        /** here we fix the conditions. 
        * Are we on a profile page ? | is user site admin ? | is user logged in ?
        */
	if ( bp_is_user() && !is_super_admin() && !is_user_logged_in() ) {

        /* and here we remove our stuff ! */
		bp_core_remove_nav_item( 'activity' );
		bp_core_remove_nav_item( 'friends' );
		bp_core_remove_nav_item( 'groups' );
		bp_core_remove_nav_item( 'forums' );
	}
	endif;
}
add_action( 'bp_setup_nav', 'bpfr_hide_tabs', 15 );

Some other hints for privacy
if you want to allow only the profile owner to view some tabs, replace
!is_user_logged_in by !bp_is_my_profile() – this scenario doesn’t need a check for logged in users as it is made by bp_is_my_profile.

If you want only to make a profile private, read here.

If you want to remove a sub-nav item (ie. View on Profile), you use something like:
bp_core_remove_subnav_item( 'profile', 'view' );

Many other possibilities for navigation are also available, including for groups. Several examples are given on Codex, here.

And if not enough, RTFM and search the forum ! 🙂

Have fun !

If you are on latest version of buddypress( > 2.6 ), the following code will work:

//hide setting nav in profile
function w24dr_remove_settings_nav() {
    $bp = buddypress();
    $bp->members->nav->delete_nav( bp_get_settings_slug() );
}
add_action( 'bp_setup_nav', 'w24dr_remove_settings_nav' );

//redirect settings to main profile page
function w24dr_redirect_settings_nav(){
    if( bp_is_user() && bp_is_current_component( bp_get_settings_slug() ) ){
        wp_redirect( bp_displayed_user_domain() );
        exit();
    }
}
add_action( 'template_redirect', 'w24dr_redirect_settings_nav' );

But it still doesn’t remove ‘settings’ nav from adminbar. You need to work some more to remove it from there.

Hi,

you can try to remove the private message button from the template or hide it with CSS.
And add a custom one who leads to admin inbox.

The link should look like
http://your-site.com/members/YOU/messages/compose/?r=THE ADMIN&_wpnonce=an_alpha_numeric_value

See here how you may code this

Codex and Forum are your friends to search about template customization.

Hi,

bp’s Usermenu is added to wp_admin_menu on the Toolbar, under Howdy. This BP menu ID is “my-account”.

When you’re on a profile page, you see also these items in the Buddymenu, below the profile header cover.

Some working examples here:
Remove an item from Usermenu

Remove an item from Buddymenu

Since 2.6, BuddyPress use a navigation API. See here for many use case.

Read also WP codex about admin bar menus.

Where to put BuddyPress custom code ?
Usually into bp-custom.php. This file is to BP code what a child theme is to a theme: a safe place with high priority where nothing get to loose when an update occurs !

Child’s functions.php should be reserved to whatever you need for the theme itself.
That said, it can happen(rarely) that some custom code won’t work from within bp-custom. In this case, feel free to remove it from bp-custom and give it a try inside child’s functions.php.

As novice, you’re invited to read BP and WP codex if you want to customize.

The whole idea is that the profile is locked down completely so I don’t want the viewer to see the activity or any other part unless they fit the criteria laid out by the member.

I understand that. But as the member appears on SWA and directories, you have to go deeper into BP and hide his activities, remove it from directories and so on. Or as already said, give this as “ultimate” option, with a big warning to site admins – and to the user. Something like: if you choose this option, your whole profile (activity, friends and group membership list) will be hidden to all members and visitors.

It was initially for a client of yours, ok, but that’s a specific use case. I would better leave that possible from inside the plugin code only (ie. a filter that a dev could activate) and give a smoother option for common community usage to the majority of BP users.

You could completely customize the Admin-bar. This snippet should help, put in either the functions.php file of your theme, or in the bp-custom.php file. It should give you a good idea of what is possible. I’m hiding the W menu. You could probably hide the Site dropdown altogether and then craft your own dropdown with links to different items. Particularly if this is a single install of BP, and not a Network/Multisite install, there really isn’t any reason for your users to see the Site dropdown:

	/**
	 * Adds custom "Home" menu to WP Adminbar.
	 *
	 * Also removes the "WP logo" menu.
	 *
	 * @param object $wp_admin_bar The WP Admin Bar object
	 */
	public function add_custom_parent_menu( $wp_admin_bar ) {

		/**
		 * Removing the "W" menu
		 */
		$wp_admin_bar->remove_menu( 'wp-logo' );

		/**
		 * Create a "Home" menu.
		 *
		 * First, just create the parent menu item.
		 */
		$wp_admin_bar->add_menu( array(
			'id' => 'commonlinks',
			'parent' => '0', //puts it on the left-hand side
			'title' => 'Home',
			'href' => ('http://domain.com/activity')
		) );

		/**
		 * Add submenu items to "Home" menu.
		 */
		// Only show the following for logged-in users
		if ( current_user_can( 'read' ) ) {
			// Support link
			$wp_admin_bar->add_menu( array(
				'id' => 'support',
				'parent' => 'commonlinks',
				'title' => 'Support',
				'href' => ('http://domain.com/support')
			) );

			// Blog request form
			$wp_admin_bar->add_menu( array(
				'id' => 'blogrequest',
				'parent' => 'commonlinks',
				'title' => 'Feedback',
				'href' => ('http://domain.com/feedback' )
			) );

			// Developers blog
			$wp_admin_bar->add_menu( array(
				'id' => 'developments',
				'parent' => 'commonlinks',
				'title' => 'Developments',
				'href' => ('http://domain.com/developments' )
			) );

		}

	}

You could customize the adminbar completely, using this snippet. I’m hiding the W menu, but you could probably hid the Sites menu and then add your own dropdown with the requisite links.

http://www.wpbeginner.com/plugins/how-to-add-edit-re-order-or-hide-wordpress-admin-menus/

         /**
	 * Adds custom "Home" menu to WP Adminbar.
	 *
	 * Also removes the "WP logo" menu.
	 *
	 * @param object $wp_admin_bar The WP Admin Bar object
	 */
	public function add_custom_parent_menu( $wp_admin_bar ) {

		/**
		 * Removing the "W" menu
		 */
		$wp_admin_bar->remove_menu( 'wp-logo' );

		/**
		 * Create a "Home" menu.
		 *
		 * First, just create the parent menu item.
		 */
		$wp_admin_bar->add_menu( array(
			'id' => 'commonlinks',
			'parent' => '0', //puts it on the left-hand side
			'title' => 'Home',
			'href' => ('INSERT LINK HERE')
		) );

		/**
		 * Add submenu items to "Home" menu.
		 */
		// Only show the following for logged-in users
		if ( current_user_can( 'read' ) ) {
			// Support link
			$wp_admin_bar->add_menu( array(
				'id' => 'support',
				'parent' => 'commonlinks',
				'title' => 'Support',
				'href' => ('INSERT LINK HERE')
			) );

			// Blog request form
			$wp_admin_bar->add_menu( array(
				'id' => 'blogrequest',
				'parent' => 'commonlinks',
				'title' => 'Stuff',
				'href' => ('INSERT LINK HERE' )
			) );

			// Developers blog
			$wp_admin_bar->add_menu( array(
				'id' => 'developments',
				'parent' => 'commonlinks',
				'title' => 'Developments',
				'href' => ('INSERT LINK HERE' )
			) );

		}

	}

Hi,

two snippets to remove profile and group items.

function bpex_hide_profile_menu_tabs() {

	if( bp_is_active( 'xprofile' ) ) :

	if ( bp_is_user() && !is_super_admin() && !bp_is_my_profile() ) {
	//	BP's profile main menu items. Comment those to show.
	//	bp_core_remove_nav_item( 'activity' );
		bp_core_remove_nav_item( 'profile' );
		bp_core_remove_nav_item( 'friends' );
		bp_core_remove_nav_item( 'groups' );
	//	exist only if you use bbPress
		bp_core_remove_nav_item( 'forums' ); 

	//	BP's profile main menu items. Comment those to show.
	//	bp_core_remove_subnav_item( 'activity', 'personnal' );
		bp_core_remove_subnav_item( 'activity', 'mentions' );
		bp_core_remove_subnav_item( 'activity', 'favorites' );
		bp_core_remove_subnav_item( 'activity', 'friends' );
		bp_core_remove_subnav_item( 'activity', 'groups' );
	}
	endif; 
}
add_action( 'bp_setup_nav', 'bpex_hide_profile_menu_tabs', 15 );

function bpex_remove_group_tabs() {  

	if ( ! bp_is_group() ) {
		return;
	}

	$slug = bp_get_current_group_slug();

		// hide items to all users except site admin
	if ( !is_super_admin() ) {

	//	bp_core_remove_subnav_item( $slug, 'members' );
		bp_core_remove_subnav_item( $slug, 'send-invites' );
	//	bp_core_remove_subnav_item( $slug, 'admin' );
	//	bp_core_remove_subnav_item( $slug, 'forum' );
	}

}
add_action( 'bp_actions', 'bpex_remove_group_tabs' );

It’s the same principle, but not the same syntax since 2.6

To hide tabs on groups, you need to specify the component. Note that all menu items (nav and subnav items) are considered as sub-nav, they have not the same distinction as on member or activity menus.

Use another function for groups. Try this.

function bpex_remove_group_tabs() {  

	if ( ! bp_is_group() ) {
		return;
	}

	$slug = bp_get_current_group_slug();

		// hide items to all users except site admin
	if ( !is_super_admin() ) {

	//	bp_core_remove_subnav_item( $slug, 'members' );
		bp_core_remove_subnav_item( $slug, 'send-invites' );
	//	bp_core_remove_subnav_item( $slug, 'admin' );
	//	bp_core_remove_subnav_item( $slug, 'forum' );
	}

}
add_action( 'bp_actions', 'bpex_remove_group_tabs' );

To get more usage examples, see here:

Navigation API

Add this snippet to bp-custom.php and give it a try.

function bpex_hide_profile_menu_tabs() {

	if( bp_is_active( 'xprofile' ) ) :

	if ( bp_is_user() && !is_super_admin() && !bp_is_my_profile() ) {
	//	BP's profile main menu items. Comment those to show.
	//	bp_core_remove_nav_item( 'activity' );
		bp_core_remove_nav_item( 'profile' );
		bp_core_remove_nav_item( 'friends' );
		bp_core_remove_nav_item( 'groups' );
	//	exist only if you use bbPress
		bp_core_remove_nav_item( 'forums' ); 

	//	BP's profile main menu items. Comment those to show.
	//	bp_core_remove_subnav_item( 'activity', 'personnal' );
		bp_core_remove_subnav_item( 'activity', 'mentions' );
		bp_core_remove_subnav_item( 'activity', 'favorites' );
		bp_core_remove_subnav_item( 'activity', 'friends' );
		bp_core_remove_subnav_item( 'activity', 'groups' );
	}
	endif;
}
add_action( 'bp_setup_nav', 'bpex_hide_profile_menu_tabs', 15 );

For anyone who is looking for the solution for not being able to save buddypress settings.

Various plugins cause issues with adding various extra css in the admin area.

in my case there was a css file from a Codecanyon Woozone plugin which hid the P tags in the buddypress options pages

use firebug and find the bottom div that cotnains the submit button and disable any css that is hiding it and you can click the submit button.

after you have done that you might want to tell the plugin developer that caused the issue about it.

TLDR the button is there its probably just hidden. use firebug or chrome tools to unhide it and click save.

Hi @navyspitfire,

when you pick up code somewhere, you should also read the comments. The solution to your issue was in one of them.

Here is what wil exclude site admin from members directory and exclude also the logged_in user. The total member count will also be adjusted correctly on All members [x] tab and for the pagination count. $count-2 instead of $count-1 do the trick.

Excluded members, incl. admin, are of course excluded from search.

function bpex_hide_admin_on_member_directory( $qs=false, $object=false ){

	// Id's to hide, separated by comma
	$excluded_user = '1' ;

	// hide to members & friends 
	if($object != 'members' && $object != 'friends')
	return $qs;
	
	$args = wp_parse_args($qs);
	
	if(!empty($args['user_id']))
	return $qs;	
	
	if(!empty($args['exclude']))
	$args['exclude'] = $args['exclude'].','.$excluded_user;
	else
	$args['exclude'] = $excluded_user;
	
	$qs = build_query($args);
	
	return $qs;
	
}
add_action( 'bp_ajax_querystring','bpex_hide_admin_on_member_directory', 20, 2 );

// once admin is excluded, we must recount the members !
function bpex_hide_get_total_filter( $count ){
	return $count-2;
}
add_filter( 'bp_get_total_member_count', 'bpex_hide_get_total_filter' );

function bpex_exclude_loggedin_user( $qs = false, $object = false ) {

 //list of users to exclude
 if( !is_user_logged_in() )
     return $qs;

 //if the user is logged in , let us exclude her/him
 $excluded_user=  get_current_user_id();
  
 if( $object !='members' )//hide for members only
	return $qs;
  
 $args=wp_parse_args($qs);
  
 //check if we are listing friends?, do not exclude in this case
 if( !empty( $args[ 'user_id' ] ) )
	return $qs;
  
 if( !empty( $args['exclude'] ) )
	$args['exclude'] = $args['exclude'] .','. $excluded_user;
 else
	$args['exclude'] = $excluded_user;
  
	$qs = build_query( $args );
  
 return $qs;
  
}
add_action('bp_ajax_querystring','bpex_exclude_loggedin_user', 20, 2 );

Codex Reference

Playing with the user’s ID in different contexts

@gerwinb, use this snippet for 2.6 +. Corrected, tested and approved by @imath

function gwb_remove_group_admin_tab() {
	if ( ! bp_is_group() || ! ( bp_is_current_action( 'admin' ) && bp_action_variable( 0 ) ) || is_super_admin() ) {
		return;
	}
	// Add the admin subnav slug you want to hide in the
	// following array
	$hide_tabs = array(
		'group-avatar' => 1,
		'delete-group' => 1,
	);
	$parent_nav_slug = bp_get_current_group_slug() . '_manage';
	// Remove the nav items
	foreach ( array_keys( $hide_tabs ) as $tab ) {
	  // Since 2.6, You just need to add the 'groups' parameter at the end of the bp_core_remove_subnav_item
		bp_core_remove_subnav_item( $parent_nav_slug, $tab, 'groups' );
	}
	// You may want to be sure the user can't access
	if ( ! empty( $hide_tabs[ bp_action_variable( 0 ) ] ) ) {
		bp_core_add_message( 'Sorry buddy, but this part is restricted to super admins!', 'error' );
		bp_core_redirect( bp_get_group_permalink( groups_get_current_group() ) );
	}
}
add_action( 'bp_actions', 'gwb_remove_group_admin_tab', 9 );