Quote:
Originally Posted by sv1cec
Nubian,
Please do not say that the install script does not work, just because it didn't work in your case. I just installed vB 3.0.3 on my test site, from scratch, and did the hack installation. The install script did everything it is supposed to do.
I would appreciate if you can tell me what your problems were, so that I can assist you.
As for your issue with the 'reason' column in the userban table, it just means it is already there. Maybe it was added by another hack, or by your installation attempts, but that column is not there in a new database, and it should be created by the hack.
If you loaded 2.3.5, and want to use 3.0.2 you have to do all the steps described in UpgradeToLatestVersion.txt, from 2.3.5 to 3.0 then to 3.0.1 then to 3.0.2.
Rgds
|
i'm deeply sorry.
i didn't want it to come out like that.
it was the new years liquor talking.

i'm not saying this out of frustration.
i have one hack installed on my board and that's a portal.
the portal did altered a few tables in the db.
if i were to reload a db that i have backed up and run the install_warn.php file it gives me this after the 2nd step:
Database error in vBulletin 3.0.3:
Invalid SQL: INSERT INTO `vb3_warning_options` values ('1','3.0', 'Yes', 'Yes','No','Yes','','0','7','10','8','6','6','8',' 0','Yes','3','0','All','Yes','Yes','No','Yes','Yes ','Yes','15')
mysql error: Column count doesn't match value count at row 1
mysql error number: 1136
prior to running your install_warn.php script there was never a vb3_warning_options table. :ermm: