BuddyPress.org

In bp-blogs.php, change 379 from
if ( (int)get_blog_option( $blog_id, 'blog_public' ) || !bp_core_is_multisite() ) {
to
if ( (get_blog_option( $blog_id, 'blog_public' ) > 0 || !bp_core_is_multisite() ) {

Also, change 427 from
if ( (int)get_blog_option( $recorded_comment->blog_id, 'blog_public' ) || !bp_core_is_multisite() ) {
to
if ( (get_blog_option( $recorded_comment->blog_id, 'blog_public' ) > 0 || !bp_core_is_multisite() ) {

I haven’t tested this but it should work.

You’ll have to wait for Google to check your site again.

You can expedite this process by signing up for Google’s Webmaster Tools and requesting your site to be delisted.

Also make sure your WP site is blocked from search engines:
https://codex.wordpress.org/Settings_Privacy_SubPanel

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/

Good stuff! Thanks a lot, that works perfectly

@mistercyril – Add bp_is_directory() to the bp_is_register_page() line.

@Travel-Junkie: Hey, your solution works great on my setup (WP MU 2.9.2 & BP 1.2.3).

I was wondering if you could help me take this one step further…

I would like my buddypress pages to be accessible only to logged-in users as they are now… but in order to get people to want to log in I think a “teaser” would be a plus. So my question is : How can we make the main BP directory pages accessible to everyone and restrict single groups, profiles, forums… ?

Thanks again for the great help so far!

Might be sad if I don’t remember what my own plugin does but I have something called Group Forum Extras – which contains some functions to pull out an index of forums. But I believe I coded the sql statement only to pull out the private forums if the user is logged in and a member of. Though this would point you in the right direction if you wanted to modify the code. (just remove that conditional) look for (bp_forum_extras_index_get_forums in the file bp-forums-extras-index.php )

You are always welcome to create your own default theme if you’re not pleased with the packaged one that comes with BuddyPress.
You’ll just have to spend more time creating your own theme!

To me it’s more troublesome for the designers and developers to get rid of js function in a child theme that inherits everything from the default.

As a designer / developer surely you know what can happen with progressive enhancement. P2 is a fine example of what a developer knows. I mean the new 2010 WP theme doesn’t come with js does it?

I like to grab it, dig in, or build from scratch. Now with the default theme inheriting a whole lot more it sometimes is a pain.

Why am i complaining this is one heck of a free meal. :p

The default theme needs to showcase everything that BuddyPress can do. Like you point out, it’s down to individual sites to decide what BuddyPress features to use, which relates to what javascript will be required.

a little unrelated but does anyone here ever wonder why the default theme has so much js?. i understand it’s pro and progressive but really don’t think this sort of function is needed at the base theme. It’s kinda confusing because your not sure what’s core and what’s not sometimes.

I believe it’s up to the community to serve whatever js they like.

Your second, third and fourth requests can be taken care of by making sure the groups are set as Private. That means that they don’t show up in public listings, and their contents are only visible to members of the group.

In order to make sure that people can only be part of a single group, you’ll want to hide the Send Invite screen for all users, or at least for non-admins. You could either do this through CSS, or by modifying/reproducing the functionality defined at bp-groups.php groups_setup_nav().

As for the first question, there are WP plugins that allow you to restrict membership to invited members. A ten-second Google search turned up this: https://wordpress.org/extend/plugins/wp-invites/, for example. I imagine that this would work fine for BP as well. The most straightforward way to populate groups would then be for the admin to use a plugin like BP Group Management http://teleogistic.net/code/buddypress/bp-group-management/, which allows admins to place people manually in groups, bypassing the invitation process.

It’s a known bug which has been fixed in the upcoming 1.2.4 release.

Thanks for the tip Shaista,

I followed your instructions and it worked for me. My blog is in a sub-folder. Now avatar upload and crop works ok.

Seems a pain that we have to change the core BP code though!

Samudradaka

So in my case I find the problem of why “upload avatar” doesn’t work.
It’s because of the BuddyPress Template pack plugin. When I use the bp default theme everything works perfectly.
When I use any wordpress theme that I made compatible with BuddyPress using the plugin bp Template pack I find exactly the same problem: Avatar Upload, private message, register… all of that doesn’t work… as soon as you click on the button “Submit” or “Crop” you go back to the same page and nothing happen?! It’s like the information wasn’t given at all…
There is a conflict somewhere that I can’t find!
Any Ideas???

[EDIT] Ok I solved the problem!!!
Ok so if none of the solution you have in this topic works for you it’s probably because you have a conflict between a js script in your default theme and a js script in your wordpress theme… take a minute tu disable all the js action in your wordpress theme ton test if it’s coming from there…