This is just an opinion from someone who’s never used the plugin… but it’s basically for login / registration ease.
You don’t have to register a new account to become a member of someone’s BP network… just login with your Facebook account!
According to the plugin’s description, there are plans to integrate the friend list and also newsfeed publishing.
You might want to head on over to the WordPress MU forums as it sounds more like a WPMU problem:
https://mu.wordpress.org/forums/
You can login with the same username and password you use here to post on the WPMU forums!
@mark, make sure you upgrade your FeedWordpress plugin as I’m guessing you upgraded from WPMU 2.7.1 to 2.8.4a.
FeedWordPress has undergone major changes since then to be compatible with 2.8+.
Oh! and also overwrite the default WordPress RSS library with FWP’s Magpie RSS library.
For more, read the upgrade installation instructions:
https://wordpress.org/extend/plugins/feedwordpress/installation/
Argggg, I spent 24 hours of non-stop trial and error (considering I am a PHP noob) to make my site work after the buddypress 1.1.1 upgrade. Made a lot of tweaking with the avenuek9 theme to look like how my site used to looked like before the upgrade. I hope you gurus can make this How-to- stuff soon. If you look at my site, its still a mess (http://bloggista.net) but it should be back in its handsome form once those minor issues are ironed out. Like, the recently active avatars are lining up in single file down to the bottom as if they’re queuing for the some firing squad.
Thanks folks, looking forward to it.
Hi snagfly. I’m the author of that plugin. It sounds like the problem is that you activated the bbPress trigger plugin inside of WordPress. As is stated in the readme files, this part of the plugin is only needed if you are running a separate installation of bbPress with BuddyPress 1.0.
If you are running BuddyPress 1.1+, you can safely delete the file bb-group-forum-subscription.php, keeping and activating only bp-group-forum-subscription.php.
I would prefer moving all admin for members out of wp-admin into the site, instead of trying to make wp-admin look more like the site. Keep wp-admin for admin only and put all member functionality in the site.
That’s not a bad idea… just making an admin theme that looks more consistent with BuddyPress. Less jarring for newbies.
Previous to BP 1.1, all user registration was dealt with by WordPress, so it’s technically correct to point people towards existing WordPress/MU resources and forums for help.
Since BP 1.1, however, BP changes the new account confirmation/activation email – because on the standard BP 1.1 signup page, the user can pick their own password. And of course, it’s a security issue if we were to somehow send their (encrypted) password back to them. So BP 1.1 overrides the standard WordPress MU email so it doesn’t include the password text.
But, the activation link is part of WordPress. Yes, the BuddyPress default theme uses this behaviour too – but it calls the WordPress code.
Yes it is confusing for users that you have to make a post to one place and to change your avatar to another.
Well what we are doing now, is putting all buddypress ‘admin’ settings in the wp-admin and reorganized them…
right now we have:
Posts
Comments
Messages
Settings
Appearance
(with submenus off course)
Everything else is stripped out. I can imagine 100 of structuring this, but for this particular install, this is what we needed.
We have very limited time.
So what i did is used an existing “admin theme plugin” and changed it so the wp-admin matches the look and feel of our front end. (think eg. facebook ‘front and back’, or lastfm etc ).
The most difficult part is getting the bp functionality such as messages completely work back end. Which atm we haven’t managed yet.
I’m still lost. I also don’t really have time to look at this until the weekend sometime. Could you help me again please?
Yep, I go to the main blog via Users menu (not site admin>users) and…
Could you give me a sample link (feel free to cut your domain off the beginning), i.e. http://example.com/how_to/get_to_this/page. I’m being a noob and can’t see it 
...EXCEPT the email with username & randomly generated password that should replace that activation email shown above. (I'm thinking this is a wordpress email? Not sure.)
Correct. Welcome Pack doesn’t (or shouldn’t) touch the activation email, which is why this issue is so weird-sounding.
You ARE aware since BP 1.1, if a new user registers via http://testbp.org/register, they are able to pick their password and as such it isn’t emailed to them? (Though they still get a confirmation/account activation email)
@jeff
I appreciate the feedback and perspective. What’s weird is I built a modular php/mysql site circa 2002 basically overusing includes, very basic css and taking functionality from Hotscripts.com’s PHP repository. In fact, what I liked about php was the modularity of what I was doing (even if a bit sloppy). BP/Wordpress seems to promise the same, but frankly the number of sites that deviate from the structure of the standard theme is small (maybe it’s too new). It’s like the complexity of the theme structure has scared people off or the fact that the themes are both style and functionality makes it difficult to be modular.
I’m hard-headed and have no hurried timeline – I’m designing for myself. I’ll probably take this on and suffer the pain of BP’s infancy just like I did in 2002. That was my education. What would be helpful is a methodology for taking on something like this.
My threshhold question is whether to use a theme framework as a starting point or whether that’ll be too restrictive and I just need to bite the bullet and build my own theme. I’d be on the hook for updates (sucks), but it sounds like it may save some pain. My limited understanding of actions/filters is that I should be able to build almost anything from a good theme framework using functions.php and style.css, etc., but not sure if that’s true or whether it’s worth pain of learning that way of developing instead of just tearing apart templates.
I’m sure, by the time I’m done there’ll be dozens of modular BP themes/frameworks to choose from. That’s what happened after I slaved over the site in 2002. Who knew WP was there with plugins for most of the stuff I hardcoded myself.
I assume you mean the plugin Group Forum Subscripton for BuddyPress found here:
https://wordpress.org/extend/plugins/group-forum-subscription-for-buddypress/
You need to contact the plugin developer and provide them with the details about your issue.
I’m moving this thread to the proper forum, “Third Party Components & Plugins”.
Most of the sites that you mention required many weeks to months of hard design and custom coding work. You need the proper design, CSS, and PHP skills to tackle this on your own. Or, you need to hire out an expert WordPress/BuddyPress developer like GigaOM Pro did–or even a team of developers.
Yep, I go to the main blog via Users menu (not site admin>users) and input the username and email address, select skip confirmation email, send. I get all of the notifications welcome pack sends out EXCEPT the email with username & randomly generated password that should replace that activation email shown above. (I’m thinking this is a wordpress email? Not sure.)
The weird thing is when I do the same process from a sub-blog everything behaves the same except I DO get the email with the username & randomly generated password in addition.
In case it helps here’s what happens over 3 tests from each main & sub blog dashboards:
MAIN BLOG DASHBOARD:
1. Broken activation email – came first all 3 times
2. Then these 3 come, random order each time:
Welcome pack welcome email
Welcome pack friend invite email notification
Welcome pack group invite email notification
SUB BLOG NEW USER:
1. Broken activation email
2. Then these 4 come, random order each time:
Account is setup email with username and randomly generated password
Welcome pack welcome email
Welcome pack friend invite email notification
Welcome pack group invite email notification
Using google, beginning to answer my own question.
http://vocecommunications.com/blog/2009/07/expanding-wordpress-with-buddypress-the-tasty-kitchen/
Now I’m wondering if I’m biting off more than I can chew. Anyone else taking on something this aggressive?
What happens when you disable FeedWordPress?
If the errors go away, then there is an incompatibility issue with that plugin and the current version of BP and/or version 2.8.4 of WPMU. Contact the plugin developer, provide them with the details about your issue, and ask when the plugin will support BP 1.1.1 and WPMU 2.8.4.
Looking at the listing for FeedWordPress ( https://wordpress.org/extend/plugins/feedwordpress/ ), it does not mention that it is even compatible at all with BP. It also indicates that it is only compatible up to version 2.8.1 of WP.
Well, I agree with WordPressfan…
But i’m still stuck 
Hello to all,
we released new version of Buddypress Multilingual.
It works out of the box with Buddypress themes (tested with BuddyPress Default Home Theme 1.0.3).
Next week we are going to see if migration to Buddypress 1.1 will require any adjustments and test it more on guest blogs.
@Erich73: we added switching on the fly. Thanks for suggestion.
I believe our issues are different but both may be directly related to conflicts between buddypress and feedwordpress. Buddypress is a sitewide plugin and the buddypress bar loads for every blog page – so every blog error could potentially be related to buddypress. I don’t have my problem when buddypress in deactivated. So my issue (and yours) with feedwordpress may be a buddypress issue rather than a wpmu issue.
Given your pm reply, I assume you’re not experiencing the same error as I. I have not seen the issue you reported either.
https://buddypress.org/forums/topic/feedwordpress-and-php-warning
Thanks! Shockingly confusing to find BuddyPress plugins… It dawns on me that WordPress.org is the place to look, and not here:
https://buddypress.org/extend/plugins/
That should be cleared up somehow. Personally I wish BuddyPress plugins would only be posted here on BuddyPress.org, so there is one centrl place to look.
Anyway, muchos gracias David;-)
The problem with using the default child theme as a base for a new theme is that it is much more work. Rather than fit the thousands of WordPress themes into the default child theme, it seems easier to fit the needed BuddyPress features into the style of the many, many WordPress themes being produced for free or commercially.
Well… this doesn’t help… but really… as far as popular CMS tools go… the WordPress backend is about as easy and intuitive as it gets. I find most clients take to it pretty quickly and easily and end up loving it and using it a lot. Compare that to Joomla sites I’ve worked on where the clients end up abandoning the site because it take a computer science degree to wrap your head around it’s confusing interface and concepts. Again… I know that doesn’t really help you.
Have you looked at limiting user roles and screen options to streamline the WP backend? I always set clients up with something less than full admin privileges and turn off a bunch of screen options they won’t need or understand.
My bp component working fine in 1.0.2 but giving me warning in 1.1.1
I replaced
bp_core_add_nav_item(
__( ‘Example’, ‘example ),
$bp->example->slug
);
by
$args = array(
‘name’ => __( ‘Example’, ‘example’ ),
‘slug’ => $bp->example->slug,
‘item_css_id’ => false,
‘show_for_displayed_user’ => true,
‘site_admin_only’ => false,
‘position’ => 99,
‘screen_function’ => false,
‘default_subnav_slug’ => false
);
bp_core_new_nav_item($args);
but giving me warning
call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ” was given in /opt/lampp/htdocs/wordpress-mu4/wp-includes/plugin.php on line 414
Thanks in advance
Same here I have been looking at doing a rewrite of the dashboard side for users, because not everyone is a seasoned wordpress user.
