Advanced Warning System (AWS)

Advanced Warning System Version 3.5.0

The AWS version for vB 3.5 has been released. You can download it and get support in this thread:

https://vborg.vbsupport.ru/showthread.php?p=770032


Advanced Warning System Version 3.4.16 (latest stable release for vB 3.0.x)


LATEST ANNOUNCEMENT

The AWS has its own Premium Forum here at vBulletin.org, so please use that for questions and discussion on this hack.

The Permium Forum is located at :

https://vborg.vbsupport.ru/forumdisplay.php?f=105





This Warning System owes its existence to Zero Tolerance's Warning Hack (https://vborg.vbsupport.ru/showthread.php?t=65336). I liked the idea, so I installed Zero's hack in my forums site. However, as in most cases, I was not fully satisfied with the way it worked, so I started customizing it. Other people in the thread above, asked questions, which I had already answered by my customizing work, so I answered, giving away those parts of the code, that I had modified.

In the long run, I almost hijacked the thread and the hack from Zero, so I guess I owe him an apology. However, the mods I did have compiled a new, more complete warning system, with much more functionality. Several members from that thread, asked if this could be released as a new hack, so after discussing it with Zero, here it is.

What it does? Well, it is a Warning System, which means it allows you (the administrative team of your site, in other words the admins, the supermods and the mods), to define offences, which the members of your forum should NOT commit. But as we all know, there are instances where members do not follow the rules. In that case, this warning system, allows you to issue a warning to the member who commited the offence. The warning has some points associated with it, as well as a period over which it is valid. When a member gathers enough points, he is banned from your forums, for a predefined period of time. That's mostly it, but below, you can find a short list of features:

Full warning system with:

- post- and non-post-related warnings
- hierarchical warning schema
- hidden or real warners
- customizable maximum warning points
- automatically bans members who reached the maximum warning points
- customizable ban days
- customizable ban user group and permanent ban user group
- customizable restore user group, where users are restored after they get unbanned
- customizable option for who can see the warning level of the members
- automatically issued warnings for posts which contain censored words
- automatically issued warnings for private messages which contain censored words
- supports incremental banning periods
- supports multiple warnings for the same post
- warned members are notified either by Private Message or e-mail when they are warned and when one of the warnings they have received is either deleted or expired
- maintains historical listings of issued warnings (even if deleted or expired)
- customizable warning types
- each warning type has predefined warning points associated with it
- each warning type has predefined maturity period, after which it is automatically deleted
- reports for admin, mods and members
- cron job included to automatically remove matured warnings
- uses vBulletin's cron job, to automatically unban banned users
- all options are setable in your AdminCP
- user warning points and number of bans viewable in your AdminCP User Manager.
- statistics show warning per type, warnings per warner, bans per user.
- Allows you to warn a user from your AdminCP/User Manager.
- Large "Warn" sign, in posts which have received a warning, for mods, supermods and admins, to easily distinguish those posts.
- Ability to remove user's avatar, signature or usage of the Private Messaging system, depending on the warning points he has collected.
- Supports non-standard admins, supermods and mods user groups.
- Allows you to save a copy of the warning send to the warned user, in a predefined forum.
- Allows you to issue "Alerts" (warnings without warning points, for first-time offenders)
- Allows you to add private or public notes for a user, either post-specific or not. Notes appear in the postbit, above each user's message.
- etc.

Admitedly, this is not an easy hack to install. It requires 20 new templates and modifications to some existing ones too. It requires five new tables and modifications to some others. It requires several new phrases. I've tried to make the installation, as easy as I could, by automating certain tasks in an automatic installer. The installer will add the new templates for you, add the new tables required and change the existing ones, and will add the required new phrases. You will have to manually edit the existing templates and the php files though. I also included an upgrade script, which will upgrade those who are using Zero Tolerance's warning hack (version 1.5) to this one. An uninstaller is also included, which removes what the installer installs.

Please keep in mind, that this is a very difficult hack to install. For this reason, I strongly recommend that you back up your database before starting the installation. I also suggest that you keep copies of each file and template you edit, so that you can always revert to a previous stable condition. Finally, I strongly suggest that you always run the latest release.

The zip file always contains both the instructions and the files required to install the latest version. If you have installed a previous version and want to upgrade to the latest, there is a text file attached, in the zip with upgrade instructions. Follow them.

In this thread, you will also find a more detailed document describing the features of this hack, as well as a document describing its version evolution.

