BuddyPress.org

This may be considered as bug in current behavior. Currently, BuddyPress only looks for published pages when looking for component associated pages in bp_core_get_directory_pages().

You may want to report it on the BuddyPress trac and the core developers and weigh their opinions on this.

Hello Brajesh Singh and Engine44

I am a newcomer to buddypress and I think I had similar problems as Engine44.
Frankly I could imagine that there are more people who have this
problem but eventually don’t even realize it as a problem.
In particular I can’t imagine that all that bp networks which
are used by schools want to have kids discuss in public. So it might
be a severe problem. But as said I am a newcomer so I might easily be
wrong.

The following concerns mostly the member and activity pages (I hope they are called
this way, this is a direct translation from german), which are either set
public -or if set private can’t be found anymore (which seems to kill more or less all major bp functions, like you can’t see profile etc.) I haven’t looked into groups yet.

I asked a person for help who is pretty proficient in solving general programming
problems but who is not a programmer and in particular not a PHP programmer. So eat with
utmost caution.

He came up with the following hack:
The activity and member pages need to be public in order to assign them
on the bp page. (I think this is the default upon installation)
Then set the pages to private.

go to buddypress/bp-core/bp-core-functions.php
and then in function bp_core_get_directory_pages() {…

change

$page_names = $wpdb->get_results( „SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) AND post_statues = ‘publish’ ” );

into

// temporary hack
if ( is_user_logged_in() ) {
$page_names = $wpdb->get_results( “SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) ” );
} else {
$page_names = $wpdb->get_results( “SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) AND post_statues = ‘publish’ ” );
}
// was:
// $page_names = $wpdb->get_results( “SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) AND post_statues = ‘publish’ ” );
// /temporary hack

@fscbmwcca

thanks for the comment. If I understand correctly then the option:
allows an admin to select which Post types and BuddyPress Components are private
seems to indicate that things like the activity component or the member community component
could be set private.
Did you test the plugin?

The sentence:
provides a Private checkbox in the upper right corner of every page, post, and custom post type selected in Settings

is a bit irritating, finally that feature exists already in a standard BP wordpress version.
That is at least in my BP wordpress version you can already mark
pages as private (i.e. non accessible to non-logged-in members),
i.e. there is already a checkbox. And if there wouldn’t be the bug then
setting the member page and activity to private would have set “the component” to
private, if I understood correctly.
Is the plugin checkbox another checkbox?

There is a plugin which, by its description, seems to set everything private:
https://wordpress.org/plugins/buddypress-members-only/
and which lets you specify which subadresses should be open.
But in my case this is not so helpful because
I want the blog to be public and the blog is not behind a /blog/ adress
but behind the year /2015/… etc.
so I would need to set each year adress open, which seems OK but not really
straightforward.

With the WordPress 4.4/BuddyPress 2.4.3/bbPress 2.5.8, if you set any of the BuddyPress pages set to private you get the following error “The following active BuddyPress Components do not have associated WordPress Pages: Activity Streams. Repair”

I tried the https://wordpress.org/plugins/buddypress-members-only/ and that didn’t seem to do what I wanted. I want people to be able to register as Subscribers but Subscribers should not see any of the BuddyPress/bbPress stuff, only the Contributors and above should be part of the BuddyPress/bbPress community. So I need to be able to exclude Subscribers from BuddyPress/bbPress. I have looked and there is some code out there that seems pretty old so I don’t know if it would work and I am not so great with php so I am a little hesitant. I am also new to BuddyPress so I’m not sure of all the ins and outs.

I tested the plugin and it’s working, in the settings there are two areas [edited – please do not copy & paste such data ]
I hope I am being clear.

With the WordPress 4.4/BuddyPress 2.4.3/bbPress 2.5.8, if you set any of the BuddyPress pages set to private you get the following error “The following active BuddyPress Components do not have associated WordPress Pages: Activity Streams. Repair”

True – If you set Visibility to Private!
Not true if you set the ‘Public or Private’ checkbox provided by the BP Simple Private.

I want people to be able to register as Subscribers but Subscribers should not see any of the BuddyPress/bbPress stuff, only the Contributors and above should be part of the BuddyPress/bbPress community.

So you want to limit access to BP content based on a user’s role.
That is a different issue from the original poster’s issue.
You should create a new topic.
The BP Simple Private plugin discussed above is not applicable to your issue.

correction:
if it’s not secluding the whole subadress,
I wanted to write
if it’s not secluding/opening the whole subadress

I know the plugin doesn’t address my issue but keeps BuddyPress for members only and hide it from non-logged in users. Privacy is very important to our members. I will upload the members that are truly members from a csv file from a list that is provided for me and give the Contributor Role. What I meant by subscriber is the “Subscriber” Role (vs Contributor, Author, Editor, Administrator).
I’m sorry I haven’t expressed myself well and now off topic. I was just trying to provide a solution for making pages private.

I wrote:

….somehow I had the impression that private had also worked for authors before the update….but thats another thing”

and

In my application sofar all members are editors (and currently planned to be editors),

The last sentence is wrong, I actually intended sofar all members to be authors (Autor in german) not editors (Redakteur in german).

I wrote the first sentence because before Shane’s comment I am pretty sure that I had tested wether the private pages are visible for authors and not only for editors or admins and thus I am pretty sure that they were so before. It is just that after Shane’s comment I wanted to check back. Unfortunately before I could check back there was an
automatic wordpress update, which now unfortunately screwed up the intended application.