Import from Vbulletin

[pdblizzard]

We were runninng a subscription hack on a vbulletin member board and have about a 1000 users (not all paid users.)

I ran a join query to get the user information I needed from 3 different tables in Vbulletin for the import to S2Member/Wordpress.

But is there any way to convert the passwords that are stored encrypted?

I'd like to be able to make the conversion process seemless for the existing subscribers, and not force them to change their password again.

Any help with this Unix/PHP/MySQL question would be greatly appreciated!

[Jason Caldwell]

With s2Member Pro, you'll have a very advanced Import/Export tool that can handle the importation of Users/Members, even with new passwords. Supporting basic fields, and also extended fields, including:

Code: Select all

"ID", "Username", "Password", "First Name", "Last Name", "Display Name", "Email", "Website", "Level[0-4] or Role ID", "Custom Capabilities", "Registration Date ( mm/dd/yyyy )", "Last Payment Date ( mm/dd/yyyy )", "Auto-EOT Date ( mm/dd/yyyy )", "PayPal® Custom String", "PayPal® Subscr. ID", "Custom Field1 Name", "Custom Field1 Value", "Custom Field2 Name", "Custom Field2 Value", ...

That being said, you MUST have the actual password, not the encrypted version. WordPress® uses a Salt of it's own in the hash it uses to verify passwords. What you CAN do, is build in a Filter for vBulletin style passwords. You can add a Filter to WordPress. Something like this:

Code: Select all

add_filter("check_password", "check_vbulletin_style_passwords", 10, 4);
function check_vbulletin_style_passwords($check, $password, $hash, $user_id)
{
    $check = the current result of the check: true|false
    $password = the plain text password entered by a User during login.
    $hash = the hash that WordPress uses.
    $user_id = the WordPress user ID of the account.
   
    So you could test $password against a vBulletin style hash here, and return true if it matches, otherwise, just return the default $check value.
}

This would give WordPress compatiblity with vBulletin style password hashes. I'm not a vBulletin guy, so someone who is familar with vBulletin will need to fill in the blanks here in this code snippet.

[Jason Caldwell]

@NP/TODO
Add an option to the s2Member Pro import routine
that supports the importation of pre-encrypted passwords.

[pdblizzard]

Thanks, I'll give the filter a whirl.

Another export/import question: Is it absolutely necessary to bring over the "PayPal® Subscr. ID"? I'm hoping "no", because it's burried in field with some other data in the Vbulletin payment transaction log.

[Jason Caldwell]

Nope. That's optional.

The required fields are:

Code: Select all

"ID", "Username", "Password", "First Name", "Last Name", "Display Name", "Email"

Even here, the ID field is optional, Display Name is optional, and so is the Password field.

To clarify. If you leave the "Password" field empty, s2Member will auto-generate a random Password during import instead. The ID field should ONLY be used, if it is your intention to update an existing account with new information, matching an existing ID in the WordPress database.

So, the absolute minimum is:

Code: Select all

"", "Username", "", "First Name", "Last Name", "", "Email"

NOTE: These instructions are valid only for the s2Member Pro Module. The Import/Export feature is not available in the free version of s2Member. ~Thanks.

[Jason Caldwell]

@NOT POSSIBLE/TODO
Add an option to the s2Member Pro import routine
that supports the importation of pre-encrypted passwords.

We took another look at this before the release of s2Member v3.2. This does not appear to be possible. Password encryption from one system to another varies greatly. The hash algorithms used from vBulletin, or any other software package, as compared to the one used by each unique installation of WordPress, creates an issue that is not easily resolved.

So instead, I'm going to create another TODO item.

@TODO - Add Import routine option that allows a site owner to email all imported Users with a custom message, which would include the new password generated by WordPress upon import.

Resolved/ in favor of this solution:
viewtopic.php?f=4&t=1163&p=9032#p9032