BuddyPress.org

This is such a huge, complicated issue. I’ve not even tried this myself. BP 1.2’s theme system changed, so you will be reverting back to the new default theme unless you build a new theme. Any specific BuddyPress plugins you are running will almost certainly stop working in some way. You’ve also got several WordPress versions to step through.

What version of WordPress are you using? I’m guessing WPMU 2.7?

This may work for you:

https://buddypress.org/community/groups/welcome-pack/

For example at the top of the twentyten theme’s style.css is the following line:
`Tags: custom-menu, sticky-post, microformats, rtl-language-support, translation-ready`
If you change it to:
`Tags: buddypress, custom-menu, sticky-post, microformats, rtl-language-support, translation-ready`
then that warning will go away.

However that warning is to tell you that the theme isn’t buddypress compatible so it needs to be converted/updated.

This can be done by following the guide in the buddypress codex: https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/

Some themes, such as Suffusion, have their own conversion pack, so it would be worth checking to see if one is available first.

Thank you all for posting this! I’ve been reading for hours and this has fixed my issues.

I’m running BP on a network install and want ALL subdomains to have use of BP. It was working on the main install but as I created subdomains, the BP pages (Activity, Members, etc,) was giving me 404 errors. I went down the htaccess rabbit hole for a while and gave up. Started at the beginning and reading thru all the forums that looked related and found this.

@WesCleveland – The bp-custom.php works like a charm so far. Thanks for posting your solution.

@ScrltOTara

Go to the group in question.
Click Admin > Manage Members > Remove from group (next to the member you want to remove)

We’ve fixed this tricky one for BuddyPress 1.3, too

Thanks for your comments, and good luck with your site.

@friederb Glad you resolved the issue on your own Thanks for sharing what the problematic plugin was.

Deactivate all plugins except BuddyPress and change to bp-default theme, does same behavior apply? WP/BP versions?

This would be the way to do that – https://codex.buddypress.org/extending-buddypress/customizing-labels-messages-and-urls/

Deactivate all plugins except BuddyPress and change to bp-default theme to start troubleshooting what’s causing the erroneous behavior.

Wonderful, Tom. A minor tweak to your solution:

The original remove_action may not always work
remove_action( ‘bp_adminbar_menus’, ‘bp_adminbar_login_menu’, 2 );
since we can’t guarantee that buddypress plugin is parsed before this fix plugin. A slight modification I made works for me:

I change add_action( 'bp_adminbar_menus', 'custom_bp_adminbar_login_menu', 2 );
to
add_action( 'bp_adminbar_menus', 'custom_bp_adminbar_login_menu', 1 );
so it will run before the original bp_adminbar_login_menu runs, but after the plugins are parsed and hooks are registered, and then in custom_bp_adminbar_login_menu, I added
remove_action( 'bp_adminbar_menus', 'bp_adminbar_login_menu', 2 );

Therefore, the whole thing looks like:

function custom_bp_adminbar_login_menu() {
global $bp;

remove_action( 'bp_adminbar_menus', 'bp_adminbar_login_menu', 2 );

if ( is_user_logged_in() )
return false;

$redirecturl = $bp->root_domain . '/wp-login.php?redirect_to=' . urlencode( $bp->root_domain ) . esc_url( $_SERVER );
echo '
' . __( 'Log In', 'buddypress' ) . '

';

// Show “Sign Up” link if user registrations are allowed
if ( bp_get_signup_allowed() ) {
echo '
' . __( 'Sign Up', 'buddypress' ) . '

';
}
}
add_action( 'bp_adminbar_menus', 'custom_bp_adminbar_login_menu', 1 );

I agree with fbutera101, though — I am having a hard time imagining a use case where users want to leave where they already are after logging in.