It’s important to note that BuddyPress is an opensource project, just like all of the other WordPress related ones. That being said, if you find something isn’t working up to your expectations you are free to develop or contribute to the project to make it work how you wish. As it stands today, BuddyPress does a good job of keeping tidy and cleaning up after itself; better than most plugins in my opinion. The signups table is specific to MU and is a new addition, so you can expect it’s functionality to be misunderstood. When a user is deleted, the idea is that their signup remain in the signups table as proof of their previous registration. One could even argue that removing all user data is a bad idea in the event someone ever needs it later, say for law enforcement purposes.
Regarding blocking spam registrations, read some articles about Twitter. Some analysts have said that nearly 50% of all registrations on Twitter are spammers. Crazy eh? There just isn’t a fool proof way to prevent it from happening unfortunately.
Also, while none of the moderators are directly employed by Automattic, it’s about the best internship I think anyone in our respective businesses can hope for. We all do our best to represent Automattic and are here to help to the best of our abilities.
If you can find a specific bug or flaw in how users are currently managed between BuddyPress and WordPress, you’re welcome to respond here or file ticket in the trac. If you feel your opinion warrants more attention you can message me privately if you’d like also, and I’d be happy to help further.
I really do appreciate all the work you do. I’m just really frustrated with the lack of synchronization and consistency between Buddypress xprofile and WordPress users/usermeta etc. Automattic needs to take a serious look at member management.
FYI, here’s the response from the WPMU forum:
Because if a spammer signs up, for instance, and you delete their username and blogs, if their registration member is also deleted, then they can sign up again.
I’m not satisfied with that answer. There must be cleaner ways to block/blacklist spammers.
Isn’t there a plugin that deletes users more thoroughly?
OK, thanks, I’ll post the question there.
But lack of synchronization between Buddypress xprofile and WordPress wp_usermeta etc. is also causing me lots of headaches, so I hope WPMU is not going to send me back here saying that it’s a Buddypress problem. Aren’t you all part of Automattic somehow?
Gabriel-
and then tag the clothes (describe, tag, categorize…). We want to have some level of control here.
In case you have not seen this, there is a wonderful BuddyPress plugin that can address this need: https://wordpress.org/extend/plugins/bpcontents/
Sorry for being a little slow on this topic, but activity streams are hard to wrap my mind around, mostly because I don’t quite get the technology. Does openmicroblogging — is this a viable part of Joseph Smarr’s so-called “social stack”? (I think they’ve moved on to calling it something else now, not “social stack,” but I digress…)
I’ll be building a version of a micro stream soon enough, or trying to adapt a former one (such as the “wire”?) to suit my own purposes.
As I understand it, there’s already a bit of a WordPress plugin:
http://adrianlang.de/mnw/
Why rebuild the wheel, when it’s built? Perhaps we should borrow/resuse from that plugin
There’s a bit of development/discussion going on over here for WordPress itself:
http://groups.google.com/group/diso-project/browse_thread/thread/84481ef2e912a099
http://groups.google.com/group/diso-project/browse_thread/thread/b9f1b8865d3d8526
Update 2: Well, I got somewhere. Buddypress appears to be working. The weird part is that I can’t deactivate it. When I click deactivate it says “Plugin could not be activated because it triggered a fatal error.” How weird is that?
I am going to run with it for now. Theme is going to need a lot of work… the fonts appear to have grown for some reason. must be a problem with my custom CSS
I did find a similar plugin, https://wordpress.org/extend/plugins/visitor-likedislike-post-rating/, if anyone could help me edit it so that it shows who voted what it would be perfect!
UPDATE: I attempted to delete all my plugins (mu and normal) from my site. Once they were all deleted, I reinstalled buddypress and then reactivated all of my plugins and yet still I receive the same fatal error.
Is this a problem with 2.8.2?
Before I chime in, when we run our unit tests with users; we:
- When testing an upgrade, I always delete a test user of mine: qauser
- sql delete, and php register the user again after the upgrade.
- I leave one user, qaeditor around. This user stays with the upgrade.
- Allows me to know if perms were set across apps, if new users are good to go, and if old users are ok.
- We flip roles too, but thats another test.
Anyways, Camel Case not supported for login.
Lowercase was put in back in 05.09 https://trac.mu.wordpress.org/changeset/1770
In trunk here is the snipit:
571 function _fill_user( &$user ) {
572 global $wpdb;
573
574 // WPMU uses lowercase logins
575 $user->user_login = strtolower( $user->user_login );
By “post”, what do you mean exactly?
A BuddyPress forum post, or just a regular blog post?
If it’s a blog post, I’m quite certain a WordPress plugin can handle that.
What do you mean by “get the RSS feed from a ‘regular’ WP blog”?
Well if I get the RSS feed from a regular installation of wordpress then it works. Perhaps there is some setting that is locking out the RSS feed from the widget.
However, if you click on the link for the feed, it does show something. Take a peek at:
http://www.piptopia.com/tribe/news/feed/
Is the hook to use this?:
user_register
Runs when a user’s profile is first created. Action function argument: user ID.
So something like this?:
<?php
/*
Plugin Name: Real Name Synchro
Plugin URI: http://
Version: v0.001
Author: peterverkooijen
Description: A plugin to store firstname and lastname from the fullname field in Buddypress registration in WPMU usermeta tables, based on examples in the <a href="http://www.devlounge.net">Devlounge</a> series.
*/
if (!class_exists("RealNameSynchro")) {
class RealNameSynchro {
function RealNameSynchro() { //constructor
}
function xprofile_sync_wp_profile() {
global $bp, $wpdb;
if ( (int)get_site_option( 'bp-disable-profile-sync' ) )
return true;
$fullname = xprofile_get_field_data( BP_XPROFILE_FULLNAME_FIELD_NAME, $bp->loggedin_user->id );
$space = strpos( $fullname, ' ' );
if ( false === $space ) {
$firstname = $fullname;
$lastname = '';
} else {
$firstname = substr( $fullname, 0, $space );
$lastname = trim( substr( $fullname, $space, strlen($fullname) ) );
}
update_usermeta( $bp->loggedin_user->id, 'nickname', $fullname );
update_usermeta( $bp->loggedin_user->id, 'first_name', $firstname );
update_usermeta( $bp->loggedin_user->id, 'last_name', $lastname );
$wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET display_name = %s WHERE ID = %d", $fullname, $bp->loggedin_user->id ) );
$wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET user_url = %s WHERE ID = %d", bp_core_get_user_domain( $bp->loggedin_user->id ), $bp->loggedin_user->id ) );
}
add_action( 'xprofile_updated_profile', 'xprofile_sync_wp_profile' );
}
} //End Class RealNameSynchro
if (class_exists("RealNameSynchro")) {
$dl_pluginSeries = new RealNameSynchro();
}
//Actions and Filters
if (isset($dl_pluginSeries)) {
//Actions
add_action('user_register', array(&$dl_pluginSeries, 'xprofile_sync_wp_profile'), 1);
//Filters
}
?>
Testing it now…
Edit: Activating this plugin produces a white screen. Not a good start… 
Where did I go wrong?
@Gpo1
I added a “share this” feature using the Add-to-any plugin which seems to be a quite good plugin.
So if that plugin is enabled, you’ll be able to check an option in the admin to show or not the share button.
ow.. this is really annoying..
if the problem is wordpress cache system.. isnt it a compatible problem? because only default caching was open 
btw.. that notification is still there..
no one got a similar problem or am i alone?
Check out the skeleton component plugin. I teaches you how to make a bp component. It has examples where it sets up two custom pages with according links, etc. That’s how I re-created the dashboard, but r-a-y’s would also work.
The skeleton component takes some time studying as it will go over much more than just setting up page templates, but it is a good learn if you are developing with bp and creating a dashboard component would be a good entry level start.
Ahh… well I actually created my version of the dashboard using a WordPress page (specificaly a WordPress page template), and not BP’s components, which is what Andy is doing.
To tell you the truth, I haven’t studied how new, component slugs work, so I just stuck to my tried-and-true WP skills 
What I did was enter the BP loops in my WP page template, but before I entered the BP loops, I do a conditional so only logged in users can view the dashboard content.
Hope the logic makes sense.
At this point I am questioning everything. Following Burt’s updated integration instructions there is only one point where I have the slightest doubt. In the bbPress admin page for WP integration, it says the following about the SALTs:
This must match the value of the WordPress setting named “auth_salt” in your WordPress site. Look for the option labeled “auth_salt” in this WordPress admin page.
There are no SALT values in “/wp-admin/options.php”. So I put values like the following in wp-config.php:
define(‘AUTH_SALT’, ‘XXX’);
define(‘LOGGED_IN_SALT’, ‘XXX’);
define(‘SECURE_AUTH_SALT’, ‘XXX’);
…where the XXX values came from “https://api.wordpress.org/secret-key/1.1/”. I have corresponding “BB_” entries in “bb-config.php”.
Need more info, Reboot Now.
Can the user log into WordPress? But not into bbPress?
Okay, here’s another check:
Double-check that your uploaded bbPress files are actually the same as the files from the distribution package! This one killed me a couple of days ago.
Have you used the bbPress Integration plugin?
https://wordpress.org/extend/plugins/bbpress-integration/
And copied the config lines verbatim?
You probably have just double-checking!
I still don’t get why when I go to domain.tld/home the members link lights up (in the BuddyPress Home Theme). And how do I make the community WordPress Page appear instead of a page listing the folders inside the community folder (forums).
As enthusiastic as you are about WordPress, most of us are about BuddyPress, so without speaking for anyone else, my opinion is biased towards using BuddyPress for every website. My moms knitting website will use BuddyPress. 
If you want users to be able to blog about their own stuff without moderation, then you want WordPressMU, because each user gets their own blog to talk about whatever they want; WHATEVER they want. That means even though your site is about fashion, that doesn’t stop them from talking about puppies.
If you want these users to be able to interact with each other, and have personalities, then you want BuddyPress.BP will allow your users to talk to each other privately, form groups to talk about things with each other, and comment on each others profiles.
The reasons NOT to use BuddyPress? At the moment there’s very little restrictive control over what people do. You can’t stop someone from putting profanity in their profile. You can’t block a user from messaging you or others. Also, the platform is still evolving as much as WordPress and bbPress are. That means that if you like to keep your website on the cutting edge, you’ll find it hard to install everything and leave it alone, as enhancements and improvements are coming through at least monthly, and so far upgrading isn’t a one click thing yet (almost though)
Those is my opinionses… Not sure how helpful they is, but if you like WordPress, you will probably see the potential of BuddyPress for what you want your website to be.
I’ve used this website before as an example and I hope he doesn’t mind, but check out leadpress.com as an example.
You’re not running BuddyPress in a sub directory, but actually just stopping it from taking over the root and /blog URLs, and instead using the normal WordPress way of assigning pages.
Rename home.php to community.php.
Use the Page Template method to name that page template “Community.”
In the blog admin, Make a page for your home, a page for your blog, and a page for your community, all with similar slugs.
The community page will use the “Community” page template.
Goto your blog settings and assign the front page to be the page you made for home, and make the index/blog page the one you made for your blog.
Then, you will want to install bbPress in a folder called “/community/forums/” and be sure to create a page with the slug “forums” as a sub page of “community”
That should do it?
Take a look at https://wordpress.org/showcase/ for examples of some of the best sites built on WordPress. WordPress itself is a stable and exciting for building sites and CMSs on, and the showcase which I’ve linked you to will let you browse the highlighted best.
The ‘biggest’ BuddyPress installation – other than this site – that I am aware of, is GigaOM Pro.
I’m not going to sell the idea of using BuddyPress to you but perhaps if you make a short list of the key features and ideas that are essential, and things you would like to have, we can all comment the feasibility.
Actually that CSS code should go in your bphome theme’s CSS file.
Or whatever you are using for your WordPress home theme.
Let’s say you’re using the “bphome” theme.
The CSS snippet should go at the very end of:
/wp-content/themes/bphome/style.css
