vB3] 2 Forums, 1 User DB... possible?
 

2 Seperate forums, site.com/forum1 and site.com/forum2 -- same login on each forum. has this be done?

I was never quite able to get this to work with VB2. It is very easy to do with phpBB, but i would rather go with vB3 then PHPBB.

I realize I would still need two BB licenses.

But is this at all easy?

with vb3 it's not that hard to achieve as long as both forums are on the same DB, just different by the tableprefix.

but there could appear some problems if you are not really really carefull... (usergrouppermissions and such)

addition: if you just want the same login, that's not that hard, as you can just insert the user into both db's when registring on one forum, but if you want to share the userprofile at all, then it would becoming the difficult way i mentioned :)

Why not just have three db's. One central user database containing the user, userprofile tables etc and then another two for the rest (e.g. forums, settings, templates etc). Then have all 3 database all on the same username and password. Then do a long-haul search and replace within the file replacing all references to the " . TABLE_PREFIX ."user table for example with nameofuserdb." . TABLE_PREFIX . "user

That'd be quite easy to do :)

right id want to share profile and such,

bother sites are on same server, so ya they could use same DB.

phpbb has a constants.php file that contains a list of all the table names... so you can just hard code the table prefix for specific tables (user table) to be the same...

your saying we could do this with vB3, where does vB3 define all the table names, or are they spread through the code?

ah ok dean, so i guess you answered my last question. search and replace. hmm. sketchy...... but whattya gonna do i guess :)

but your idea is good, better then all sites on 1 db with diff table prefixes.

Wow phpbb does that - that's a great idea :) The tablenames are hardcoded but I genuinely think this'd be a good idea to do in later versions of vB3. I suggest you suggest this as a feature suggestion. I was going to suggest a way to do this in not so many lines within config.php. However I'm not sure if php's capabilities would allow this.

Basically for all those that may know I was thinking that perhaps you could write some ifs and regexp's to check the instance of where the constant is being used. For example if the follow characters until the next gap of TABLE_PREFIX was user then replace it with something. I don't know if this is possible.

Dean, that's exactly the way i mentioned above.
with that way you can produce some real problems if you are not carefully when creating new usergroups and such

Note: to do this you would need two licenses as effectively you'd be running two forums :)

course. the boards are already all online and licensed for VBB. yet another reason id rather not go to phpBB

could you not just move the usergroups table into the `user-db` ?

what types of problems you have in mind?

yea its kinda neat. http://www.phpbb.com/kb/article.php?article_id=55

i will suggest it for vb. very handy.


as for adding db prefix to sql queries in vB code... easy nuff to do with text editor. rather find and replace by hand anyway just to make sure im not flubbin nothing.


just looking at the vB3 DB schema it could be quite a challenge figuring out what tables exactly to seperate... hmm.


would this also work for vB2 do you imagine?

Well I kind of just did a practice of how this would work.

Assuming you had a table prefix (WILL NOT WORK WITHOUT A TABLE PREFIX :)!) you add this within db_mysql.php:

Below:

Now don't actually do this - This is just to illustrate how you could use it. You'd replace the a with the name of the database and a period and it'll work. The problem comes with the key fields like userid, usergroupid. Just a though for people thinking about doing this though :)

hmm. if both sites have the same user groups tho, this would not be a problem correct?

what lines of db_mysql are you adding these snippets?

It was just pseudo code not to actually be implemented. It was just to show the possibilities of how it could be done :)