Make vbulletin use another table for users

[Lurk]

that doc gonna be posted here?

[Zachery]

Originally Posted by Lurk

that doc gonna be posted here?

I dunno lurk, its still alot of work, and you gaveup after 20 seconds

[Lurk]

lol , i wanna try it though. I'm going to try it if i got a doc to help me out

[Lurk]

So, Zachery, i hope you don't mind me asking this, but can you either post the doc here or send me a pm?

[nicholas]

Zachery, please post either the doc or your modified version. I'm interested in this and I'm sure a LOT of others are as well.

[Lurk]

yeah

[Lurk]

Zachery, you gonna release it?? I really wanna try it

in includes/db_mysql.php
FIND:

PHP Code:

    function query($query_string, $query_type = 'mysql_query')
    {
        global $query_count, $querytime; 


JUST AFTER, ADD:

PHP Code:

        global $yournewdatabase, $yournewprefix;
        $query_string = ereg_replace( TABLE_PREFIX."user ", $yournewdatabase.".".$yournewprefix."user ", $query_string); 


$yournewdatabase = you share your users in a single database, so you need to switch from the vB database this forum use, to the one you want to share.

$yournewprefix = your new database have a different prefix i suppose... change it there...

you can add these new variables to your config.php file... but have to be added or the script is useless.

also, this hack is for sharing between different vB, and have not been tested for other purposes... and i will not release it, because you really have to own 2 different licenses to be able to deal with it - or it's illegal!

this can become a official hack btw!

[Andreas]

I think, except the legal issues, there are several problems:

• post counter
• last activity
• used style
• PMs
• reputation
• usergroup membership

Id' like to know how this problems can be avoided/fixed?

for this list, just make the exact same change as for the user table... tables are precisely identified, so it's not a problem... the friend just asked for the users table, not the entire system...

some will tell this change make some overhead, but when you want to share your stuff like that, you have to deal with some problems... you can make a global change around the script and make it impossible to update later, or make this little quicky that will enable you a complete merge of users without changing more of the script...

i've done the same change for hivemail to use my own vb table instead of the regular vb integration ... job is cool!