I just uploaded a new version, with some minor changes.

The report, I've added yesterday, was not correct. In order to show you which members have been warned, it was checking the warning level of the users. However, a user may have a warning level of zero points, and still have received warnings, which have expired or were deleted. So I added another column in the user table, where I keep the number of warnings a user has received and changed the report accordingly. The upgrade is an easy one, two or three things to do.

Rgds
--------
John

thankyou, just updating now

Get an error

ALTER TABLE `user` ADD COLUMN `warnings` int(5) before warning_level

#1064 - 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 'before warning_level' at line 1

Wow, this is getting better by the day! :D
I do however have some questions:

1. The warning sys I use now cumulates warning points until my set value is reached, then it auto bans. With this maturity level system, do I have to set the maturity to insanely high to have cumulating work as it does now, or can it auto ban no matter how long ago it has been since he was warned?
2. Does a member see his own warning level? If no, then I submit it as a feature suggestion :)

Im sorry if these have already been answered before, but 8 pages of replies.... neeh ;)

And @ mcyates: Try running the query without the "column" word. I have never seen this in a SQL query, and I have added fields to the user table before (in fact I did this just north of 3h ago ;))


//peace

that didn't help, i still got the warning, the code it from the latest upgrade so i don't see why its not working:

I upgraded to 1.3 and am getting the following error when trying to warn someone:

Database error in vBulletin 3.0.3:

Invalid SQL: insert into vb3warnings values('','11','1','1101609844','test 1.3','464','1','A','','')
mysql error: Column count doesn't match value count at row 1

mysql error number: 1136

I am also getting this error when trying to upgrade to 1.3.1

Ok. I fixed the above by running the following:

I looked @ the table structure and the new column should be inserted between `salt` and `warning_level`. I took a peek @ the ALTER TABLE documentation and didn't see a BEFORE parameter, but did see an AFTER parameter, so decided to try that.

http://dev.mysql.com/doc/mysql/en/ALTER_TABLE.html

I have ZT's warn hack (1.5) and get the following error when I run the admincp/upgrade_warn.php script:

Any idea what is wrong?

Also, I downloaded the code last night (November 27th, 2004)...

1. BEFORE and AFTER parameter in SQL.

I would swear I used before, but I may be wrong. I'll change the documentation.

2. Revan's question. Two different things here, the maturity is the number of days that the points stay in a user's account. It doesn't pay to warn a user for a minor thing (maybe one point) and keep that warning point for ever. If you do not want that to happen, yes, you need to set the maturity of the warnings to something like 99999.

Yes, a member sees a link, which shows him his own warnings.

3. Torqued. If the column hasn't been added because of the mistake that mcyates reported, and which you were also getting, it's normal to receive an incorrect columns error. Now that you added the column, does it still produces that error?

4. Ptenthus, change that line (185) from

to:

Those damn quotes are the problem.

OK folks, sorry for these issues, I am trying my best.

Rgds
---------
John