I think upgrade isntructions are in the zip file.

As far as the drop down list for usergroups, it's nice and all but surley there is soem way to have it read what groups you have set up on your board. What you did only covers the basics.

Also is it possible for sv1 to upload all the up to date scripts into on proper zip file. There are so many scripts in this thread it's ahrd to know what been changed and what hasn;t. Would an update email be possible to? :)

Great work you guys.

1)yes
2)follow instructions in UpgradeToLatestVersion.txt
3)you need to download this file instructions are within the zip

MySQL errors are sepose to be showen in your browser window when you import the product althrough vbulletin can be configuerd to log all errors this is not enabled by default

i'm taking a wild guess here that you are using an out of date MySQL version ?

people,

I think i found a bug.... in admin_warn.php.Set "Maintain Historical Records?" to no submit the form you'll see a confirmation form choose no there and in here i get a white blank page when i submit the confirmation form that's unexspected behavior

already fixed however i'm getting an annoying empty vbulletin messagebox telling me nothing

We're running MySQL 4.1.15. Any database errors should be sent to my email, but I don't get anything on the import page nor in my email. I just don't know what might be wrong. Executing all the SQL statements manually works fine and creates all the necessary tables and what not, but the hack doesn't seem to use them anyway. Even if I add warning types, the table is empty when looking at it with phpMyAdmin.

It's all very strange.

fixed working as it should now one more problem sorted out :D

you only get emails about database problems if

• $config['Database']['technicalemail'] = "tech@mysite.com";(config.php)
• the setting in vbulletin options (error handeling & logging section) is not set to yes
• you do not use thirdy party hacks that might interfere with this

the problem you are having is verry odd.Your MySQL is not a problem i was wrong there

Yeah I know, I've set up vBulletin to send an email when db errors occur. It's very odd indeed. By the looks of it, everything is fine, until I actually try to warn anybody or access the "warnings by user" statistics page. At least I think it was that page. In those cases, I DO get an email saying things made a booboo. Those errors are the ones I posted before. However, that is all, the rest looks just fine.

Well, if you disregard the fact that warning_types is empty when it quite clearly shouldn't be empty.

wait, those instructons is for vb 3.0.x AWS upgrading. im on 3.5.x now and i want to upgrade from the older version.

those instructions dont explain that to me.

Now, you all understand why I am reluctant to do any work on this?

Gotti is asking a question, and I have no answer. Because I didn't do the initial packaging and because I have no idea how vb 3.5 handles these issues.

Gotti, my answer would be, just follow the installation instructions. It shouldn't harm your tables, so you won't loose any information and the installation script will install the plugins etc. Then all you may have to do manually, is upload the php files.

Delphi, can you post here all the files you have changed so that I can upload them in the hack's area instead of being in every post in here?

Sorry guys, I explained to you in the past, this is NOT easy for me, and I understand your frustration, but there is nothing much I can do.