Also keep in mind that the installer, will add the AWS templates only to your default style. If you want to use them in another one, you may try this Zero Tolerance's hack, which copies the templates to other styles you may have.

Another thing, the installation instructions were written when vB was at release 3.0.3, so you may expect to find some differences, with the latest files and templates. As far as I can tell, I haven't faced any such case, but I post this reservation here, since I do not have the time to recheck all the instructions for compliance with the latest vB release. The hack has been installed and is working fine with the vBulletin version shown at the top of this thread.

Finally, if you are using more than one style, the installer will install the templates only in the default one. If you want to use the rest of your styles, here is a hack, that will do this for you.

This hack can also be integrated with Zero Tolerance's vBChat. However, since I am using a heavily-modified version of vBChat, I haven't included instructions, on how to patch the original vBChat files, in the documentation. If you are interested in having AWS issue automatic warnings when one of your user enters a censored word in a vBChat message, or if you want your moderators to be able to warn a user, who misbehaves in vBChat, please post a thread in this forum and I'll help you through.

This is my first officially released hack, so please don't be to harsh with me, if I broke any rules or made any mistakes. The mods have been tested extensively, both by me and two volunteers (thank you gentlemen), but I am only human.

Closing, let me thank Zero Tolerance, who got me started in this, and who owns a big part of the code of this hack. I definnitely couldn't have done it, without his code.

Special Note
For those who upgrade from Zero Tolerance's hack to my AWS, even though I have included a script which will do some of the work automatically, not everything is done by that script. Read the installation instructions carefully. You have to run the upgrade script first and then do several things manually. If you just run the upgrade script and just upload the files, the AWS will not work properly. If you have any questions, please do not hesitate to post here.

Also, let me add here, that version 3.3.0 wouldn't have been possible without the contribution of Revan.

And a couple of warnings:

PLEASE DOWNLOAD THE LATEST ZIP FILE FROM HERE, BEFORE YOU START INSTALLING THIS HACK. JUST BECAUSE YOU DOWNLOADED IT A COUPLE OF DAYS AGO, THAT DOES NOT MEAN IT IS THE LATEST VERSION. MAKE SURE YOU DOWNLOAD THE ZIP, JUST BEFORE YOU START INSTALLING THIS HACK.


LATEST VERSION

Version 3.4.16 (released Thursday August 25th, 2005 GMT 18:18)

A couple of bugs fixed in this version. One is related to the Notes feature, and it allowed plain users to see the notes entered, if the "Who can view warning points" setting was set to "All".

Features.txt a new version of this file has been uploaded on April 4th2 005 GMT 09:30, which covers the latest additions to the hack. The original Features.txt file hasn't been updated since the first release of this hack, so it was time for an update.

John

[mcyates]

Originally Posted by sv1cec

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

PHP Code:

$install[]="alter table ".TABLE_PREFIX."user add `warning_bans` int(2)", add `warnings` int(5); 


to:

PHP Code:

$install[]="alter table ".TABLE_PREFIX."user add `warning_bans` int(2), add `warnings` int(5); 


Those damn quotes are the problem.

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

Rgds
---------
John

No worries mate your doing a fantastic job.

[sv1cec]

OK folks, as you probably know, I've been working to implement an "Automatic Warning" feature. A member asked for it, and I thought it was a good idea.

Basically, what it does, is it issues a warning, when a user enters censored words in a post. I assume you are aware with the censorship option of vBulletin. Now, it's pretty much ready, and it traps censored words in new threads, new posts (answers to posts), when you edit a post you made, when you send a Private message.

What I want to ask you, is if you can think of any other area, where such an automatic warning will be necessary.

Your ideas would be appreciated.

