Closed (fixed)
Project:
Drupal vB
Version:
5.x-2.0-beta1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Apr 2008 at 21:30 UTC
Updated:
8 May 2008 at 04:05 UTC
Jump to comment: Most recent file
Comments
Comment #1
sgdev commentedI said vb_thread and vb_datastore "files" above, but what I meant is database tables.
Comment #2
sgdev commentedAh ok a bit more research shows that this isn't about the install file, rather the code is pointing to the Drupal DB when it should be pointing to the forums. Changing the title accordingly.
FYI, my configuration has no table prefix. In config.php I have the following:
$config['Database']['tableprefix'] = '';Comment #3
sunThis should not happen. Did you setup your database connection for vBulletin in DrupalvB's settings page after upgrading?
Comment #4
sgdev commentedI just looked at Home > Administer > Site configuration > Drupal vB Integration, and selected the database tab. The database connection is set as follows:
Host: localhost
Database: forum
Username: XXXXX (our user name)
Password: XXXXXXXXX (our password)
Table prefix: vb_
The first four fields are correct, but why is table prefix a required field? We are not using any table prefixes for our forums database. I should be able to have this blank but I cannot.
Comment #5
sgdev commentedAlso very strange, if I look at the integration tab in Drupal vB Integration, it seems like the module doesn't even recognize where the forums are located. In 5.x-1.x, I could hover over "View the Forum" and the other links, and it would give me the right location. Now the word "forums" is completely missing from the URL. For example: "http://localhost/web//admincp" (should be "forums" in between the two slashes)
All I did was copy over the config.php file I was using for 5.x-1.x, so should be no issue with that.
Comment #6
sunok. First shot (the easy one). After applying this patch, you should be able to re-submit your database connection settings.
Comment #7
sgdev commentedSometimes the right fix is the easy one. After clearing out "vb_" and saving, all errors have gone away. :) I will continue with my testing.
Comment #8
sunThanks, committed.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.