![]() |
Attachment Mysql Errors
Hello,
I think this problem is unique, I haven't found this exact error here or in Google. So I can upload attachments to my board, they show up in the Attachment Manager, but when I go to view the post, I get a mysql error: PHP Code:
|
FWIW I ran the same query on my own unmodified test 3.6.8 and I got the same error. Have you installed any hacks that have done anything to the attachments table?
Could this be caused by a bad hack UNinstall? |
I've got 3.6.8 on my test site and I have no field called extratype in the attachment table. I then did a search in all my files in my test site and found no reference to the field 'extratype'. I would look at any hacks you may have installed.
|
Thanks for the replies. The only hacks I installed were hacks I used a few weeks ago without incident. It's odd too that I don't have EXTRATYPES anywhere in my sql or templates.
I actually installed Vbul clean, no addons, no hacks, and the problem still persists. It must be something with my host I'm guessing. |
Quote:
|
I fixed it, I think*
I simply added a an extra row in ATTACHMENTS in the sql and instantly, the error went away, thumbnails are being viewed, shalala, lalalala. Isn't it odd that both a clean install of Vbulletin with a fresh database would have the same problem? The problem being that a single yet necessary row was not created in the database during install? Doesn't everyone else have this EXTRATYPE in their ATTACHMENTS table? |
First of all, vBulletin uses a table named "attachment", not "attachmentS".
Second the column "extratype" is not a default vBulletin column. By adding it you only have worked around the symptoms but you did not solve the problem. Even though you claim that you have no modifications, this really can only be caused by a modification that is still installed. |
As Marco said, there is no field named "extratype" in the attachment table by default. You have a query somewhere that is looking for it though. If you already looked through all your files, then you need to look through your products. You didn't post the complete error in your first post because it would have said what page is making that query. You can look in your error_logs and probably find out what line the query is getting called on and if it's a hook location, then you just need to look through your products for anything that uses that hook.
|
All times are GMT. The time now is 02:16 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|