Trying to use this module and it would appear to work correctly, but my issue is that there are two databases (vB and Drupal 6) where vB's tables are without prefix and Drupals include a prefix. A single login to the vB installation and a separate login for the Drupal installation.

In a nutshell, the module only allows for a single user login and is limited by a matching or non-existent prefix. Has this been changed in the DEV build or do we need to wait for a patch for this type of integration?

Also, please add a README to somewhere OTHER than the DEV build. Thanks!!!

Comments

z33k3r’s picture

z33k3r commented

I just realized that my title was over zealous. My appologies. There is the prefix option under the advanced fieldset. This again goes back to the issue of both databases needing matching prefixes...

liam mcdermott’s picture

liam mcdermott commented
Priority: Critical » Normal
Status: Active » Closed (won't fix)

The table prefix in the vBtoDrupal settings relates to the vBulletin table prefix. The Drupal table prefix doesn't need to be set, since we already know what it is from Drupal's settings. :)

The README will end up in the next stable version, but there are some bugs I'd like to iron out before creating it. Sorry for the inconvenience.

Unfortunately, I'm pretty sure it's impossible to use two logins without re-engineering the whole module and -- in the process -- making it 100's of times slower. So this is a won't fix, although it is quite a frequently asked question, so I should find a way of communicating this information to people in the README.

Thanks for taking the time to raise this issue! :)

hixster’s picture

hixster commented

there's a challenge using this module when running on Plesk in that (without shell access) you can't have a single user access multiple databases, which is kind of ridiculous.