BuddyPress.org

Add to your theme’s style.css
div#item-header span.activity { display: none; }
This will also hide same in Group’s pages

Edit – ok @hnla that was fast

You could probably hook into the get_header action, do your conditional check and if the person is a mentor, then show the page, otherwise show the registration page or whatever.

Modify the function listed in this thread:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/?topic_page=2&num=15#post-44616

Hopefully it gives you a few pointers.

Not sure what to tel you about the theme issues you’re having (I just modified the BP default one), but I get what you mean about the BP groups/forums confusion.

The audience I’m after is used to vbulletin forums, so I actually found some code posted here on BP.org that made groups open onto the group forum by default, and then I put a conditional around the activity stream posting thing on the group activity pages that only allows admins to see/use that. This way, all group activity id funneled into the forums, unless the group admin just feels the need to post something to the activity stream. I also just did away with the ability to post activity stream updates from the sitewide stream page, but you could just modify the ‘post update to’ dropdown menu there to hide and make it post to the user’s profile only.

All in all, I’ve found that Buddypress can be a bit of work if you want to change the way it does certain things, but for most people the features are worth the trade-off of some extra work. I hope you get it all figured out and working the way you’d like

@themeanwhile – you can enable or disable the various components so if you want Activities only, enable that and disable other components. After you activate BuddyPress, go to the new BuddyPress menu item on the left column of dashboard, and go to

a) General Settings – these are your choices
Base profile group name:
Full Name field name:
Disable BuddyPress to WordPress profile syncing?: Yes No
Hide admin bar for logged out users?: Yes No
Disable avatar uploads? (Gravatars will still work): Yes No
Disable user account deletion?: Yes No
Disable global forum directory?: Yes No
Disable activity stream commenting on blog and forum posts?: Yes No
Default User Avatar – For users without a custom avatar of their own, you can either display a generic logo or a generated one based on their email address

b) Component Setup
Activity Streams – Allow users to post activity updates and track all activity across the entire site.
Enabled Disabled
Blog Tracking – Tracks blogs, blog posts and blogs comments for a user across a WPMU installation.
Enabled Disabled
bbPress Forums – Activates bbPress forum support within BuddyPress groups or any other custom component.
Enabled Disabled
Friends – Allows the creation of friend connections between users.
Enabled Disabled
Groups – Let users create, join and participate in groups.
Enabled Disabled
Private Messaging – Let users send private messages to one another. Site admins can also send site-wide notices.
Enabled Disabled
Extended Profiles – Activates customizable profiles and avatars for site users.
Enabled Disabled

I would suggest you set up a test install so you can check the features for yourself.

“Of course, activity filters, profile page, friends page, settings page, etc, would also need to be migrated to display in the backend.”
Why? If you want to make the BP Activity section private, you can add conditional tags for is_user_logged_in …

this plugin hides every pages ton non-registered users
https://wordpress.org/extend/plugins/registered-users-only-2/

this one can hide specific pages / components
https://buddypress.org/community/groups/s2member/

Terrific plugin! Using BuddyPress Links 0.4.1 (with BuddyPress 1.2.3, WPMU 2.9.2). Some feedback:

Frontend:

– When viewing a link in the Links tab, the A tag of the external link icon needs a target=”_blank”.

– Would be nice to have “Report Broken Link” and “Flag as Inappropriate” buttons for each link (or may be simply “Report” to save space, and it popups to “Report Broken Link” and “Flag as Inappropriate”). Then have that status show up in the Manage Links page as two additional columns. And also have a way of filtering and showing just broken or inappropriate links in the Manage Links report. And also have a way to clear status. Perhaps record user who reported the status (in case that user is falsely reporting and should be banned).

Backend:

– Instead of 3 entries in the BuddyPress dashboard menu (i.e.: BuddyPress Links / Manage Links / Edit Categories), have only one entry “Links”. Then divide the admin page into tabs: Settings, Links, Categories, Support, About.

– The “Search Links” box and the “Search Categories” box (on the Manage Links and Edit Categories pages, respectively) are not in the same vertical location. “Search Links” box is above the heading, “Search Categories” is below the heading.

