You can tryout Buddypress Analytics Plugin at https://wordpress.org/extend/plugins/buddypress-analytics/
This plugin will allow you to use your analytics script with your buddypress site (with wordpress mu) Supports any analytics script including but not limited to Google Analytics.
More info at http://www.pingsense.com/2009/11/buddypress-analytics-plugin/
Please let me know if you got some success asap
I just installed BuddyPress Links and It would be interesting to see if it can be hacked together and modified so that it can be an aggregator
any thoughts dudes?
I have also now tried resetting the permalinks, by using the save the option, and still no change.
I checked the .htaccess file against the default and nothing has changed, so the site has the default .htaccess settings, does it need any custom entries for Buddypress?
The BuddyPress install was manual, upload the BuddyPress folder to /wp-content/plugins/
Then moved the bp-default themes to /wp-content/themes/ and activated the theme
David
You could try our Buddypress Ads Plugin available at https://wordpress.org/extend/plugins/buddypress-ads/
This plugin will allow you to publish ads through your buddypress site(with wordpress mu) Supports multiple ad networks including adsense , adbrite and many more. Just replace the ad code in the file bp-custom.php with your own ad code.
http://www.pingsense.com/2009/11/buddypress-ads-plugin/
Have a look at how it’s done here on buddypress.org (at least on the CSS end of things). https://buddypress.org/developers/boonebgorges/ The nav li items are floated to the left.
As for the PHP, you might have to play around with where the userbar and optionsbar are called in header.php of your child theme. Most of the work is done in the CSS though – the markup is pretty flexible.
Huh… Thought I fixed that. Looks like it crept back in. I’ll check it out.
I put something together along these lines today. I used the version of TinyMCE that ships with WP. Have a look, and please feel free to build on it or tell me what I’m doing wrong 
: http://teleogistic.net/2009/12/tinymce-in-buddypress/
5563306Inactive
We have installed wordpress and buddypress in our site.
After the last buddypress update we discovered that USERS can´t upload avatars.
Once they select the file and click UPLOAD they receive “(Error when uploading! The error was The file type does not meet security policies. Try another)”
BUT admin user can upload avatar without problems!!
We are using WordPress MU 2.8.6 and BuddyPress 1.1.3
Thanks!
Francisco
I think a directory page might make more sense than a sidebar list. What happens once you have 100 documents? Also, it would really make sense with the rest of the BuddyPress world. You could have tabs for “all documents” and “my documents”. You could have sorting by “active”, “recent”, “popular”. etc. And you could have “search” of course. Maybe not to start… but you know… Phase 2.
And how could anyone hate the WordPress backend?! It’s awesome!!! Show them Joomla… then their heads would truly explode. But I understand how being taken into a completely different interface would be jarring. And I think it’s a huge bonus that this will all work on the front end. Nice.
@Andy figured. cool. thanks.
I was hoping you’d say don’t touch the default for another 2 weeks! Now I have no excuse not to get to work 
Yep, the original default is just renamed “classic” but has been updated. The wire has been completely removed from both the new and old theme and replaced with the new activity stream posting.
I will more than likely include the wire and status updates components in the “backwards compatibility” plugin for people to use with older themes.
I would consider it safe to begin working with the 1.2 theme. I expect there to be mostly bug fixes from now on. There is a chance thread favouring and/or reply notifications make it in before i freeze new stuff on Dec 30th, but it all depends on time. It should not change the theme though.
The final 1.2 should be out at the end of Jan.
I have a couple of lazy questions.
1. Will BP 1.2 still support the 1.1 default theme if people still want to use it?
Edit: Yes
1(b). Is the wire totally dead, or just not used in the new theme?
Edit: I am guessing it must still be there if the old theme is still supported.
2. Is there any kind of timeline as to when the new default theme will be considered safe to start working on plugin support? I want to avoid any extra iterations due to sudden changes in direction.
Edit: Late January?
Ok, that was three.
@Mike Pratt – unfortunately previous to the change the links to threads were only being recorded with the group slug. Any posts from this point on will contain the link to the actual thread on the “View Thread” button.
@Mike,
seems this is already fixed at testbp.org
Hi I am not sure if there’s now (seven months later) a better idea…. Is it possible for a contributor to subscribe at a sub blog, rather than going to the route buddypress install to register?
Thanks in advance
Add “?” to the end of the url..
https://codex.buddypress.org/?
Add “?” to the end of the url..
https://codex.buddypress.org/?
Just to confirm I’ve tested it with the BuddyPress default theme now and it’s still saving the wrong hash in the database for some reason :S
The signup-password POST data is definitely being delivered to the signups backend PHP… so I can’t work out why it wouldn’t be saving it correctly…
Hi again,
Everything is done through the frontend – our students and academics absolutely hated the backend (and I tend to agree – at least in regards to buddypress doing pretty much everything through the frontend aside from blogs).
1. Wiki directory page is definitely on the cards but we’ve not started working on that yet. Probably something for the new year 
2. Tags would be nice but I suspect something that will come later too sorry…
3. I’ll discuss the idea of a vertical page listing with people more next week. I suspect it’ll be put on the back-burner until we’ve got most of everything working properly though. (e.g. whatever the rest of the team have already partially completed will be the way we go for the next week or two).
FYI each commit message is being duplicated:
Revision 2206: Fixes #1478: Fixes #1478 http://bit.ly/7QLtay
