BuddyPress.org

When you send a private message you see their name in a button beside the textarea. When you send a public message you get a textarea pre-populated with @username. I think if you instead got a textarea with their name in a button beside the textarea… just like a private message… that would be more consistent. It would also be less prone to user error. For instance, I can envision someone wanting to public message “Jim Smith” clicking the button and seeing “@unibomber” in the textarea and thinking… what the?! And then deleting the offending weird text. It sounds ridiculous… but sit down with some non-computer savvy users and you will be amazed :o)

That said… it sounds like you’re aware of that and will be putting some thought into it in future releases. So that’s great.

I guess the question is… if we your don’t rely on the @ shorthand… how would someone make mention of someone else without using the “Public Message” button? Could there be some kind of auto-complete text box for targeting your comments? Or would the @ shorthand simply remain as-is and be considered a “power user” feature.

Just thinking out loud :o)

Upgrade to the latest trunk version of BP 1.2.

“Send Public Message” and “Send Private Message” was added in about a week ago.

@balbert if you look at 1.2 (on testbp.org) you will notice there are 2 types of Send Message. Public and private. the private is as you say. The public is merely a status update.

@ray – i really appreciate this. it’s all clear to me now. I can now manually hide the group forum in bbpress (irregardless of public or private or hidden group). Its quite basic but works fine i.e. group members must go their group site to have access to the group forum.. which is cool btw.

In step #2 above:

How do we make sure that all new group forums are automatically added into the forum category? At the moment, its added as another forum, so we have to manually change this as child to the bbpress forum category for group created in Step #2.

Thanks again for your meticulous help & instructions abv.

@ray, i tested this again: enabled buddypress forum in the component setup, then reinstalled forum using existing bbpress installation setting ***.

I created a private group with forum enabled and posted a topic in this group forum. I then logout, used other browser to view the wpmu forum (bbpress), and I can still see the topic posted in the bppress that should have been a private post. When logged in as another user (non-group member), i can reply to that topic! That’s the privacy issue that I was talking abt.

*** would selecting new installation of bbpress overwrite my existing bbpress ?

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.