BuddyPress.org

I used a different approach for our BuddyPress using a BuddyPress filter to exclude all private Blogs activities from showing up:

http://blogs.zmml.uni-bremen.de/olio/2010/01/12/activity-privacy-plugin-for-buddypress/

Ercih, if you set your bp groups to be PRIVATE, the forum in that group is actually using bbpress; and will be visible to users that go directly to bbpress itself — they can read, post new topics, edit, delete their topics — just like a normal bbpress stuffs that really defeats the purpose of having a privacy option for BP Groups, i.e. those that is setup with forum.

I hope I am completely wrong; but this is what I am seeing with my wpmu2.8.6+bp1.1.3+bbpress1.0.2

I am not sure I understand:

are you saying, that if you create a “Private Group” within BP, then the associated “Group-Forum” is not private ?

So when creating a private Group, the Forum-posts are still visible by everybody ?

Fantastic plugin which I came across in error

However I see a problem:

1) I’ve posted my first link and set it to private, so only I can see it… But after posting the link, there’s no way of deleting it via the admin panel as it doesnt appear.

Yes you can delete it from the front end, but thought Id report this anyway in case you wasn’t aware.

I’m using BP 1.1.3 and WP 2.8.6

Other than the above- Fantastic plugin. Probably the best 3rd party one ive come across yet

**EDIT** I see the problem now- If you made the link public, it will then display in the admin panel. However don’t you think admins should be able to see ALL links, private or not?

I found a fix here: https://buddypress.org/forums/topic/more-privacy-options-private-blogs-and-activity-streams. Worked for me.

TLDR version: Introduce types of groups. e.g. “User group” type – it has no forum, no “Home” page, just members listing and activity stream. This group added to Activity Stream filters where relevant.

Would have to filter out custom group type “User group” out of the /groups/directory page & member profile group page.

These custom group types could be set so they are publicly visible/private to those members involved/or hidden (visible to the creator only). As per current Group privacy settings.

Could add e.g. “Friends”, “Colleagues” and “Fans” as default, empty groups for each user on user registration. Obviously revise theme to make the “Friends” page (“Connections”, maybe) look like the Friends page rather than a regular Group.

Different users might create “User group” types with the same name but with different meaning (“Fans” could be interpreted several ways for example). This is no problem as such categorisation is defined — and belongs to — the user who does it. Might need some semantic group kind/type identifier in the code to allow FOAF/SIOC RDF profiles to be able to assigned to these “User groups”.

When composing a private message, is the javascript being loaded? Look in the page source and copy-and-paste the javascript URL in your browser and see if it loads up a text file.

@ Jivany

You’ve covered this on trac: https://trac.buddypress.org/ticket/1536

So this is a question of privacy settings for the blog.

I hope this isn’t considered hijacking, but do you, DJPaul or anyone know how to make _old_ posts that were counted as private (as per above) appear in the stream?

