Advanced Warning System (Beta Version)

Advanced Warning System


IF YOU ARE RUNNING vB 3.6, THERE IS A NEW THREAD FOR THIS HACK UNDER THAT VERSION. vB 3.6 USERS GO HERE:

https://vborg.vbsupport.ru/showthread.php?t=124477


This is a direct port of the Advanced Warning System, as it was implemented in vB 3.0.x. This port has all the features of AWS version 3.4.16, except the Notes.

For a complete description of AWS capabilities, please refer to the following thread:

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

The vB 3.5 compliant version of AWS includes:

1 Product XML (17 Plugins, 107 Phrases, 26 Templates, 43 Settings)
1 ACP Navigation XML
1 PHP Functions File
3 Images
2 PHP Frontend Files
1 PHP Admin CP File
1 PHP Mod CP File
3 PHP Cronjob Files

This port would not be possible, without the help of KirbyDE, to whom I am greatful. KirbyDE will also be responsible for supporting you here, with questions related to this particular release. Also, this port would not have been possible, without the help of Juan P hernandez, who offered me a free test system, in which the porting was performed.

The hack has been tested and it is believed to be bug-free, however since this is a major hack, I release it today (September 9th 2005) as beta.

I hope you all enjoy it.

History (Productversion)
3.5.b
Initial Version

3.5.b1
Fixed a typo that caused Errors in User Datamanager.
Fixed a wrong object reference in functions_warning.php

3.5.b2
Fixed a Bug that caused PHP Error Messages.
Fixed a Typo in the Install Code that causes mySQL Errors.
Updated the Template Edit instructions to be (hopefully) compatible with RC3

3.5.b3
Fixed User not showing up in automatic warning PMs
Fixed 2 missing Phrases
Fixed Hidden Warner being Used for Automatic Warnings
Fixed "View x's Warnings" Button in Usermanager not working

3.5.b4
Removed one unsued Phrase, added one missing Phrase
Fixed a Typo that caused PHP Errors when sending PMs
Fixed a Typo that caused PHP Errors upon Installation
Changed Product ID for Admin CP Navigation XML from vbulletin to aws, so it won't show up any longer if AWS is uninstalled/disabled.

A bug was found which didn't allow you to delete an entered Warning Type. Bug fixed in the current distribution file.

If you found a Bug, please report it at http://bugs.kirbydemos.ath.cx

This helps to keep issues organized, which can't be guaranteed if it's only posted in the Thread.
Thank you.

P.S.1: After you install the hack per the instructions, please update your installation with the separate files listed. They are newer files not included in the zip.

P.S.2: If you want to use the Notes feature, as it existed in AWS 3.4.16, please install AWS per the instructions in the zip file, and THEN follow the instructions included in the warn_notes_update_instructions.txt.

IMPORTANT NOTE: Please keep in mind that this hack is not supported. What this means is that I have no obligation to support it. The reason for that, is because I have no access to a vB 3.5 system any more, so I can't work on this hack any more. Andreas (or KirbyDE) who undertook the support of this version of the AWS hack in the beginning, is obviously too busy to support it. So you are on your own, at least as far as the interaction with vB is concerned. If you have an issue with the hack files themselves, I'll do my best to solve it, but without a test environment, it is not easy. So users of vB 3.5 beware!

P.S. May 31st 2006: The zip file uploaded today, should contain all the debugging done by Delphi, so it should be fine as it is. You do not need the other files listed at the right, only the zip. Download it and follow the instructions in it, for installing the hack. I leave the other files there, just in case some one needs them, they will be deleted later.

SV1CEC

[Andreas]

I really don't see how they could interfere with each other.

[adalren]

I don't see why it doesn't work either. When both are active, doing a clean_gpc doesn't put the request variables into $vbulletin->GPC. The forum starts to act funny and I can't login or view page 2 of anything. I had to edit the class_hook.php and disable fetch_hook to fix it.

[Andreas]

Erm ...

PHP Code:

define('DISABLE_HOOKS', 1); 


is the solution for such problems

Anyway, are you 100% sure that this is not caused by other Plugins?
If you are: Were you able to track down which Plugin exactly is causing the problems?

[adalren]

I disabled all plugins except AWS and it's AWS that's causing the problem. Initially I thought it was the sort order plugin conflicting because it instantly gave me an error when trying to view forumdisplay.

[adalren]

I removed the

PHP Code:

global $vbulletin; 


line in functions_warning.php file and it worked.

[Andreas]

Yeah, that line is unnecessary - fixed that earlier already.

[Lea Verou]

Wow, this hack does most of the things my mods and admins are currently doing manually! However to be able to use it, I need 2 features :nervous:
1. Categories. We have different warning limits for different "crimes". For example if somebody offends another member he is banned after 3 warnings. If somebody writes greeklish he's banned after 5 warnings and those counts are separate. One could have 4/5 for greeklish and 2/3 for offensive posts and not be banned.
2. Warnings limit based also on how many times the user was previously banned. for example if a user offends someone he's banned temporarily after 3 warnings as I said before. If, when he returns he does THE SAME thing 2 (not 3) more times then he gets banned permanently.

Is there any chance that these features will be added? :nervous:

PS: Are you greek? You must be the 2nd greek coder I've seen here! (I am the other )

[Xplorer4x4]

Originally Posted by Loukrhtia

Wow, this hack does most of the things my mods and admins are currently doing manually! However to be able to use it, I need 2 features :nervous:
1. Categories. We have different warning limits for different "crimes". For example if somebody offends another member he is banned after 3 warnings. If somebody writes greeklish he's banned after 5 warnings and those counts are separate. One could have 4/5 for greeklish and 2/3 for offensive posts and not be banned.

Why not just srt up a warning limit and then say you use 9 points...if they get 3 warning at 3 points there banned for oofending members. Then use 2 points as the warning value for greekish. They will actually hit 10 points instead of 9 but when the warning points are lifted the extra point will cancel out I would assume.

2. Warnings limit based also on how many times the user was previously banned. for example if a user offends someone he's banned temporarily after 3 warnings as I said before. If, when he returns he does THE SAME thing 2 (not 3) more times then he gets banned permanently.

I wouldn;t mind seeing this, but again it is all a matter of setting up a warning type and dividing up the points by your ban limit.

[Lea Verou]

I agree on the last part. It can be done this way, woo hoo!!
About the first part though... It will not work... The above were only 2 samples of our rules. There are other categories too, eg posting spam, trolling etc

[Xplorer4x4]

Set up multiple warning level for the same thing like i did....for example I have Spam1,Spam2, and Spam3...If I issue a spam 1 then this gives them one warning point where as spam level 3 is 3 warning points...this is exactly how you would have to do it with a catgorey set up this way will just be less organized.