The username field is a mandatory WPMU field. It is used by WPMU as the “user_login” field of the wp_users table. It is the necessary piece of datum that is used when a user logs in.
BuddyPress has its own mandatory registration field that by default is called “Full Name”. Look in the BuddyPress submenu group in WPMU’s backend. Go to “BuddyPress > General Settings > Full Name field name”.
You can change the “Full Name” field name to display whatever you want but you cannot remove that field from the registration page nor edit it to be something other than a single textbox field–at least not without hacking the core. Look under the “Basic” field grouping in “BuddyPress > Profile Field Setup” to see what I mean.
In fact, for testbp.org, Andy did change the outputted name of that field to simply read “Name”.
It is this BuddyPress field that is used to display the user’s name. If fact, this field can be edited by the user when they visit their profile and navigate “Profile > Edit Profile”. On the other hand, the username field, which is a WPMU field, cannot be edited.
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/
Are you using a custom theme? Have you added any required fields via the “BuddyPress > Profile Fields Setup” in WPMU’s backend?
By default, WPMU with BuddyPress installed is setup to do exactly what you are asking–have one “Username” field and one “Name” field on the signup page.
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
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?
Yes. I used bphome and bdmember theme from BuddyPress 1.0.3 package. (I delete old one and upload new)
Here is my instalation for test purposes:
http://loger.outsider.pl/
Maybe it will help to sole my problem.
I know that problem is have to be on server side. I was installing BP at my local Wamp instalation and at Zeus Web serwer. – Works fine
Here is phpinfo http://loger.outsider.pl/phpinfo.php
Don’t run a public site on trunk? I mean, I have a local development installation of trunk but to run that publicly…
The most recent trunk entirely changes the way the forums component is integrated into BuddyPress, which is why you are getting these problems.
Okay, I found an easier way for this.
Instead of creating a new stylesheet, you can use your existing admin bar CSS, but define some new rules for just the WPMU admin area.
Use this as your CSS selector:
body.wp-admin #wp-admin-bar {ENTER YOUR STYLES HERE}
Remember to define the body.wp-admin selector for each BuddyBar element you want to style.
eg.
body.wp-admin #wp-admin-bar {
background:yellow !important;}
body.wp-admin #wp-admin-bar li * {
font:12px normal georgia,times,serif !important;
}
This will change the BuddyBar background colour to yellow and the font to a serif for the WPMU admin area.
Hope that helps!
I’ve recently started doing this for the purpose of renaming a few of the predefined labels as well.
I use PoEdit and followed the instructions listed here:
https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/
The “Labels and Messages” section is what you want to read up on.
Follow them explicitly and you should be good to go.
You’ll probably want to find a PoEdit tutorial on Google as well.
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.
You’d have to define a separate stylesheet for the admin BuddyBar, and hook it into the admin_head.
You can start work on that separate stylesheet, after you’ve done that I can help you hook it in the admin area.
i am using that plugin in http://yerleske.net/pano/
i want to use user’s avatars in forum pages too.. i tho its possible because we are calling buddypress with this plugin right?
Updates and fixes are coming, but I need to finish some things for 1.1 before I can do them.
Hey unsalkorkmaz,
Submit a ticket (login with the same username and password as on buddypress.org) noting the problem and one of the BP devs will look to see if your problem can be duplicated.
The “Favorite Topics” functionality was broken when the BuddyPress forums changed the permalink structure from ID to pretty permalinks (I’m speculating, but I think I’m right).
The groups hyperlink is a known bug as well.
Maybe this problem is also connected with this:
https://buddypress.org/forums/topic/sigh-integration-cookie-problem-for-all-users-except-admin
since you have a capital letter in your username and groups are connected with bbpress
I am not sure though
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?
Hi fangonk,
If you scrolled a little bit down, you would have seen this thread!
https://buddypress.org/forums/topic/remove-image-upload-option-from-signup-only
It’s a simple fix that uses CSS to hide the avatar fields on the registration page.
Ok, I don’t know if this helps, but when I had wpmu 2.7.1 and used bbpress-integration plugin, I had to add
define( 'COOKIEHASH', '####################' );
define( 'COOKIE_DOMAIN', '.yourdomain.org' );
define( 'SITECOOKIEPATH', '/' );
define( 'COOKIEPATH', '/' );
to the wp-config.php file and
define( 'WP_AUTH_COOKIE_VERSION', 1 );
to the bb-config.php file
After upgarding to wpmu 2.8.1, I read here that I had to delete the line I added to the bb-config.php file. Could that be the problem???
