Forum Replies Created
-
Thanks Nicola Greco!
I knew there had to be a better solution, something like this, but couldn’t put it together.
So I replaced that database line with this:
$uid = get_userdata($user_id);
$email = $uid->user_email;Works fine.
I can live with in this case, but let us know if you have a better solution.
Trying to use Manoj Kumar’s Buddypress Users Import plugin. I get this error:
Fatal error: Maximum execution time of 30 seconds exceeded in /serverpath/wp-includes/class-phpass.php on line 60
I don’t recognize anything in that line:
function get_random_bytes($count)
{
$output = '';
if (($fh = @fopen('/dev/urandom', 'rb'))) {
$output = fread($fh, $count);
fclose($fh);
}Can I just temporarily delete it? Would that solve the problem? Other solutions?
I’m trying to import 600+ members, so I’m not surprised it times out.
EDIT: 490 members were actually imported quite nicely!
EDIT2: Not as nicely as I first thought… Username and full name didn’t make it over, only email addresses. Should I have added labels to the top line?
EDIT3: There is no fast way to delete 490 users…?
EDIT4: Does this plugin also update firstname + username in wp_usermeta. If not, I have to add it.
Thanks Treblamah!
Wow, that is horribly unusable again…
This spits out all the xprofile data:
<?php bp_get_profile_header() ?>
<?php bp_the_avatar() ?>
<?php if ( function_exists('xprofile_get_profile') ) : ?>
<?php xprofile_get_profile() ?>
<?php else : ?>
<?php bp_core_get_wp_profile() ?>
<?php endif; ?>And I guess I have to add parameters to make it more selective. Or copy that xprofile_get_profile function and customize it.
I’ll look into that later…
Even this doesn’t work:
$email = $wpdb->query("SELECT user_email FROM $wpdb->signups WHERE activation_key = %s", $key);And this also does not work:
$email = $wpdb->query("SELECT user_email FROM $wpdb->users WHERE ID = %s", $user_id);??
To autogenerate a temporary username put this function in bp-custom.php:
function randomusername() {
$length = 10; //length of string
$start = 65; //Where to start from on ascii table
$end = 90; //where to end on the table
for ($k = 0; $k < $length; $k++){
$randomname .= strtolower(chr(round(rand($start, $end))));
}
return $randomname;
}Make this edit to the username input field on the form (hacking core file, should become easier in version 1.1):
<input name="user_name" type="text" id="user_name" value="'.$user_name = randomusername().'" maxlength="50" />Test it if you want; you’ll see a random string in the username field that will be replace by the autogenerated username based on fullname on activation.
You can hide the username field on the signup form, without getting error messages for not giving it proper TLC, by using this CSS trick.
That requires another core file hack, since you need to add a id like username-form-field. Again, should become easier in version 1.1.
My registration form is now:
Name:
Email address:
And that’s it! Everything works. Full name is available as first and/or last name. The URL is the full name lower case without spaces.
Only thing left to do is clean up the email messages etc. that still mention the username…
Temporary solution how to customize registration form until 1.1 arrives, FYI and my own reference:
Changed this line in function bp_show_register_page() in functions.php in my template:
require ( BP_PLUGIN_DIR . '/bp-core/bp-core-signup.php' );to
require ( 'custom-signup.php' );Copied bp-core-signup.php to the template folder, renamed to custom-signup.php.
Go customize!
Unfortunately the custom fields are generated by yet another core function:
do_action( 'signup_extra_fields', $errors );This action is associated with the function xprofile_add_signup_fields in bp-xprofile/bp-xprofile-signup.php.
Copied the function to bp-custom.php, renamed action and function to custom_signup_extra_fields and custom_xprofile_add_signup_fields.
Used this CSS trick to hide the avatar upload. Will use the same trick to hide the username field.
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?
