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

[D.Ilyin]

Originally Posted by sv1cec

if not, I can email you a different Warn.php file.

ye.. it will be greate...

[D.Ilyin]

another bug (or future )..... i found
Try to find user with given warning's in admincp. And try to:
"Remove"
_http://my.forum//admin_warn.php?act=remove&id=1&userid=99057&uname= andersder&wname=Замечание&postid=205118&ban=N&orderstring=
1. "admincp" is missing.
2. what if someone call warning type in chines?
"Copmletle remove"
_http://my.forum//admin_warn.php?act=completeremove&id=1&userid=9905 7&uname=andersder&wname=Замечание&postid=205118&orderstring=
same as above
"Warned User ID/Name"
_http://my.forum//user.php?do=edit&userid=99057
1. "admincp" is missing.

"Warned By"
_http://my.forum//user.php?do=edit&userid=46225
1. "admincp" is missing.

[sv1cec]

Is your admincp defined in the vB's configuration file?

[D.Ilyin]

Originally Posted by sv1cec

Is your admincp defined in the vB's configuration file?

i think so... because the link to "Comment" are right:
_http://my.forum/admincp/admin_warn.php?do=showcomment&id=1

[sv1cec]

Open your admin_warn.php file and find :

require_once('./includes/functions_misc.php');

Under that, add:

$admincpdir=$vbulletin->config['Misc']['admincpdir'];

Then find every occurence of "/admincp/" and replace that with "/$admincpdir/".

You will need to replace that about 10-12 times.

KirbyDE, please make that change as well.

[Michael-DLR]

Originally Posted by Michael-DLR

Hi!

Let me start off by saying this is the best hack for VB in my opinion and I appreciate Andreas and sv1cec for working on this hack for us.

I do have an issue and are in need of some guideance. Moderators and SuperModerators are receiving auto warns even though they are in the correct usergroup id's assigned by VB. The set-up explains not to put them in the protected usergroup which I did not. I have tried though adding the id to the protected usergroup to see if it would help and it did not.

Any ideas what I am doing wrong? Thank you.

Help? Thanks!

[sv1cec]

Are you using the Hierarchical schema? If yes, then Smods and mods can be warned by admins. If you do not want that to happen, do not use the hierarchical schema.

[sv1cec]

I think you have mixed up things. The image you attach is not from AWS. I do not know from which hack this is (it definitely is not even from the old ZT hack), but it's certainly not AWS.

In AWS you define each offence (Warning Type) in AdminCP, from there on, the moderators cannot change either the points associated with that offence or the duration of the ban. In a few words, AWS will cover your needs.

[Andy R]

sorry about that, please have a mod delete my post...

[adalren]

There seems to be a conflict with kirby's default sort plugin. When I install both, none of the $vbulletin->GPC variables work. It will work when either plugin is disabled.

What's weird is that I got both to work in my home server but the production server doesn't. The only think I can think of is that I installed it in a different order.