BuddyPress.org

@masoud1111,

You’re talking about 2 different things: profile and groups. Let me explain you a little…

On the buddy nav bar, navigation looks similar but doesn’t work the same way on profile and on group page. While profile navigation use nav and sub-nav, the group navigation use only sub-nav.

Also, as documented on codex, define('BP_DEFAULT_COMPONENT', '...' ); is a constant related to a component, not a sub-nav tab. It let you define the default landing component, but not the one or other sub-nav tab. For example on profiles, the component Activity has 4 sub-nav attached to it: personnal, mentions, favorites, friends, groups

To get one of them, you need to specify a new default tab, not another component. 🙂

Buddybar main nav items on profile page
Activity Profile Friends Groups Forums (if you use group forums)

Default tab is Activity/personnal. To change it for “Friends” you use the constant:
define('BP_DEFAULT_COMPONENT', 'friends' );

To change the default landing tab from (Component/sub-tab). For example Activity/personnal to Activity/mentions, you define a new nav default tab with a function like this one:

function bpex_set_member_default_nav() {
 
    bp_core_new_nav_default (
        array(
            'parent_slug'       => buddypress()->activity->id,
	   // other "activity" sub_nav slugs : personal favorites friends groups
            'subnav_slug'       => 'mentions',
            'screen_function'   => 'bp_activity_screen_mentions'
        )
    );
}
add_action( 'bp_setup_nav', 'bpex_set_member_default_nav', 20 );

For groups, it’s a similar technique, but a different syntax. The following example is a bit sophisticated, as it let you change the landing tab differently for each defined group.
Depending each group activity or target, you can choose a different default tab.
In this example, the kill bill group has Forum as landing tab, while Leon’s group use the group member directory.

function bpex_custom_group_default_tab( $default_tab ){
	/**
	 * class_exists() is recommanded to avoid problems during updates 
	 * or when Groups Component is deactivated
	 */
	if ( class_exists( 'BP_Group_Extension' ) ) : 
	
	$group = groups_get_current_group();//get the current group
	
	if( empty( $group ) ) {
	 return $default_tab;
	}
		switch($group->slug){
			
			case 'kill-bill': // group name (use slug format)
			$default_tab='forum';
			break;
			
			case 'leon':
			$default_tab='members';
			break;
			
			default:		
			$default_tab='home';// the default landing tab
			break;
			
		}
	
	return $default_tab;
	
	endif; // end if ( class_exists( 'BP_Group_Extension' ) )
}
add_filter('bp_groups_default_extension','bpex_custom_group_default_tab');

All this tested and working with BP 2.7.2 / Twenty Sixteen

Hi,

no of course ! Read 2.7.2 changelog.

If you use a child theme or a third party theme, ensure it is updated for BP 2.7+: verify the templates.

Template Updates 2.7

Hi,

all is explained in the doc !

Changing Internal Configuration Settings

Navigation API

Try the solution near the bottom of this codex page:
https://codex.buddypress.org/emails/#filter-from-address-and-name

add_action( 'bp_email', function( $email_type, $email_obj ) {
$email_obj->set_from( "custom@example.com", "Custom Website Name" );
}, 10, 2 );

I think you are looking for BP Registration options – that provides you with new member moderation.
https://wordpress.org/plugins/bp-registration-options/

If you are new to BuddyPress I’m developing a site aimed at helping people get the most out of BuddyPress http://buddyuser.com

You can find this information in the codex https://codex.buddypress.org/themes/buddypress-cover-images/

define( 'BP_GROUPS_DEFAULT_EXTENSION', 'members' );

change members to the slug of the extension and then that tab will load when you click a link to a group.

more configurations here https://codex.buddypress.org/getting-started/customizing/changing-internal-configuration-settings/

use this plugin https://wordpress.org/plugins/buddypress-custom-profile-menu/

Under Settings in the admin click BuddyPress. Then the tab Pages and re associate the page to the component.

This has got to be plugin conflict or theme related issue since avatar and cover image uploads work when BuddyPress is running standalone. I’d try deactivating all other plugins and if that does not work then switching to the 2016 theme to check