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

[sv1cec]

Originally Posted by Revan

Okay Im gonna start remaking this version now, to work with $vboptions
sv1, I seem to remember some guy saying that he wasn't gonna release new versions every 3 days *sees 2 update emails in his inbox just today*
*cough*
XD

Well, one of the updates was a bug fix, and it was a serious bug, which made me turn red! So what was I supposed to do? Keep the fix for next month?

Gentlemen, I can withhold any updates and release them once a month. I've asked you in the past, what's your prefered way and got no anwers. It looks as if I have one vote for delayed releases, so that I do not send out new versions every two days (or sometimes every day). If I have no opposite views from you guys on this subject, I'll keep all the updates and release them once a month.

[Viol8or]

Feature updates don't have to be there in 2 days for, I'm happy you are willing to incorporate them and can wait a few days/weeks if necessary.
However, bugfixes should not be delayed, is my opinion.

[j_86]

This hack is VB3.05 compatiable, bar one very small code change related to the instructions, which isn't a big problem because most people who edit PHP files don't have mutiline search boxes and will search for the first line of code to change. I forgot which instruction it was, i'll find it again soon.

[Viol8or]

I think this is the one ... global $DB_site, $vboptions, $vbphrase, $bbuserinfo, $forumperms, $usergroupcache, $wehavecensoredwords, $weneedacounter, $newpostid, $_REQUEST;

But was stated a few post ago.

[Revan]

Originally Posted by sv1cec

Well, one of the updates was a bug fix, and it was a serious bug, which made me turn red! So what was I supposed to do? Keep the fix for next month?

I was kidding, mate...

[Viol8or]

I've encountered an error when trying to change something in the 'Manage Warning Options' page:

Database error in vBulletin 3.0.5:

Invalid SQL: update gf_warning_options set hierarchical='Yes', automatic='Yes', automaticpm='No', autocomments='No', warner='0', automatic_warner='1', collector='1', banned_limit='7', points_before_banned='10', banned_usergroup_id='16', troll_usergroup_id='8', protected_usergroups='6|6', aprotected_usergroups='6', restore_groupid='0', incr_ban_days='Yes', max_no_bans='4', bans_mature='31', viewoption='All', multiple_per_post='Yes', send_pm_warning='Yes', send_em_warning='Yes', email_on_ban='No', historical='Yes', allowoffpost='Yes', warnings_per_page='20'
where oid='1'
mysql error: Unknown column 'autocomments' in 'field list'

mysql error number: 1054

Date: Saturday 08th of January 2005 10:00:11 PM
Script: http://mysite.org/admincp/admin_warn.php
Referer: http://mysite.org/admincp/admin_warn...=manageoptions

Did an install from scratch to latest version of AWS
If I look at the table it is indeed not there.

[Rhoads]

Hello sv1cec

When I look at the users (View Banned Users) in the mod of adminCP I get the next error.

Parse error: parse error in /var/www/html/forum/modcp/banning.php on line 518

It's a edit file of the warning system, what can I do.

vb 3.0.5 file :

PHP Code:

print_table_header("$vbphrase[banned_users]: $vbphrase[temporary_ban] <span class=\"normal\">$vbphrase[usergroups]: " . implode(', ', 
$querygroups) . "</span>", 7); 


Edited file :

PHP Code:

print_table_header("$vbphrase[banned_users]: $vbphrase[temporary_ban] <span class=\"normal\">$vbphrase[usergroups]: " . implode(', ', 
$querygroups) . "</span>", 8);$querygroups) . "</span>", 7); 


Thnx, it's the only problem for me with 3.0.7 and vb3.0.5

[Delphiprogrammi]

hi,

updated to the latest release all works fine except for the new feature with that "stop" sign like image i don't see it and i am logged into my administrator account & did all the template modifications and uploaded the images to /images/misc/Warn.gif all is ee is a read line with the users warning level

Viol8or you need to add that colum to your database run

ALTER TABLE `".TABLE_PREFIX."warning_options ADD COLUMN autocomments char(3)

drop TABLE_PREFIX if MySQL complains about it and replace it by your table name

[Delphiprogrammi]

Originally Posted by drl2005

Hello sv1cec

When I look at the users (View Banned Users) in the mod of adminCP I get the next error.

Parse error: parse error in /var/www/html/forum/modcp/banning.php on line 518

It's a edit file of the warning system, what can I do.

vb 3.0.5 file :

PHP Code:

print_table_header("$vbphrase[banned_users]: $vbphrase[temporary_ban] <span class=\"normal\">$vbphrase[usergroups]: " . implode(', ', 
$querygroups) . "</span>", 7); 


Edited file :

PHP Code:

print_table_header("$vbphrase[banned_users]: $vbphrase[temporary_ban] <span class=\"normal\">$vbphrase[usergroups]: " . implode(', ', 
$querygroups) . "</span>", 8);$querygroups) . "</span>", 7); 


Thnx, it's the only problem for me with 3.0.7 and vb3.0.5

look carefully that you didn't forgot a ( { ) } or quotes parse error is php syntax related error you should look in the line number php tells you OR in the lines of code above it

[Rhoads]

Originally Posted by Delphiprogrammi

look carefully that you didn't forgot a ( { ) } or quotes parse error is php syntax related error you should look in the line number php tells you OR in the lines of code above it

Thnx Delphiprogrammi

It's fixed, I forget to delete $querygroups) . "</span>", 7); after replacing that with $querygroups) . "</span>", 8); :ermm: