I've just tried installing the categories addon but run into a problem.
I uploaded all the files into the correct directories and then proceeded to import the product as mentioned in the readme file. this is the error I received:
Code:
Database error in vBulletin 3.7.2:
Invalid SQL:
CREATE TABLE IF NOT EXISTS vault_category
(
entryid INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
title VARCHAR(255) NOT NULL DEFAULT '',
threadid INT(11) UNSIGNED NOT NULL DEFAULT '0',
PRIMARY KEY (entryid)
UNIQUE undupify (threadid, title)
INDEX threadid (threadid)
INDEX title (title)
);
MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'UNIQUE undupify (threadid, title)
INDEX threadid (threadid)
INDEX title (t' at line 7
Error Number : 1064
Request Date : Thursday, August 28th 2008 @ 09:45:52 AM
Error Date : Thursday, August 28th 2008 @ 09:45:52 AM
Script : http://www.bluedragons.co.uk/forums/admin/plugin.php?do=productimport
Referrer : http://www.bluedragons.co.uk/forums/admin/plugin.php?do=productadd
IP Address : xx.xxx.xx.xxx
Username : xxxxxxx
Classname : vB_Database
MySQL Version : 4.1.20-log
Just an FYI -- when I installed the categories module today I had to manually run the query to create the vault_category table. It was not created during the installation. I downloaded the zip file today.
Do you know why? The only thing I found was an extra space in the installcode, but that seems a little obsurd to have been the problem. Also, once installed, Categories will not work unless your vault_link table contains the templateusage column.
I'm getting something that I think is related. I didn't get any errors when installing, but as soon as I try adding a category and saving the article vb bombs telling me the "vault_category" table doesn't exist.
I looked in the product xml and I have the latest version where the missing commas was fixed.
If I grab the sql and run it via phpmyadmin on the vb db it works fine so I'm not sure what's going on.
Apparently I changed something in the XML on 8/31, probably fixing the second iteration of this bug. If you downloaded the product after this time, there should be no more issues with the table.
This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.