BuddyPress.org

The first version of BuddyPress is for open networks, there won’t be any real privacy settings.

Once we have a 1.0 release, then the plan is to work on a generic privacy component that will introduce privacy levels across an install.

I did a simple check of $current_user to restrict access to the profiles while waiting for privacy options to be included in BP.

Did you put it on the index.php of every single page Ron? What syntax did you use? I was thinking about just putting the if_logged_in argument, but is $current_user better to use?

Trent

Thanks Ron. I will try that out and see what goes on. Did you put ending tags in footer.php then?

Trent

I’ve not tested it extensively yet, but this plugin:

http://wpmudev.org/project/More-Privacy-Options

seems to allow the blocking of all users, except the registered community, from viewing anything related to buddypress.

If I set “I would like my blog to be visible only to registered users from blog community” for the main/first blog where all the buddypress features sit, then you have to login before being able to see anything except for blogs, which have their own privacy options.

Is it really this simple to create a private social networking community but allow the blog privacy to remain under the control of the blog owner? I hope so. Perhaps someone can test and verify this?

Thanks.

@trent

Could you please point me to that thread (the plugin working out of /plugin/)?

That’s very reassuring that you’re using dsaders privacy plugin, too. Nice to see such a simple solution already exists to provide private BuddyPress communities while not affecting the privacy of individual’s blogs. In education, I can see this being very attractive. Hopefully Andy is aware of this for future core feature development.

I’ve just posted this to the WPMU forums, but it’s just as relevant here: Regarding dsader’s more privacy options plugin…

“I’m testing this plugin on a WPMU 2.7 and BuddyPress (both from SVN) installation. It can turn BuddyPress into a private social network quite simply by making the main/first blog private. However, there’s one issue I can see:

the ../activity/feed RSS feed is private when the ‘main’ blog is private.

But, member’s activity feeds i.e. ../members/josswinn/activity/feed remains public.

Any way to fix this? I appreciate that the plugin wasn’t written to support BuddyPress, but it’s so close to working well on BuddyPress that it would be good to look at this and provide a way to create truely close BuddyPress networks.

Thanks!”

I’ve since found that this is happening to me on a site installed in a sub-dir but not on an install using wildcard DNS/sub-domain. Can anyone verify this?

Ok…figured it out for dsader’s plugin. Just needs priority added to it. Check out this post in WPMU forums, but basically add priority to the template_redirects like:

add_action('template_redirect', 'ds_users_authenticator', 1);

add_action('template_redirect', 'ds_members_authenticator', 1);

add_action('template_redirect', 'ds_admins_authenticator', 1);

Just adding the “1” for priority makes it go before Andy’s changes. All those lines are near the top of the plugin.

Trent

Hiya, here’s what I’m trying. I’d like to password protect my entire BuddyPress install with one username and password (I’ll change it from time to time).

Here’s BuddyPress’s htaccess file

---

RewriteEngine On

RewriteBase /community/

#uploaded files

RewriteRule ^(.*/)?files/$ index.php [L]

RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*

RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]

# add a trailing slash to /wp-admin

RewriteCond %{REQUEST_URI} ^.*/wp-admin$

RewriteRule ^(.+)$ $1/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule . – [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]

RewriteRule . index.php [L]

<IfModule mod_security.c>

<Files async-upload.php>

SecFilterEngine Off

SecFilterScanPOST Off

</Files>

</IfModule>

---

To which I tried to add:

AuthType Basic

AuthUserFile /home/username/sitename.org/subdirectory/.htpasswd

AuthName “Community Name”

require valid-user

---

and I made a .htpasswd file too.

---

Possibly because I installed into a subdirectory of an exising WP install, it winds up going to sitename.org and nothing is protected.

I will try the whole thing in subdomain.domain.org to see if I can get the htaccess stuff to work.

So, can anyone point out how I can just password protect the whole BuddyPress site with one username and password?