BuddyPress.org

Ok, thanks for the reply.

Thanks guys, I’ll take a look!

I see the html for the xprofile input fields is in function get_edit_html in bp-xprofile-classes.php:

switch ( $this->type ) {

case 'textbox':

$html .= '<div class="signup-field">';

$html .= '<label class="signup-label" for="field_' . $this->id . '">' . $asterisk . $this->name . ':</label>';

$html .= $this->message . '<input type="text" name="field_' . $this->id . '" id="field_' . $this->id . '" value="' . attribute_escape( $this->data->value ) . '" />';

$html .= '<span class="signup-description">' . $this->desc . '</span>';

$html .= '</div>';

break;

So I guess I could add onkeyup=”copyinput()” there, but then all xprofile fields will get that. Would that mess up the system? The Javascript refers to the fields by ID.

According to Jeff Sayre this method will be deprecated in version 1.1, but I need a temporary solution before I make the switch.

Trying that now…

If so, the display name is still editable via the “Edit Profile” screen (like I stated above). Not sure what would happen if you attempted to change the display name… would it sync up with the usermeta table?

Yes it does, that’s what the original xprofile_sync_wp_profile() already did, although I think you can turn it off in the admin area. Even if you did that, it wouldn’t mess up anything vital.

My main concern was to consistently get a separate first name + last name in the database, because I need them for several other scripts. That only needs to happen on activation.

Also I needed to learn how to use the fullname value in a function so I could autogenerate a username from it.

Re: rearranging the signup page… BP 1.1 will enable you to move fields around on the sign up page. Check out testbp.org as an example of a customized register page.

I need my site done before Labor Day or September 1st really. And the new more versatile template system does not solve any of my other issues.

This function for bp-custom.php adds fullname from xprofile field_1 to wp_usermeta.

function synchro_wp_usermeta($user_id, $password, $meta) {

global $bp, $wpdb;



$fullname = $meta[field_1];

$space = strpos( $fullname, ' ' );



if ( false === $space ) {

$firstname = $fullname;

$lastname = '';

} else {

$firstname = substr( $fullname, 0, $space );

$lastname = trim( substr( $fullname, $space, strlen($fullname) ) );

}



update_usermeta( $user_id, 'nickname', $fullname );

update_usermeta( $user_id, 'first_name', $firstname );

update_usermeta( $user_id, 'last_name', $lastname );



$wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET display_name = %s WHERE ID = %d", $fullname, $user_id ) );

$wpdb->query( $wpdb->prepare( "UPDATE {$wpdb->users} SET user_url = %s WHERE ID = %d", bp_core_get_user_domain( $user_id ), $user_id ) );

}

add_action( 'wpmu_activate_user', 'synchro_wp_usermeta', 10, 3);

It shouldn’t be a big step to make the fullname lowercase, strip the spaces and store it as username.

Make lowercase and strip space looks something like this:

$str = strtolower($str);



$str = str_replace(' ', '', $str);

But does the system even allow changing the username at the wpmu_activate_user stage?

The username is stored in four places in the database:

wp_signups -> user_login

wp_users -> user_login

wp_users -> user_nicename (?!)

wp_users -> user_url (as last part)

Manually changing the username at these points in the database does NOT screw up my system. Login with email address continues to work fine with the same password. The profile page and links function as normal.

That is good news. It means it is possible to simply update the username from this same function.

Now I just have to figure out the PHP and the queries for those four fields. Any pointers apprecriated!

EDIT: Is $user_id a number or the username? That could complicate things…

I assume $user_id is the username. Can I make this a two-stage rocket? First run the synchro_wp_usermeta function and then a separate function to deal with username, synchro_name_username? Put them in a plugin with something like this at the bottom?:

add_action( 'wpmu_activate_user', 'synchro_wp_usermeta', 10, 3);

add_action( 'wpmu_activate_user', 'synchro_name_username');

Would that execute the functions in the right order?

When I do this:

$fullname = $wpdb->get_var("SELECT meta FROM $wpdb->signups");

echo $fullname;

I get the serialized content of the first meta field in wp_signups:

a:8:{s:7:"field_1";s:13:"Julius Caesar";s:18:"xprofile_field_ids";s:2:"1,";s:20:"avatar_image_resized";s:84:"/serverpath/wp-content/blogs.dir/1/files/avatars/0/caesar.jpg";s:21:"avatar_image_original";s:84:"/serverpath/wp-content/blogs.dir/1/files/avatars/0/caesar.jpg";s:6:"public";s:1:"1";s:7:"lang_id";i:1;s:8:"blogname";s:9:"theempire";s:10:"blog_title";s:16:"The Roman Empire";}

The function inserted this crap also into the wp_usermeta fields. Success! (Sort of…)

The bit of data I need is the fullname, the second bit, in this case ‘Julius Caesar’. I’d need the second bit of data from the user with the activation key.

How would I add that to the query?

I’ll first try this:

$fullname = $wpdb->get_var("SELECT meta FROM $wpdb->signups WHERE activation_key = %s", $key);

echo $fullname;

Nothing…

I probably had to add $key as an argument. Trying again after some food…

Sorry about the empty response. I thought I had it and when it didn’t work it screwed up. I edited out my post.

Okay this is the fix I came out with. I created a new group in BP profile called signature and the field name signature too.

In BBpress in the post.php I inserted (note I don’t know PHP, if anyone can shorten this would be appreciated):

<?php if ( bp_has_profile('user_id='.get_post_author_id().'&profile_group_id=XXX') ) : ?>

<?php while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

<?php if ( bp_profile_group_has_fields() ) : ?>

<?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>

<?php if ( bp_field_has_data() ) : ?>

<?php bp_the_profile_field_value() ?>

<?php endif; ?>

<?php endwhile; ?>

<?php endif; ?>

<?php endwhile; ?>

<?php else: ?>

<?php endif;?>

Just replace XXX with your group id #, mine was 3.

What it doesn’t do is toggle between signature, anyone want to try that?

The ideal registration form would look like this:

– fullname

– email address

Both fields would of course be mandatory. Ideally fullname would be checked for two or more parts, but xprofile_sync_wp_profile() can handle one part input and I can live with an occassional missing last name.

I use a jQuery validation script on another form in my site, that I may also be able to use on the registration form. As far I understand it doesn’t interfere with anything on the server side.

Username would be generated behind the scenes from fullname.

Many other member information fields would be optional under edit profile.

If I can figure out how to select fullname from meta in wp_signups, adapting xprofile_sync_wp_profile() shouldn’t be that difficult.

Or are my latest attempts above still nowhere near a solution? If you see the obvious mistakes, please point them out.

Mike Pratt, you’re right, that is one way to do it. Then you have the following fields on your registration form: username, name, first name, last name. That is an excellent solution if your aim is to annoy potential members.

Another option is to use the default “fullname” field for first name and create a second one for last name, but then you’re kinda messing with the system and perhaps causing problems in the future. I have already done this solution in an earlier version. It’s my fallback option.

But why would I have to create custom fields when WordPress already has the first_name and last_name fields in wp_usermeta? And there is even a ready-to-use Buddypress function that synchronizes the fields in wp_usermeta with the fullname in BP.

Unfortunately at the moment that function is only run when the user updates his profile, so it’s completely useless. I’m trying to tweak it and make it useful and introduce to Buddypress the wonders of a first_name, last_name in the database. (Wow, I know…)

Also I’d like to get rid of the username on the form, by autogenerating it from the fullname – make lowercase, take out spaces, store as username. That should be a relatively easy next step once I’ve figured out how to use the fullname input from the registration form in a function.

Also I wasn’t able to get bp tags working in a plugin, where I had no problem pulling first_name and last_name from wp_usermeta, providing they were available…

This should be a really easy plugin for any php coder, but as Jeff Sayre has pointed out, having a somewhat clean, professional user registration in Buddypress is reserved for those well-versed in the codebase or with deep-enough pockets.

@Mariusooms, I need to finish the site before Labor Day, with a related event on September 22nd. When will bp1.0.3 be released?

I’ll figure it out somehow, with or without the help of WordPress insiders.

I had a good feeling about this attempt, but still nothing in wp_usermeta:

function synchro_wp_usermeta($user_id, $password, $meta) {

global $bp, $wpdb;



$field_ids = $meta['xprofile_field_ids'];

$field_ids = explode( ',', $field_ids );



// Loop through each bit of profile data and save it to profile.

for ( $i = 0; $i < count($field_ids); $i++ ) {

if ( empty( $field_ids[$i] ) ) continue;



$field_value = $meta["field_{$field_ids[$i]}"];

}



$fullname = $field_value['field_1'];

$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( 'wpmu_activate_user', 'synchro_wp_usermeta', 10, 3);

This version messes up registration:

function synchro_wp_usermeta($user_id, $password, $meta) {

global $bp_user_signup_meta, $bp, $wpdb;



$fields = BP_XProfile_Field::get_signup_fields();



$field_ids = $meta['xprofile_field_ids'];

$field_ids = explode( ',', $field_ids );



// Loop through each bit of profile data and save it to profile.

for ( $i = 0; $i < count($field_ids); $i++ ) {

if ( empty( $field_ids[$i] ) ) continue;



$field_value = $meta["field_{$field_ids[$i]}"];

}



$fullname = $field_value['field_1'];

$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( 'wpmu_activate_user', 'synchro_wp_usermeta', 10, 3);

Registration goes through as normal. The user gets one email with the activation link. But the page on the link says ‘Your account has already been activated. You can now log in with the account details that were emailed to you.’ No email arrives.

So the above code hijacks activation without doing anything (probably because $bp_user_signup_meta was added). Still nothing in wp_usermeta either.

My problem is getting the $fullname from $meta. I don’t understand the array stuff. I’m basically just guessing.

If there are any php coders out there that can spot any obvious mistakes or can suggest other things to try, please help me out.