– Disable the “Delete” buttons if no Links/Categories selected to delete.

– When doing a search (Search Links / Search Categories), add a “Show all Links” / “Show all Categories” button/link to clear the search criteria.

Manage Links page:

– Make all the A tags (Details / Owner / Edit) have target=”_blank”.

– Link the link avatar to the destination URL (with a target=”_blank”).

– If hover over a link avatar, show full size image in floating popup (like a tooltip).

Settings:

– Have a setting to enable/disable rel=”nofollow”.

– Have 3 checkbox settings to hide a link if it: (1) goes below a specified negative rating (e.g.: -10); (2) is flagged inappropriate a specified number of times; (3) reported broken a specified number of times. The link’s owner would still see the link but with a warning.

– Have a setting to specify what avatar to show if none specified. First radio box would be “default avatar”, following by radio boxes to select screen snapshot thumbnail from the various snapshot website services.

Hi MrMaz, I think your plugin is super! I do have one question, we are building a buddypress pay site and we want to hide all of the tabs except for a few pages if the user is logged in. Where can I find the code that creates the “Links” navigation in the top header so that I can hide it if the user is logged in or not? Also, can “Links” navigation item be changed to the word “Videos” instead? It seems like both of these would be easy fixes once I knew where the code is, or is it more complicated than that? Thanks in advance for your help!

Here is my Sidebar which does exactly what you want: Show different sidebars on different BP sections of the site.. It does not work 100% (blog sidebar does not show up yet) but it should get you started. You use BP conditional tags to show/hide the different sidebars depending where the user is on the site:

<?php do_action( 'bp_before_sidebar' ) ?>



<div id="sidebar">



<div class="padder2">

<?php

locate_template( array( 'accordeon.php' ), true );

?>

<?php do_action( 'bp_inside_before_sidebar' ) ?>

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



<?php do_action( 'bp_before_sidebar_me' ) ?>



<?php endif; ?>



<?php /* Show forum tags on the forums directory */

if ( BP_FORUMS_SLUG == bp_current_component() && bp_is_directory() ) : ?>

<div id="forum-directory-tags" class="widget tags">



<h3 class="widgettitle"><?php _e( 'Forum Topic Tags', 'buddypress' ) ?></h3>

<?php if ( function_exists('bp_forums_tag_heat_map') ) : ?>

<div id="tag-text"><?php bp_forums_tag_heat_map(); ?></div>

<?php endif; ?>

</div>

<?php endif; ?>



<div class="padder3">



<?php if(bp_is_group()){

if(!dynamic_sidebar("Group Sidebar")){?>

<?php }

}

else if(bp_is_member()){

if(!dynamic_sidebar("Profile Sidebar")){ //if user profile etc

?>

<?php

}

}

else if(bp_is_blog_page() || bp_is_directory()){

if(!dynamic_sidebar("Blog Sidebar")){?>

<?php } }

else dynamic_sidebar( 'Sidebar' )?>

<?php dynamic_sidebar( 'sidebar' ) ?>

</div>



<?php do_action( 'bp_inside_after_sidebar' ) ?>

<?php /* Show forum tags on the forums directory */

if ( BP_FORUMS_SLUG == bp_current_component() && bp_is_directory() ) : ?>

<div id="forum-directory-tags" class="widget tags">



<h3 class="widgettitle"><?php _e( 'Forum Topic Tags', 'buddypress' ) ?></h3>

<?php if ( function_exists('bp_forums_tag_heat_map') ) : ?>

<div id="tag-text"><?php bp_forums_tag_heat_map(); ?></div>

<?php endif; ?>

</div>

<?php endif; ?>

</div><!-- .padder -->

</div><!-- #sidebar -->



<?php do_action( 'bp_after_sidebar' ) ?>

Make sure to register the sidebars in your functions.php (of your child theme)

