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

[pfdc]

Originally Posted by sv1cec

Just make sure that all the changes in banning.php are made correctly. You must have made a mistake there, somewhere.

I think I did everything right. here is my banning.php file



any help will be appreciated.

[Zachery]

Never, ever post your vBulletin files at this site or any other, you are breaking the rules of this site as well as the vBulletin License agreement.

Please refrain from doing so again.

[sv1cec]

Originally Posted by Delphiprogrammi

sv1cec,

Slightly offtopic question but i'm gonna ask anyway :ermm: if a member is banned and he trys to login he just get's the "no permission" page not mentioning he's banned i'd like to change that to something "you have have been banned for $time" etc etc you have any idea what phrase i need to edit ?

$vbphrase[nopermission_loggedin] <<-- this one will help

rgds

I do not think you should change that phrase. This phrase is used for a special purpose, to tell the user that he used a wrong password or that he visited a page he is not permitted to. What we need to find, is where the ban check is done and change something there. I spend some time trying to figure out, where the ban condition is checked, but couldn't figure it out. I'll look again for that in the morning, 'cause it's 23:00 over here, and I need some rest.

Keep your fingers crossed.

[sv1cec]

Originally Posted by pfdc

I think I did everything right. here is my banning.php file



any help will be appreciated.

The changes I make in the banning.php file, are just to add an extra field in the banning form and the userban table of course. It has no real connection to AWS, so restore your original banning.php file and see if it works OK. If it does, then try making the changes again, but with a little more attention.

Rgds

[Delphiprogrammi]

Originally Posted by sv1cec

I do not think you should change that phrase. This phrase is used for a special purpose, to tell the user that he used a wrong password or that he visited a page he is not permitted to. What we need to find, is where the ban check is done and change something there. I spend some time trying to figure out, where the ban condition is checked, but couldn't figure it out. I'll look again for that in the morning, 'cause it's 23:00 over here, and I need some rest.

Keep your fingers crossed.

offcourse sv1cec we all need some rest now and then no hurry in it really just thought it would be nice to tell a user he/she is banned and that's the reason he/she can't view anything not the "privileges" thingy

i keep my fingers crossed :nervous:

i'll have a look myself to

[Delphiprogrammi]

Originally Posted by pfdc

I think I did everything right. here is my banning.php file



any help will be appreciated.

i've had a problem to editing that file allot of parse errors however i got around it by editing the database querys manually just look at you do not forgot anything like quotes or { } ( ) ; and stuff like that i would give you my working banning.php file but according to this site rules and the vbulletin licence i'm not allowed todo that just edit the file with care and always have an orginal banning.php on a safe please just in case

[pfdc]

Originally Posted by Zachery

Never, ever post your vBulletin files at this site or any other, you are breaking the rules of this site as well as the vBulletin License agreement.

Please refrain from doing so again.

I am very very sorry as I didnt know this rule. It will never happen again.

[pfdc]

I uploaded my old file and its working again. Does this in any ways limit the Warning system's capabilities?

Thanks for your help.

Originally Posted by sv1cec

The changes I make in the banning.php file, are just to add an extra field in the banning form and the userban table of course. It has no real connection to AWS, so restore your original banning.php file and see if it works OK. If it does, then try making the changes again, but with a little more attention.

Rgds

[sv1cec]

Originally Posted by Delphiprogrammi

offcourse sv1cec we all need some rest now and then no hurry in it really just thought it would be nice to tell a user he/she is banned and that's the reason he/she can't view anything not the "privileges" thingy

i keep my fingers crossed :nervous:

i'll have a look myself to

Good morning to all,

although it is definitely not the same, why don't you enable the "e-mail on ban" feature? In that way, when the user is banned, he gets an e-mail and he knows. (I know, I know, I'll look into it, it's just that I haven't have my coffee yet).

Rgds ;-)

[Widok]

Has installed, has created a rule with "Automatic Warnings".
Has written the message with ObsceneWords, I send - there is an error:

Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 1844

At me in this file to this address:

foreach($nav_array AS $nav_url => $nav_title)

In a window such error:

Error 
An Error Has Occured! 
An error has occured, the following message has been left below:

Invalid Warning Type Specified 
[ Back ]

Actually the message has gone, the Obscene Words were replaced on *, but the warning to the user has not gone..