BuddyPress.org

Hey DJ Paul

I noticed that you added bp_core_account_activated hook which should work in most cases, but like I said (in my particular case) I skip over the activation via the buddypress fbconnect plugin. It inserts the user directly.

Maybe there is a way for me to call that activation once the facebook user is authenticated? Do you know of a way to trigger that whole authorization process without actually making the user click on an email?

That way it basicaly works like this

1. User registers with Facebook conenct button

2. Facebook sends back userinfo (via the api) – thats working currently

(and here is where I am fuzzy)

3. Take the fb information and trigger the account activation “automatically” …effectively bypassing the need for a “key”

Or

Is there another hook I can grab onto somewhere in the process beyond bp_core_account_activated that would work only on INITIAL Registration…but still after all globals are loaded (to ensure the messaging will work)

Any ideas?

Thanks again for the help!

Wow thanks…I will try as soon as I get back to the local computer hosting my test dev. What seems to be happening (in short) is that becuase my users use facebook to login/register…it never goes through the “activation” email scenario….and becuase it registers a new user (and activates them) BEFORE those messages_global are set – the send message function fails.

I tried reording the load_plugin order of the core and the message globals so that they would boot before, but once I did that it screwed up other things (like the order they need to be in to boot through the various functions in buddypress)..so I reverted, and have sense been trying to figure out how to maybe Trigger the “activation” silently in the registration process so that the email verification is not necissary.

I will try the new plugin and report back

I’ve searched over there already. Can’t find anything that can be used to disable that email activation.

actually the log out problem is gone now. the only problem i have is that users don’t get the registration/activation email. here are the answers.

1. Which version of WPMU are you running?2.8.4

2. Did you install WPMU as a directory or subdomain install? directory

3. If a directory install, is it in root or in a subdirectory? root

4. Did you upgraded from a previous version of WPMU? If so, from which version? no

5. Was WPMU functioning properly before installing/upgrading BuddyPress? don’t know, i installed both one right after another

6. Which version of BuddyPress (BP) are you running? 1.0.3

7. Did you upgraded from a previous version of BP? If so, from which version? no

8. Do you have any plugins other than BuddyPress installed and activated?

-ajaxed wordpress

-akismet

– all in one seo pack

– contact form 7

– events calendar

– google xml sitemaps

– login with ajax

– more privacy options

– page links to

– register plus

-remove buddypress admin bar

– sociable

-tweetmeme button

– wordpress database backup

-wp postratings

9. Are you using the standard BuddyPress themes or customized themes? customized

10. Have you modified the core files in any way? no

11. Do you have any custom functions in bp-custom.php? no

12. If running bbPress, which version? no

13. Please provide a list of any errors in your server’s log files. how do i check?

Also, I don’t know if this is relevant but hosting is through GoDaddy.

This works:

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

global $bp, $wpdb;



$email = $wpdb->get_var("SELECT user_email FROM $wpdb->users WHERE ID='$user_id'");



$fullname = $meta[field_1];

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



$company = $meta[field_2];



if ( false === $space ) {

$firstname = $fullname;

$lastname = '';

} else {

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

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

}



$firstname = nameize($firstname);

$lastname = nameize($lastname);



...



$wpdb->query("INSERT mailingusers SET users_id='$user_id', group_id='1', signup_date= UNIX_TIMESTAMP(), firstname= '$firstname', lastname= '$lastname', email_address = '$email' ");

$wpdb->query("INSERT mailingcdata SET cdata_id=NULL, user_id='$user_id', cfield_id='1', value='$company'");



}

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

I used it as part of this function. This should work other mailinglist scripts as well, just change the table and field names.

I don’t understand why $user_email didn’t work. I had to pull the user_email from the database. Is there a cleaner way?

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);

??

I’m now trying to add firstname, lastname and email address straight to the database tables of my mailing list. I’ve added the queries to the function I had put together here:

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

global $bp, $wpdb;



...



$wpdb->query("INSERT mailingusers SET users_id='$user_id', group_id='1', signup_date= UNIX_TIMESTAMP(), firstname= '$firstname', lastname= '$lastname', email_address= '$user_email'");

$wpdb->query("INSERT mailingcdata SET cdata_id=NULL, user_id='$user_id', cfield_id='1', value='$company'");



}

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

This mostly works, except the for the email address. $firstname, $lastname and $user_id are all correctly added to the table, but the email_address field stays empty.

Can anyone spot the problem?

How can I “call” the user’s email address upon ‘wpmu_activate_user’?

Adding a $user_email argument only produces missing argument errors. I’m out of guesses…

$current_user->user_email doesn’t work either:

$wpdb->query("INSERT mailingusers SET users_id='$user_id', group_id='1', signup_date= UNIX_TIMESTAMP(), firstname= '$firstname', lastname= '$lastname', email_address= '$current_user->user_email'");

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…

How can you identify the user on wpmu_activate_user? Only by the key from the activation link? How does that work?

Then $bp->loggedin_user->id doesn’t work on activation either, does it?

How is Lance Willet able to use $userid on wpmu_activate_user?

Can I somehow use that to pull up the right meta row from wp_signups and store the values in wp_usermeta with the right user_id?

Or can I use the email address as an identifier?

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.