[noppid]

After upgrading to 3.0.2 it seems that the tables for setting and settinggroup were recreated. At least the vbgarage options were no longer in them.

Here's how we enabled it again.

Backup your DataBase First!

edit init.php to this...

PHP Code:

    // Reputation

    'canseeownrep'             => 256,
    'canuserep'                => 524288,
    'canhiderep'               => 1048576,
    'cannegativerep'           => 2097152,
    'canseeothersrep'          => 4194304,
    'canhaverepleft'           => 8388608,
    // START VBGARAGE HACK
    'canvbgarage'              => 16777216
    // END VBGARAGE HACK    
); 


This leaves the vB options in their correct places.

Next run these five queries to repair the vbulletin option menu. We did it in phpmyadmin and do not have table prefixes, if you have table prefixes you must edit the table names.

[sql]
INSERT INTO settinggroup (grouptitle, displayorder, volatile) VALUES ('vbgarage', '650', 1);

INSERT INTO setting (varname, grouptitle, value, defaultvalue, optioncode, displayorder, advanced, volatile) VALUES('vbgenable', 'vbgarage', '1', '1', 'yesno', 10, 0, 1);

INSERT INTO setting (varname, grouptitle, value, defaultvalue, optioncode, displayorder, advanced, volatile) VALUES('vbgcomments', 'vbgarage', '1', '1', 'yesno', 20, 0, 1);

INSERT INTO setting (varname, grouptitle, value, defaultvalue, optioncode, displayorder, advanced, volatile) VALUES('vbgmaxupload', 'vbgarage', '6', '6', '', 30, 0, 1);

INSERT INTO setting (varname, grouptitle, value, defaultvalue, optioncode, displayorder, advanced, volatile) VALUES('vbgmaxfilesize', 'vbgarage', '200000', '200000', '', 40, 0, 1);

[/sql]

All of the queries are from the install script.

Good Luck.