frostdawn

I also attempted to add an exception to the LoginRedirect before the loggedin check is performed. I didn’t get the syntax just right, but it could prove to be an alternative way to get something past the privacy filter. Provide the URL to a page you don’t want protected to the exception rule and if that URL is hit, it should exit out of the if loop in the LoginRedirect function.

Thanks for the post, however trying the above, I got the following error:
Parse error: syntax error, unexpected T_STRING, expecting T_FUNCTION in C:\xampp\htdocs\wordpress\wp-content\plugins\private-buddypress\private-buddypress.php on line 88

I then tried to add the option of a page filter to the exception rules already defined in the source such as:

function LoginRequired() {
// No login required if homepage is excluded
if ( true == $this->options->exclude->homepage && is_front_page() )
return false;

// No login required if terms is excluded
if ( true == $this->options->exclude->terms)
return false;

// No login required if registration is excluded
if ( true == $this->options->exclude->registration && ( bp_is_register_page() || bp_is_activation_page() ) )
return false;

// No login required if blog pages are excluded
if ( true == $this->options->exclude->blogpages && bp_is_blog_page() )
return false;

// No login required if blog pages are excluded
if ( true == $this->options->exclude->page && bp_is_page(‘mypage’) )
return false;

// Login required
return apply_filters(‘pbp_login_required_check’, true);
}

While that block of code didn’t throw any errors, it didn’t exclude the page as expected either.