I had the same problem. Odd, my sign up link didn’t even show up??? But I did what windHamDavid said and I went here /wp-admin/wpmu-options.php
Note: because I have MU installed maybe different for regular wordPress
I disabled registrations saved and re-enabled, and it worked.
Thanks windHamDavid
Plugin’s been updated to fix all known bugs, now at 0.0.3.
Download or update to the latest version.
It would be cool to just use the single WP blog for a site-wide blog with BP. Each user’s page could query their own posts to show their “own” blog. The site could pull blog posts from all users collectively and easily. And best of all, it would keep uniformity and simplicity across all blogs.
I know this functionality is already in WordPress, but what I am asking for is a way for users to post on the front-end, seamlessly with BP, so they don’t even have to know they are using WP (just like everything else is with BP).
Being a developer myself, I can create a plugin for this, but I think it should be in the core.
Any thoughts?
@finni3 Until Andy trumps all of our work and goes deep core, Boone’s & D Cartwright’s excellent merged plugin will fit your needs https://wordpress.org/extend/plugins/buddypress-group-activity-stream-subscription/
Does the problem occur when you deactivate WP-o-matic?
My guess is it definitely has something to do with WP-o-matic.
I’d recommend moving to FeedWordpress myself.
Create a new page in the WordPress backend. Then go to the “Settings > Reading” and select that page as the front page. You may want to create another “Blog” page and set that as the posts page.
We need some more votes on the plugin page for BuddyPress, there are only 19 and I know/hope there are more people using and liking it than that. 
So, if you use it and like it, vote it up! I feel like people miss this with BP since much has been direct downloads from the BuddyPress.org site in the past.
Also – if everything is working for you correctly, please be sure to mark it as “Works” on that page too. That way others can benefit when they look to install.
All here on the right sidebar (use the same login): http://wordpress.org/extend/plugins/buddypress/
Okay. I’m a little less advanced than most on this site. I was in my wordpress dashboard and noticed this plug in on the bottom of the page. I clicked on it, hit install and I thought that I activated it. It all happened so fast. Anway, now, wehn I log into my admin at wordpress, this message is just parked on the screen and I don’t really know how to change it. It won’t let me go to any other screens to activate or deactivate anything. Thoughts? Can I delete the buddy press file from my files . . . if so, will it make this error go away and allow me back into my wordpress administrative console? Thanks. Collin
I just installed buddy press, like it and got this message:
Fatal error: Call to undefined function is_site_admin() in /home/content/02/5452202/html/keeptexasinsured/wp-content/plugins/buddypress-like/bp-like.php on line 34
and it is totally preventing me from doing anything in my console in wordpress. when I log in, this error message is just standing there and i can’t do anything about it. Please advise.
A few other actions were added in 1.2 to help plugin authors hook into the correct places within BuddyPress.
bp_setup_globals
bp_setup_nav
bp_setup_root_components
bp_setup_widgets
The intent of those hooks for plugin authors, is to not load your code before BuddyPress does, potentially putting your navigation menus or global component setups out of alignment with BuddyPress. Typical WordPress priority rules apply, so it is still possible to bump your plugin ahead of BuddyPress if you need to.
I’m running WPMU 2.9.1 and BP 1.1.3. I’m about to update my website to BP 1.2.1 tonight but I can’t find the guide on how to do that. The first-time installation guide here makes no mention of what to do for existing installations.
I’ve looked around online and I thought that I saw it somewhere but now I can’t seem to find it and it’s not listed on the front page blog post. I saw the post for upgrading from 1.2 to 1.2.1 but is that the same for 1.1.3 to 1.2.1?
Could I possibly…
1. Deactivate all plugins
2. Deactivate the BP 1.1.3 plugin
3. Use FTP to completely delete the BP 1.1.3 plugin from my plugins folder
4. Then use the “Add New” plugin option from the WPMU dashboard to install BP 1.2.1
5. Activate BP 1.2.1
6. Finally, activate all other plugins
Would that work? Or do I need to use the Backwards Compatibility Plugin if I had been using the default BP 1.1.3 theme up to this point? What if I’m ok with now using the BP 1.2.1 theme? Do I still need to use the Backwards Compatibility Plugin? The plugin page doesn’t specifically come out and say that… or am I just missing it?
Thanks,
Paul
Gotcha…except I’m seeing “userbar” referring to different things as well.
https://buddypress.org/forums/topic/horizontal-userbar
Whatever it’s called, it seems like a critical piece to creating a self-perpetuating network. Anything we can do to make it easier for members to promote the network helps.
WPMU Dev Premium has an affiliate plugin that creates member-specific code tied to images.
http://premium.wpmudev.org/project/wordpress-mu-affiliate
A basic badge that links back to the member’s profile should be much simpler. To me, this should be a core function…
ok, tagged on wordpress repo v0.0.2
https://wordpress.org/extend/plugins/buddypress-sitemap-generator/
Hopefully next weekend I’ll get the Admin UI cleaned up, some documentation, and a priority calculator
Also looking for MU users to test it out.
…and least Google accepted it 
Sitemap Index Total: 5,629, Indexed: 116 Feb 23, 2010 – Resubmit Feb 23, 2010
username = tester123
installed under subfolder URL = http://www.example.com/tester123
all sub menu access (profile, messages, friends, groups, etc.) will redirect to home
clicking on user’s profile will redirect to members list
[wordpress2.9.2 + buddypress 1.2.1]
sometimes when you copy items from a folder on harddrive to server via ftp program it misses hidden files like .htaccess
You can create a file htaccess.txt add the rewrite code then upload it after upload change the name of the file to .htaccess
I’m using WP single and this is whats in my .htacess file
RewriteBase /
#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.*/wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
<IfModule mod_security.c>
<Files async-upload.php>
SecFilterEngine Off
SecFilterScanPOST Off
</Files>
</IfModule>
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
we usually call them “userbars”, as facebook changed the name just to make themselves proud to invent something new… 
sure it can be easy to code, i’ve done a great version for vBulletin, and it would take little to make one for WordPress… i suppose someone will be able to code one..
Hey I solved this problem.
There were two problems:
1) no .htaccess
2) Text editor in Mac
You should have .htaccess in your FTP.
Maybe it’s hidden, but if it is not, you should make one.
You can make it with a simple text editor:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
copy and paste this and save it as .htaccess and upload it your root wp folder.
Another problem for me was that I used the text editor in mac.
Its RTF format put some information in the beginning of the file which is invisible in the text editor.
That caused 500 error problem.
So I made .htacess in Dreamweaver (the memo app in Windows would be OK I guess), and uploaded it, IT WORKED.
I hope this would help for other people.
The reason my FTP did not have .htacess in the first place is beyond me.
There are lots of regular WP event plugins. I’d suggest searching on the wordpress.org site / forums. But for a BuddyPress integrated plugin… there are only two… one which is a WordPress MU Premium (paid) plugin… and bp-events from Erwin… the development of which seems to come in spurts. Last I heard… Erwin was pretty far along in making it 1.2 compatible and was mostly just working on an Ajax calendar feature. Hopefully it will be finished up soon-ish :o)
ehmm, please refrain from opening new posts which basically links to an other post which links to another post 
Not that I do not agree with your request, but by annoying people who might be able to help out, you steer focus away from the problem.
Anyway, does feedwordpress not work?
I should highlight this again since it has changed, and it’s very important.
If you’re building a plugin that relies on BuddyPress, you MUST make sure it doesn’t break the site if BuddyPress is disabled and your plugin is left enabled. A perfect example of this scenario is upgrades.
It’s easy to do this. I’ve found a good solution is to use a loader.php file and include this code (based on code from jjj):
/*
Plugin Name: My Plugin
Plugin URI: http://example.org/my-plugin/
Description: My BuddyPress plugin
Version: 1.0
Requires at least: WordPress 2.9.1 / BuddyPress 1.2
Tested up to: WordPress 2.9.1 / BuddyPress 1.2
License: GNU/GPL 2
Author: Some Person
Author URI: http://example.org/me/
*/
/* Only load the BuddyPress plugin functions if BuddyPress is loaded and initialized. */
function my_plugin_init() {
require( dirname( __FILE__ ) . '/my-plugin-bp-functions.php' );
}
add_action( 'bp_init', 'my_plugin_init' );
/* Add any code here that does not rely on Buddypress */
So basically include any code that will not work if BuddyPress is disabled in a separate file that is only loaded when BuddyPress is active and ready. That way if BP is disabled, the code will never be loaded an won’t whitescreen an install.
Hello,
I’m having the same issues……..I do not have an “.htaccess” file anywhere on my hosting server.
I read that the two latest versions of WordPress and Buddypress may not be compatible – could this be the problem?
Thank you!
Rob
I started the group for splogging and spam a while ago, but to be honest I haven’t experienced any for quite a while now.
@andy’s right about changing the signup slug, that made a big difference for me. I also renamed (removed) the wp-signup.php file as that’s not in use, and again that made a difference – though watch for that on a wpmu / wp upgrade as it’ll replace the file.
I removed the WordPress references in my theme footer too, just to make it a little less obvious that I’m running WP.
Also running SI-Captcha antispam and NoSpamNX, but that’s about it nowadays.
@geofm33
– Yes just like that 
– hmm i could do that
will be there in the next version.
Next version will be a version that is going to be on the wordpress plugins site, so everybuddy can update it directly from the admin.
@blackphantom, bloody brilliant!! Fixed the 404 issue!
Here is where I am with what doesn’t work (WordPress 2.9.2 and BP 1.2)
– I don’t see the filter for “Tweets” in the pulldown for the activity stream.
– My Twitter > BP timestamp is off by 6 hours.
– My Twitter > BP sync doesn’t work with (or I don’t understand) filters! It works when I remove the filters.
Requests:
– Extend the new forum topic “To Twitter” functionality to allow the same thing for topic replies.