BuddyPress.org

@tyler ~ I’ve now built two similar ‘medical related’ sites where the privacy was of utmost concern and I used my code from above beautifully. You could drop the plugin and the secondary install and just use that for any pages you want to keep private from both unregistered users and spiders/robots.

I’ve submitted a ticket for the issue of wp-login not being registered as a root_component:

https://trac.buddypress.org/ticket/2074

There’s a patch attached to that ticket, to make the necessary changes to bp-core.php

And here’s my revision of the lockout plugin:

<?php

/*

Plugin Name: BuddyPress Lockdown

Plugin URI: https://buddypress.org/

Description: Lock down your BuddyPress site if a user is not logged in.

Author: Andy Peatling & Andrew_S1

Version: 1.1

Author URI: https://buddypress.org/

Site Wide Only: true

*/



function bp_lockdown() {

global $bp;



if ( BP_REGISTER_SLUG != $bp->current_component &&

BP_LOGIN_SLUG != $bp->current_component &&

BP_LOGIN1_SLUG != $bp->current_component &&

!is_user_logged_in() ) {



bp_core_redirect( site_url( BP_LOGIN_SLUG ) );

}

}

add_action( 'bp_init', 'bp_lockdown');

?>

Code revised to give protection even if buddypress gets deactivated: adds a second line of defence by hooking a wordpress action too. I’ve assumed that there’s no conflict here, but I don’t know if these two hooks collide. It seems to work ok.

<?php

/*

Plugin Name: BuddyPress Lockdown

Plugin URI: https://buddypress.org/

Description: Lock down your BuddyPress site if a user is not logged in.

Author: Andy Peatling & Andrew_S1

Version: 1.2

Author URI: https://buddypress.org/

Site Wide Only: true

*/



function bp_lockdown() {

global $bp;



if ( BP_REGISTER_SLUG != $bp->current_component &&

BP_LOGIN_SLUG != $bp->current_component &&

BP_LOGIN1_SLUG != $bp->current_component &&

!is_user_logged_in() ) {

bp_core_redirect( site_url( BP_LOGIN_SLUG ) );

}

}

function wp_lockdown() {

if ( !is_user_logged_in() ) {

auth_redirect( 'wp-login.php' );

}

}



add_action( 'bp_init', 'bp_lockdown');

// if no buddypress, have a backup plan

add_action( 'send_headers', 'wp_lockdown');

?>

There’s a trac ticket with a patch for bp-core.php, and a reworked version of Andy Peatling’s plugin, just here: https://trac.buddypress.org/ticket/2074

Grrr, my posts to this thread aren’t appearing here. Please check my activity stream to see what I wrote earlier!

What does the link in the activation email look like? What’s the “.php” bit of the URL, specifically? (is this in WPMU?)

I just wanted to add my own low-tech solution to a similar situation. This is what I did to hide all my BuddyPress features (members, activity, etc) while keeping my pages and blog posts publicly accessible…

In my child theme, I copied the members/index.php, activity/index.php(etc etc) folders and files. Then in the index files, I surrounded everything inside the “padder” div (which displays all the content) with a is_user_logged_in tag like this:

<div class=”padder”>

<?php if (is_user_logged_in()){ ?>

(content guts go here)

<?php } else { echo “<h3>Members Only!</h3><p>Sorry. The page you have requested is for registered members only. Please visit our About page for more information on member registration. Thank you for visiting.</p>”;} ?>

</div>

PHP isn’t really my thing, so that’s probably not the best way of doing it, but it worked.

@aishing – Check out the following code:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/?topic_page=2&num=15#post-44616

Add it to your theme’s functions.php file.

@aishing – Try putting the code after the register_sidebars code in your theme’s functions.php. Then see if you get an error. Can you please paste the error if you get one?

Btw, you should be creating a child theme to add custom code snippets, otherwise when you upgrade BP, you’ll lose your changes.