Database Errors after upgrade to vBulletin 3.6.7

[rcwild]

When upgrading vBulleting to 3.6.7 is there something I should have done to upgrade PhotoPost, too?

Our forum was up and running after the upgrade, but generating thousands of email error messages. Our server asked us to shut down the forums and gallery until we solve the problem.

Here is a typical error message:

Database error in vBulletin :

Invalid SQL:

SELECT *
FROM sd_datastore
WHERE title IN ('','options','bitfields','attachmentcache','forumcache','usergroupcache','stylecache','languagecache','products','pluginlist','cron','profilefield');

MySQL Error : Table 'content.sd_datastore' doesn't exist
Error Number : 1146
Date : Tuesday, July 10th 2007 @ 01:42:46 PM
Script : ../gallery/showphoto.php/photo/88/si/da
Referrer :
IP Address :
Username :
Classname : vb_database

Note: I truncated the script URL and deleted the IP address.

[Chuck S]

Well thats a vb specific error that has nothing to do with a photopost query or script.

We dont send out errors like that

[rcwild]

So ...

vBulletin says it's a PhotoPost problem (referencing the ../showphoto.php script) and there's nothing they can do about it.

PhotoPost says its a vBulletin problem and there's nothing they can do about it.

In the meantime, I have a forum and a gallery with over 3100 registered users that is down.

[Chuck S]

That is not a query from Photopost or a Photopost database table so please enlighten me on how this is a problem with our program here.

I am can appreciate you being upset about something not working but based on what I am seeing with your error that query comes from vbulletin not us. That error is even in a vb format they should know this. It is not a photopost message.

My suggestion is try disabling any hacks in vb and see if the problem persists. I can show many working examples of vb3 and Photopost

[rcwild]

Our PhotoPost gallery was working perfectly until we upgraded to vBulletin 3.6.7. I had no complaints about either PhotoPost or vBulletin.

We have a problem now. I'm not a programmer, but if I get good direction I can usually figure things out. Here's the most recent response from vBulletin:

I know this is probably a waste of time but let me reiterate. Look at that error:

Script : ../gallery/showphoto.php/

That is NOT from vB. That is because there is NO file named 'showphoto.php' in vB. That error is from your add-on.

As I said, you will not get this error with the default vB code and blaming me for pointing that out is not going to solve this problem. This is due to your add-on, NOT vB.

This came in response to me pointing out that the guys over at PhotoPost are sure it is a vBulletin issue. Yes, I'm getting frustrated.

[Chuck S]

Listen I am trying to push blame here and sure that says the error is happening over photopost for whatever reason thats fine. The one single point I have made here which is unmistakable here is the error itself the query the mail sent out to you is all vbulletin it does not have a single thing to do with photopost

Content visible to verified customers only.

We dont have a datastore table in Photopost so how can this be a Photopost error? Thats what this really comes down to. Have you disabled hacks? Does the error give you any ideas why that table does not exist?

Why is your forum table sd_datastore table not found in the database content. I assume here your telling Photopost your forum uses a table prefix of sd_ and vb 3.67 definately has a datastore table. So since you know alot more about your server and what settings are right or wrong why do you get this error? Is the database wrong? Have you entered the wrong vbulletin table prefix?

[rcwild]

I only posted here because the vBulletin guys told me they were absolutely sure the problem is due to my PhotoPost add-on. I had to ask if there was something I needed to do with PhotoPost when I upgraded vBulletin.

Like I said, I'm not a programmer, but I believe that it is a vBulletin issue, not a PhotoPost issue. Simple logic. I had no problems until I upgraded vBulletin. I voiced my frustration here, but I'm not pointing blame at PhotoPost. I'm quite satisfied with your response and will continue to look at vBulletin for the source of the problem.

Thank you for your time.

[Chuck S]

Now as I stated I gave you several things to check as to what might cause your vbulletin error. That should help you track it down.

Does the database or table prefix or anything I pointed out above give you any hints to your error?