if (function_exists('register_sidebar')) {

register_sidebar(

array(

'name' => 'Blog Sidebar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Profile Sidesbar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Group Sidebar ',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Left Footer',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Middle Footer',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Right Footer',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

}

So many posts about this topic!!!

I too want to restrict pages / posts / and ALL buddypress pages to non members …

Thanks peterverkooijen for the temporary solution but there should be a plugin that can do this in a nicer way.

Does anyone know?

I just wanted to add my own low-tech solution to a similar situation. This is what I did to hide all my BuddyPress features (members, activity, etc) while keeping my pages and blog posts publicly accessible…

In my child theme, I copied the members/index.php, activity/index.php(etc etc) folders and files. Then in the index files, I surrounded everything inside the “padder” div (which displays all the content) with a is_user_logged_in tag like this:

<div class=”padder”>

<?php if (is_user_logged_in()){ ?>

(content guts go here)

<?php } else { echo “<h3>Members Only!</h3><p>Sorry. The page you have requested is for registered members only. Please visit our About page for more information on member registration. Thank you for visiting.</p>”;} ?>

</div>

PHP isn’t really my thing, so that’s probably not the best way of doing it, but it worked.

It’s not any one plugin that does the job. Here’s how I do it.

Create a new blog (let’s call it Test) and set the privacy (more privacy options needed here and bp-mpo-activity-filter to keep it’s content out of the stream) to “only blog admins can see this blog” (this is necessary, but keeps things clean since nothing should get added to this blog).

Use new-blog-defaults to set the blog defaults including menus that the users cannot use.

Members is used to set capabilities of the admin (I don’t change the role of the new blog just the admin’s capabilities) so the admin is “like” an editor or author, but I can still let them change their themes (theme changing is very important to young users).

Wpmu-plugin-manager lets you set which plugins to allow users to use and which ones are automatically turned on (I always turn on Ozh’s Admin Menus for example). Turn on any plugins you want to use and tweek their settings and any other blog settings.

Then Adminimize to further hide menus the users don’t need (it only hides menus, but most users will never find them anyway). Adminimize is great for simplifying the write panels for posts and pages too. Any plugins I don’t want users to change settings on I can make sure they don’t have access to by making sure the menus are hidden.

Now use new-blog-options under the site admin menu and give it the blog id of Test and check off any of the database fields you want new blogs to have (make sure the Members and Adminimize ones are checked). Maybe this isn’t exactly what you want, but it is probably the best overall way to simplify blogs for younger users.

Also since I use these with classes, I just import my whole list from a spreadsheet using DD Import Users as subscribers on the main blog. I use limit-blogs-per-user and set the site-admin/options to 2. Now users can create their own blog, but can only create one blog of their own. This saves me a lot of time, but still gives the users a fair amount of freedom with their blogs.

It isn’t a perfect solution. I would like to see some of the overlapping capabilities put into one plugin for cloning blogs. I would especially like to see the ability to have different templates (ie base blogs to clone from) so that I could have one setup for say grade 1 students and another setup for grade 5 students.

Hope this is useful to someone.

Great work! I haven’t had the time for a detailed test, but i have some short feadback for the beginning:

1. Everything works fine and seems logical. Thats great. There could be some front-end twaeks, but i will come back later next week with some more detailed ideas and mockups.

2. From our experience it is great to have advanced edit functions but hide them in a second row from the avarage user (like the wordpress backend editor does). For a wiki article the user (students) should focus on the content instead of any fancy formating. Basic options could be a select-box for h1, h2, h3 (this is important and must be easy accessible, because it will build the toc and people should get used to it) bold, italic, url link, unordered list, and numberd list. Everything else could go in a second or third row which appears if you click some “advanced options” button.

3. (future release) A searchable wiki directory page with all public pages.

4. (future release) “Suggest a wiki page” button so that non admin-members could ask the admin to create a new wiki page for them.

5. (future release) non-admin wiki page creation

@Bowe

setting up different group types is fairly easy. You just have to attach some groupmeta to the group, that basically let you add as many types as you’d like. Then you just check the metadata to figure out what type of group you’re in. Using the groups API you can then add different functionality for different groups.

I’ve written a types-plugin for one of my sites. It doesn’t have an interface, though. The 3 types I needed are hardcoded into it, so it’s really not suited for a release at the moment. There’s also a lot of more stuff, like a shopping cart, part of that plugin. So, I’ve stripped the functions needed for group types out (hopefully al of them).

First we need to add the addtional fields to our registration form:

function sv_add_registration_group_types()

{

?>

<div id="account-type" class="register-section">

<h3 class="transform"><?php _e( 'Choose your account type (required)', 'group-types' ) ?></h3>



<script type="text/javascript" defer="defer">

jQuery(document).ready(function(){

jQuery("#account-type-normal_user").attr("checked", true);

jQuery("#group-details").hide();

jQuery("#account-type-type_one,#account-type-type_two,#account-type-type_three").click(function(){

if (jQuery(this).is(":checked")) {

jQuery("#group-details").slideDown("slow");

} else {

jQuery("#group-details").slideUp("slow");

}

});

jQuery("#account-type-normal_user").click(function(){

if (jQuery(this).is(":checked")) {

jQuery("#group-details").slideUp("slow");

} else {

jQuery("#group-details").slideDown("slow");

}

});

});

</script>



<?php do_action( 'bp_account_type_errors' ) ?>

<label><input type="radio" name="account_type" id="account-type-normal_user" value="normal_user" checked="checked" /><?php _e( 'User', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_one" value="type_one" /><?php _e( 'Type 1', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_two" value="type_two" /><?php _e( 'Type 2', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_three" value="type_three" /><?php _e( 'Type 3', 'group-types' ) ?></label>



<div id="group-details">

<p><?php _e( 'We will automatically create a group for your business or organization. This group will be tailored to your needs! You can change the description and the news later in the admin section of your group.', 'group-types' ); ?></p>



<?php do_action( 'bp_group_name_errors' ) ?>

<label for="group_name"><?php _e( 'Group Name', 'scuba' ) ?> <?php _e( '(required)', 'buddypress' ) ?></label>

<input type="text" name="group_name" id="group_name" value="" />

<br /><small><?php _e( 'We suggest you use the name of your business or organization', 'group-types' ) ?></small>



<label for="group_desc"><?php _e( 'Group Description', 'scuba' ) ?></label>

<textarea rows="5" cols="40" name="group_desc" id="group_desc"></textarea>

<br /><small><?php _e( 'This description will be visible on your group profile, so it could be used to present your mission statement for example.', 'group-types' ) ?></small>



<label for="group_news"><?php _e( 'Group News', 'scuba' ) ?></label>

<textarea rows="5" cols="40" name="group_news" id="group_news"></textarea>

<br /><small><?php _e( 'Enter any news that you want potential members to see.', 'group-types' ) ?></small>

</div>

</div>

<?php

}

add_action( 'bp_before_registration_submit_buttons', 'sv_add_registration_group_types' );

Then we have to validate things and add some usermeta when a regitration happens:

/**

* Add custom userdata from register.php

* @since 1.0

*/

function sv_add_to_signup( $usermeta )

{

$usermeta['account_type'] = $_POST['account_type'];



if( isset( $_POST['group_name'] ) )

$usermeta['group_name'] = $_POST['group_name'];



if( isset( $_POST['group_desc'] ) )

$usermeta['group_desc'] = $_POST['group_desc'];



if( isset( $_POST['group_news'] ) )

$usermeta['group_news'] = $_POST['group_news'];



return $usermeta;

}

add_filter( 'bp_signup_usermeta', 'sv_add_to_signup' );



/**

* Update usermeta with custom registration data

* @since 1.0

*/

function sv_user_activate_fields( $user )

{

update_usermeta( $user['user_id'], 'account_type', $user['meta']['account_type'] );



if( isset( $user['meta']['group_name'] ) )

update_usermeta( $user['user_id'], 'group_name', $user['meta']['group_name'] );



if( isset( $user['meta']['group_desc'] ) )

update_usermeta( $user['user_id'], 'group_desc', $user['meta']['group_desc'] );



if( isset( $user['meta']['group_news'] ) )

update_usermeta( $user['user_id'], 'group_news', $user['meta']['group_news'] );



return $user;

}

add_filter( 'bp_core_activate_account', 'sv_user_activate_fields' );



/**

* Perform checks for custom registration data

* @since 1.0

*/

function sv_check_additional_signup()

{

global $bp;



if( empty( $_POST['account_type'] ) )

$bp->signup->errors['account_type'] = __( 'You need to choose your account type', 'group-types' );



if( empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )

$bp->signup->errors['group_name'] = __( 'You need to pick a group name', 'group-types' );



if( ! empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )

{

$slug = sanitize_title_with_dashes( $_POST['group_name'] );

$exist = groups_check_group_exists( $slug );

if( $exist )

$bp->signup->errors['group_name'] = __( 'This name is not available. If you feel this is a mistake, please <a href="/contact">contact us</a>.', 'group-types' );

}

}

add_action( 'bp_signup_validate', 'sv_check_additional_signup' );

And then we set up the group for the user (there are some constants in this function, so you’ll need to change that):

/**

* Create custom groups for skools, biz and org accounts

* @since 1.0

*/

function sv_init_special_groups( $user )

{

global $bp;



// get account type

$type = get_usermeta( $user['user_id'], 'account_type' );



if( $type == 'normal_user' )

{

// Do nothing

}

elseif( $type == 'type_one' || $type == 'type_two' || $type == 'type_three' )

{

// get some more data from sign up

$group_name = get_usermeta( $user['user_id'], 'group_name' );

$group_desc = get_usermeta( $user['user_id'], 'group_desc' );

$group_news = get_usermeta( $user['user_id'], 'group_news' );



$slug = sanitize_title_with_dashes( $group_name );



// create dive skool group

$group_id = groups_create_group( array(

'creator_id'	=> $user['user_id'],

'name'			=> $group_name,

'slug'			=> $slug,

'description'	=> $group_desc,

'news'			=> $group_news,

'status'		=> 'public',

'enable_wire'	=> true,

'enable_forum'	=> true,

'date_created'	=> gmdate('Y-m-d H:i:s')

)

);

// add the type to our group

groups_update_groupmeta( $group_id, 'group_type', $type );



// delete now useless data

delete_usermeta( $user['user_id'], 'group_name' );

delete_usermeta( $user['user_id'], 'group_desc' );

delete_usermeta( $user['user_id'], 'group_news' );



// include PHPMailer

require_once( SV_MAILER . 'class.phpmailer.php' );



$mail = new PHPMailer();

$mail->IsSMTP();

$mail->Host = SV_SMTP;



$auth = get_userdata( $user['user_id'] );

$profile_link = $bp->root_domain . '/' . $bp->groups->slug . '/' . $slug . '/admin';



$message = sprintf( __( 'Hello %s,



we have created a group for your business or organization. To get more out of your presence on Yoursitenamehere please take some time to set it up properly.



Please follow this link to fill in the rest of your profile: %s



We wish you all the best. Should you have any questions regarding your new group, please contact us at support@yoursitenamehere.com.



Your Yoursitenamehere Team', 'group-types' ), $auth->display_name, $profile_link );



$mail->SetFrom("support@yoursitenamehere.com","Yoursitenamehere");

$mail->AddAddress( $auth->user_email );



$mail->Subject  = __( 'Your new group pages on Yoursitenamehere', 'group-types' );

$mail->Body = $message;

$mail->WordWrap = 75;

$mail->Send();

}

}

add_action( 'bp_core_account_activated', 'sv_init_special_groups' );

When you write a group extension we’ll have to swap the activation call with a function like the one below to be able to check for group types.

/**

* Replacement activation function for group extension classes

*/

function activate_type_one()

{

global $bp;

$type = groups_get_groupmeta( $bp->groups->current_group->id, 'group_type' );

if( $type == 'type_one' )

{

$extension = new Group_Type_One;

add_action( "wp", array( &$extension, "_register" ), 2 );

}

}

add_action( 'plugins_loaded', 'activate_type_one' );

The last thing we need to do is add our group type names to group and directory pages:

/**

* Modify the group type status

*/

function sv_get_group_type( $type, $group = false )

{

global $groups_template;



if( ! $group )

$group =& $groups_template->group;



$gtype = groups_get_groupmeta( $group->id, 'group_type' );

if( $gtype == 'type_one' )

$name = __( 'Type 1', 'group-types' );



elseif( $gtype == 'type_two' )

$name = __( 'Type 2', 'group-types' );



elseif( $gtype == 'type_three' )

$name = __( 'Type 3', 'group-types' );



else

$name = __( 'User Group', 'group-types' );



if( 'public' == $group->status )

{

$type = sprintf( __( "%s (public)", "group-types" ), $name );

}

elseif( 'hidden' == $group->status )

{

$type = sprintf( __( "%s (hidden)", "group-types" ), $name );

}

elseif( 'private' == $group->status )

{

$type = sprintf( __( "%s (private)", "group-types" ), $name );

}

else

{

$type = ucwords( $group->status ) . ' ' . __( 'Group', 'buddypress' );

}



return $type;

}

add_filter( 'bp_get_group_type', 'sv_get_group_type' );



/**

* Modify the group type status on directory pages

*/

function sv_get_the_site_group_type()

{

global $site_groups_template;



return sv_get_group_type( '', $site_groups_template->group );

}

add_filter( 'bp_get_the_site_group_type', 'sv_get_the_site_group_type' );

It’s quite a bit of code, but it should get you started. This hasn’t been tested with 1.2 btw.

well there are members plugins that wont allow the nav to show if the member isnt logged in, one is user access manager – you can specify pages to not show all together, in nav as well – would this work?

There are other platforms and have tried a few myself. As new as the bp platform is, it is by far the quickest out of the box that enables much of what you need already (together with wpmu). However other platform might offer more fine grained control, but it comes with a hefty learning curve as the platform is simply more complex. The upside to bp’s less complex architecture makes it also easier to develop for.

I’ll see if I can give some input on your requirements.

The main feature is an easy and somewhat restrictive way to post content. The only thing girls can publish is pictures of outfits, and then tag the clothes (describe, tag, categorize…).

It looks like you need a custom content type that omits the post message. Flutter allows you to create a specific post type. I haven’t tried it with wpmu. There is also a wpmu plugin called ‘toggle_meta_boxes’ which allows you to hide unneeded post boxes to make it super easy for your users to just upload content.

We want to have some level of control here. BTW not all users can upload content.

Since you only have one subject users post on I would recommend NOT giving every user a blog at sign up, but just let them post to the main blog. Keeps you in control over categories, tags, etc. Plus it lets you control the user level. I however you do want to give users a blog there are wpmu plugins which allow you to set blog defaults like categories, predefined pages and posts and such. Also you can make new blog users have an editor role rather than an admin role if you want to control what they can or can not do.

The content published by everyone goes to the main page, same of today.

This is done by buddypress through widgets or even custom loops if you are adventurous.

No problem there.

People con vote their fabs.

I haven’t looked at this, but I imagine there would be a wp plugin which would let users vote on posts. If you can find a vote plugin that serves an RSS feed you could pull that into the bp user profile. EVen link it to the activity stream with a small custom plugin.

When user is logged in, she sees the content of the girls she is following (not pictures of everyone, just pictures of the ones that inspire the user).

In bp through making friends with other users you can follow the activity of your friends only. At the moment the activity stream is text only, afaik, but I think images in the activity stream is in the pipeline?

User profile is built by the outfits she publishes

The profile page shows the latest activity, blog posts, wire messages, etc. of the profiles user.

and the outfits she favorites.

This is the most dificult part, since I haven’t looked into it. Assuming you can find a good vote/favorite plugin it should be doable.

You can search for/discover/subscribe to trends, types of clothes, styles, colors, people…

This is where bp shines as the search is very well done. Combine it with bp_contents plugin which allows your users to tag themselve, groups, blog and add categories…your archiving possibilities are endless.

Some pitfalls (already mentioned):

Privacy controls, inappropriate content flagging (is coming in 1.1 though), it is still not an out of the box solution (however for you requirements there is none that I can think of).

There are still even other approaches when I think about it, I would recommend wp and bp in a heartbeat. Especially since the backend of both are really solid. Plugins are installed and upgraded easily. It is a widely supported and growing platform and would not hesitate to recommend it to you.

I hope this helps a little bit.

It looks like the options bar is showing up on the directory pages when it shouldn’t – most likely because I forgot to add a hide function. All the other pages are working fine. I will update this.