If I do not hear from you until tomorrow morning (that's in about 8 hours from now), I'll upload Version 2.0 of AWS, as I have it now.

One more thing. Today, even though several of you have posted messages with questions, I haven't received a single notification from vbulletin.org. Did the same thing happened with you too?

Rgds
-----------

John

[Torqued]

Originally Posted by sv1cec

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?

John,

Yes. After adding that column, I am still getting this error when adding a warning to a user:

Database error in vBulletin 3.0.3:

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

mysql error number: 1136

Here's what I have in my "warnings" table:

Field Type Attributes Null Default Extra Action

wid int(15) No auto_increment
warned_user int(15) No 0
warned_by int(15) No 0
warned_time int(15) No 0
warned_reason text No
warned_post int(15) No 0
warned_warning_id int(15) No 0
warned_status char(1) Yes NULL
removed_by int(15) Yes NULL

What am I missing?

No worries on the issues, mate! You're doing a great job! Thanks for all the hard work and for responding to other users' requests for features.

[ptenthus]

Fixed the quotes as you suggested, but am now getting the following when I run upgrade_warn.php:

Parse error: parse error, unexpected ']', expecting T_STRING or T_VARIABLE or T_NUM_STRING in /path/to/my/forum/admincp/upgrade_warn.php on line 187

[sv1cec]

Originally Posted by Torqued

John,

Yes. After adding that column, I am still getting this error when adding a warning to a user:



Here's what I have in my "warnings" table:



What am I missing?

No worries on the issues, mate! You're doing a great job! Thanks for all the hard work and for responding to other users' requests for features.

OK, that explains it, you are missing the removed_date column, at the end of the table.

ALTER TABLE `warnings` ADD `removed_date` int(15)

That's all

Time to go to bed.

--------
John

[Torqued]

Thanks, John. That fixed it.

[Torqued]

John,

Seem I've found another issue:

I added a warning for a user as admin, and then removed that warning.

Whenever I try to add a warning for another post, I get the following message:

An error has occured, the following message has been left below:

This post has already been warned for. You cannot issue another warning for it.

I am getting this on posts that I have not warned this user for before.

I have done some additional testing, and it seems that this only occurs after I have added a non-post related warning. Once the user has a non-post related warning, if I try to add a post-related warning, I get the above error message.

edited again to add:

Even if the non-post related warnings are deleted/inactivated, I still get the above error message. I can only add new post-related warnings after I prune all non-post related warnings for a user.

[Revan]

Originally Posted by sv1cec

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.

Okay, cool. Thanks for replying.

I can see the usefulness of a maturity level, because my members seem to like posting short annoying messages that sometimes aint even on topic
Warning them for each and every post would get them kicked offa the board within a day


About the AutoWarn, how about including autowarn for posting in threads older than [admin set time]? And this only has effect in [admin set forums]?
I know I could install hacks that auto closes threads, but I am having a problem with my users posting in ancient Newbie threads. I dont want ALL old threads to be closed, as sometimes its not bad to revive them, but being welcomed by a dude who just joined after the welcomed member has 200 posts, thats just dumb


//peace

[sv1cec]

Originally Posted by ptenthus

Fixed the quotes as you suggested, but am now getting the following when I run upgrade_warn.php:

Parse error: parse error, unexpected ']', expecting T_STRING or T_VARIABLE or T_NUM_STRING in /path/to/my/forum/admincp/upgrade_warn.php on line 187

Show me that area of the file, there is no ']' in that line. Show me a few lines before and a few after. Maybe you erased something more than just the quotes.

Rgds

[sv1cec]

Originally Posted by Torqued

John,

Seem I've found another issue:

I added a warning for a user as admin, and then removed that warning.

Whenever I try to add a warning for another post, I get the following message:



I am getting this on posts that I have not warned this user for before.

I have done some additional testing, and it seems that this only occurs after I have added a non-post related warning. Once the user has a non-post related warning, if I try to add a post-related warning, I get the above error message.

edited again to add:

Even if the non-post related warnings are deleted/inactivated, I still get the above error message. I can only add new post-related warnings after I prune all non-post related warnings for a user.

Oooops,

This thing is getting too complicated. It's impossible to test every combination!!

OK, easy one. Please find the following line in Warn.php:

PHP Code:

if($_POST['post']=="" || !$_POST['post'] || $_POST['post']<1){
RunError("Invalid Post ID Input");
}

if($postwarnedalready=$DB->query_first("select warned_post from ".TABLE_PREFIX."warnings where warned_post='{$_GET['post']}'") AND $warn_options[multiple_per_post]=="No")
{
RunError("This post has already been warned for. You cannot issue another warning for it.");
} 


Change it to:

PHP Code:

if($_POST['post']=="" || !$_POST['post'] || $_POST['post']<1){
RunError("Invalid Post ID Input");
}

if($postwarnedalready=$DB->query_first("select warned_post from ".TABLE_PREFIX."warnings where warned_post='{$_POST['post']}'") AND $warn_options[multiple_per_post]=="No")
{
RunError("This post has already been warned for. You cannot issue another warning for it.");
} 


Sorry!!!