That's because you were not running the latest version before version 3.0.

In version 2.3.4, there was a query:

ALTER TABLE `".TABLE_PREFIX."userban` ADD COLUMN `reason` mediumtext

So, now drop the reason you have inserted and add the proper reason, char(3) is not enough.

Rgds

Thank you Sir!

I have to admit, it gave me some headache to implement it, but thanks to a helpful soul here, Dean C, I got it working fine. And yes, I think that it is a cool feature too, it can provide you with so much information, just with the click of a button.

One other thing that the new version has, and which I really like, is that the routines which do the warning and then send the messages, are in one place now. So, if I want to add an automatic warning somewhere else, all I have to do, is call the routines (now they are ... functions), with the proper parameters. That was the reason why you had to remove the large chunk of code from editpost.php, newreply.php, private.php etc. It makes the code so much easier to maintain.

Rgds

I keep getting this error when I try to run the query to update from 2.5 -> 3.0

An error occurred while attempting to execute your query. The following information was returned.
error number: 1103
error desc: Incorrect table name '".TABLE_PREFIX."warning_options'

that worked fine thank you !! allis working now except the automatic pm feature if a user posts something and that post contains censored words (a pm is not sended althrough i enabled this) and i have cencored words defined but that isn't so bad i always can do this myself

happy holidays John !! :smoke:

Something has gone wrong or i missed something.

I had Zero Tolerance warning hack 1.5. So I only followed the instructions from WarningSystemInstallationInstructions.txt and the upgrade_warn.php file ran without any error now though:

• In admincp I have 2 tabs: Warning Systems and the old warning Options.
• Clicking on "View Warning Logs" results in: Could not find phrase 'no_warnings_found'.
• "View Banned users" results in:
  Quote:

  Database error in vBulletin 3.0.3: Invalid SQL: SELECT user.userid, user.username, user.usergroupid AS busergroupid, userban.usergroupid AS ousergroupid, userban.reason AS reason, IF(userban.displaygroupid = 0, userban.usergroupid, userban.displaygroupid) AS odisplaygroupid, bandate, liftdate, adminuser.userid AS adminid, adminuser.username AS adminname FROM user AS user LEFT JOIN userban AS userban ON(userban.userid = user.userid) LEFT JOIN user AS adminuser ON(adminuser.userid = userban.adminid) WHERE user.usergroupid IN(8) ORDER BY userban.liftdate ASC, user.username mysql error: Unknown column 'userban.reason' in 'field list' mysql error number: 1054

• And finally when clicking on "view warnings" inside someones posts I get an empty white screen.

So did i miss anything? or just messed up hardcore and should retry ?

John,

I had v1.3 installed. I ran the uninstaller, and removed the file changes manually. When trying to run the installer for 3.0, I'm getting the following:

Parse error: parse error, unexpected T_STRING in /home/mydomain/public_html/forums/admincp/install_warn.php on line 285

edited to add:

I think I fixed it:

I found this in the install_warn.php file:

and changed it to this:

It looks like the $DB_site->query(" was missing. After making that change, the install_warn.php completed successfully. Just have to do the file/template edits now.

Check if there is a "reason" field in the userban table. If it isn't there look here . That should fix it.

Seems as if there are one ore more templates missing.

Also, in the current .zip file, it looks like the functions_warning.php, install_warn.php, and mod_warn.php are not in the correct directories in the zip file. There are no files in the /uploads/modcp folder in the zip.

edited to add:

John,

I got AWS v3.0 installed and it seems to be working so far... still have to work through testing a few more things..

A question for those using this hack:

What sorts of things are you guys setting up warnings for?

I want to install this tonight, from fresh. Can we have confirmation that the files are correct in he latest zip. Having mod_warn outside the modcp folder seems wrong.