I can make new posts appear in the stream now but all the old blog posts (https://wordpress.org/extend/themes/p2) are still hidden. Some value in the db?

Hooray!

Maybe, Erich73 – the only thing is that this problem is caused by incompatibility with another plugin. I’m not sure what the policy is on accommodating other plugins. Maybe More Privacy Options is enough of a no-brainer for BP communities that it’d be OK?

I guess this is worth a TRAC-ticket ?

Hi Afoka –

Your post reminded me that I had to change this hack a bit in BP 1.1.3. Here are the notes I made for myself at the time. Let me know if they make sense, and if you can make them work:

===

In wp-content/plugins/buddypress/bp-blogs.php:

– function bp_blogs_record_post has two cases, one for new posts and one for edited posts. Change

if ( (int)get_blog_option( $blog_id, 'blog_public' ) ) {

to

$is_blog_public = get_blog_option( $blog_id, 'blog_public' ); //added



//if ( (int)get_blog_option( $blog_id, ‘blog_public’ ) ) {



if ( $is_blog_public > 0 ) { // changed to account for More Privacy Options

in both of the cases.

– functions bp_blogs_record_comment and bp_blogs_approve_comment. Replace

if ( (int)get_blog_option( $recorded_comment->blog_id, 'blog_public' ) ) {

with

$is_blog_public = get_blog_option( $recorded_comment->blog_id, 'blog_public' ); //added



//if ( (int)get_blog_option( $recorded_comment→blog_id, ‘blog_public’ ) ) {



if ( $is_blog_public > 0 ) { // changed to account for More Privacy Options

Did you try making the change to bp-blogs-classes.php described in the link I gave you? It will only take affect with new blog posts – you’ll have to delete the old unwanted activity items manually.

Try making the change to bp-blogs-classes.php, and then post a new entry to a private blog to see if the change has worked.

I’m not sure how those plugins in particular work, but here’s a solution that worked for me with the plugin More Privacy Options: https://buddypress.org/forums/topic/more-privacy-options-private-blogs-and-activity-streams

The same principle can probably be applied to your case. Figure out how your plugins are recording fine-grained privacy options, and then adjust the code at the above link to match.

With BuddyPress being used now by/for different interest groups from colleges to niche organizations to purely social networking, etc. there is no doubt that there would be different opinions regarding importance of the friends component vis-a-vis groups component.

I’m surprised in the first place that the friends component could even be considered for deprecation since that’s a popular feature. How about a switch to enable or disable the friends component? In one install, e.g. for a professional organization, they don’t need “friends” and prefer “groups.” In another install, for a social club, they’d like “friends” and “groups.”

It would be great if we see categorization of friends (as Bowe mentioned above) as it makes a lot of sense and extend it so that you could send a message only to Friends-Family or send a message only to Friends-CollegeBuds.

However, should the friends component be deprecated, I would request devs to expand Groups component with a user function to have the ability to privately categorize the people within a Group he/she belongs. e.g. Group-Hiking-Friends, Group-Hiking-Pros, Group-Hiking-CollegeBuds, Group-Hiking-NeedsMoreTraining.

hola, sorry guys – wish i’d get an email notification every time someone had a bug with this theme. anywho, i’ve moved all the project files to google code at http://code.google.com/p/avenuek9-bp-theme/ where I have several FAQs and patch files available.

*please note* that bp 1.2 will improve things dramatically by adding a boatload of new features, which includes theming. if you go to testbp.org you’ll see how the default theme has changed. consequently, the avenuek9 theme will change accordingly near BP 1.2 release.

if you are not running bp 1.1.x on a development server (with the avenuek9 theme), please hold out on theming your installation, as it may become a royal pain in the arse once you upgrade. also, if you need any additional help, i usually respond better to private messages (because they fire off a notification to my personal email account saying that i need to bug squash )

I can see how it might be good tokeep friending, but give the option not to use it. I hate it when Ning takes away features …

Just in general I don’t like the idea of any features being taken away …

If friending gets taken out in 1.3, then I’ll stay with Buddypress 1.2 …

We should be thinking about extending the BuddyPress framework and not deprecating major components at this time …

Not sure why JJJ wants to remove the “friending feature” in favour of the “following-feature”? Can we not have both ? …

I am worried Buddypress will fall into the trap of trying to be everything to all people and will become a bloated mess. For my projects I need a coherent, reliable core before I need any more features – forums, events, galleries, enterprise features, ecommerce, …

It’s great the developers are rethinking friending, how it can make more sense in the Buddypress context. If Buddypress can come up with a different approach, logically tied into groups and (micro)blogging, that could really set BP apart from Facebook, Ning, etc. Less is more!

JJJ’s proposal already is the best of both world imho (yes, we can have both!):

1. Deprecate “Friends” component code into a separate downloadable plugin that can still be used exactly like it is now, just not part of the core anymore.

2. Merge friends functionality into private “user” groups so that developers can choose to ditch the “friends” model if they want …

3. “Friends” would replaced with the core ability to “follow” peoples activity, and for your activity to be followed by others …

This is also a next step in the evolution in web friending, from classic Friendster/Facebook -> Twitter following -> following/friending with more context in groups and blogging (not just based on 140 chars brain farts).

Absolutely agree with Windhamdavid btw!