BuddyPress.org

I think what we all really want to know is…

Will this plugin keep my thoughts private and protect them from the aliens?

If the group forum is an “open forum” meaning it is not hidden or private, then you will automatically join the group when you post a reply or create a topic in it.

Try toggling public/private on that blog setting on and off. Something else is to make a test post on that blog (and see if that refreshes the BuddyPress display or not).

Ha, faster :o) Jap, the plugin works to 50%, but the changes in bp core will this version not support. We will wait for your plugin, before i will not go online with the (beta :p) page.

@madloki

The solution you linked to does not work with BP 1.1 because it relies on a core function that is now deprecated. It also relies on hacking a core file, which is never a good idea.

My Privacy Component will be out soon.

Me too! An privacy option is very important. This http://devbox.computec.de/2009/06/buddypress-xprofile-privacy-plugin/ does not work with 1.1

Edit: it does work! But user must select before. But privacy fields like birthday etc. should never be visible for guest. Maybe with an click to activate, but at the moment thats not good.

Thanks Reboot Now – and wordpressfan for suggesting it in the first place. Will definitely look into giving this code a try prior to future BP work as this is very important for privacy, especially for children, who will potentially be a significant part of a site I am working on. Membership will be verified to ensure protection of the children’s private information while allowing them to participate fully in the community.

Maybe someone could take this and turn it into a plugin…?

@Jeff Sayre – your plugin is also useful as it gives a universal (i.e. WP not just BP) and individual-focussed privacy option, which is also very important. good work!

This is a little risky for a non-programmer, but here is some code that would replace the profile-loop.php file in the skeleton member theme. Note that this theme is deprecated in the new parent-child theme setup. It is also not a sophisticated privacy component like the one Jeff is working on. It simply omits everything except the base profile fieldset when a non-member views the profile.

This is from my own installation, but I have removed some pieces (mostly formatting) to simplify things a bit. I haven’t tested it in the simplified form.

It assumes that “Base” is the base profile group name you specified in the BP dashboard settings.

<?php

/*

* /profile/profile-loop.php

* This file loops through the profile field groups, and then each profile field to

* display the profile information that a user has entered.

*

* Loaded by: 'profile/index.php' (via the xprofile_get_profile() template tag)

*/

?>

<?php if ( bp_has_profile() ) : ?>



<?php while ( bp_profile_groups() ) : bp_the_profile_group(); ?>



<?php if ( (bp_get_the_profile_group_name() == "Base") || ( is_user_logged_in() ) ) : ?>

<div class="info-group">



<?php if ( bp_group_has_fields() ) : ?>



<h4><?php bp_the_profile_group_name() ?></h4>



<table class="profile-fields">

<?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>



<?php if ( bp_field_has_data() ) : ?>



<tr<?php bp_field_css_class() ?>>

<td class="label">

<?php bp_the_profile_field_name() ?>

</td>

<td class="data">

<?php bp_the_profile_field_value() ?>

</td>

</tr>



<?php endif; ?>



<?php endwhile; ?>

</table>



<?php else : ?>



<h4><?php bp_the_profile_group_name() ?></h4>



No info yet.



<?php endif; ?>



</div>



<?php endif; ?>



<?php endwhile; ?>



<?php if ( !is_user_logged_in() ) : ?>

<p class="not-a-member">You need to log in to see full member profiles.</p>

<?php endif; ?>



<?php else: ?>



<div id="message" class="info">

<p><?php _e( 'Sorry, this person does not have a public profile.', 'buddypress' ) ?></p>

</div>



<?php endif;?>

To be clear, the core privacy component will offer users the ability to decide which pieces of their core-created data they want to make available to which users (or groups of users). It will not offer a mechanism to hide data from people who are not “subscribers” as subscriber is not a BuddyPress user classification or level.

For more details, I’ve created a new thread about my plugin.

No, this sort of privacy change isn’t going to get into BP 1.1.

One way is to use the “is_user_logged_in()” function in the profile loop (normally, “profile-loop.php” in the member theme).

You need to use that in conjunction with (bp_get_the_profile_group_name() == “BASIC”), where BASIC is the base profile group name you specified in the BP dashboard settings, to test whether you’re on the BASIC profile.

I am interested in this as well:

– the BASIC profile-information about the user should be publicly visible.

– the DETAILED profile-information about the user should only be visible for registered users.

any chance to get this implemented into the official release of BP 1.1 (prior to Jeff Sayre´s Privacy-Plugin) ?

Many thanks,

About private/hidden forums, will topics made in these forums show up on the main BP forums page for group members who are a part of those forums?

As it stands, no. This may change if I can work out a way that doesn’t require a slow query.

Also about bbPress plugins, would it be possible to somehow take advantage of bbPress’ existing plugins and use them in the BP forums environment?

Possibly if you place them in mu-plugins, but you don’t have the bbPress backend.

Or would we need to port some of these plugins over by adding the appropriate filters/actions that BP forums uses?

I would try and port some if you’re up for a challenge.

No, because private groups are private. This would make a good enhancemet ticket for a future version of BP

Good questions, DJPaul. These are things I’m wondering about myself!

About private/hidden forums, will topics made in these forums show up on the main BP forums page for group members who are a part of those forums?

Also about bbPress plugins, would it be possible to somehow take advantage of bbPress’ existing plugins and use them in the BP forums environment?

Or would we need to port some of these plugins over by adding the appropriate filters/actions that BP forums uses?

If you are not providing users direct access to your bbPress forums, then you can delete your bbPress files, if you are then leave them alone. You do not need the buddypress-enable.php file anymore.

I can’t speak for plugins, but if the forums in question are attached to private groups then they will not show up. They will remain hidden in the new directory when accessed through BuddyPress.

If you are not running a highly customized bbPress install, definitely consider using the new forums directory instead of a separate bbPress setup. The integration is seamless and requires no messing with cookies, integration settings/plugins.

First of all, with the version of BuddyPress trunk that you have installed, you will now only have one activity table in your MySQL database. This table is wp_bp_activity_user_activity_cached.

I know that based on the private message you sent me, you have read this thread which details why this is the case. So, unless you added those tables back to the DB, I am surprised that you even have the other two activity tables in your DB. If the BP upgrade was successful, it should have automatically removed those two tables.

Trying to add those tables and their corresponding data back to the DB will do nothing. The BuddyPress codebase no longer references those other activity tables. They are no longer needed.

As for the Site Wide Activity widget, make sure that you log into WPMU’s backend and go to “Appearances > Widgets” and remove the Site Wide Activity widget and then add it back. Also, your widget will not show any activity until someone does something that gets recorded into the wp_bp_activity_user_activity_cached table.