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

[bosal]

no i'm trying to add new type

[Delphiprogrammi]

Originally Posted by bosal

no i'm trying to add new type

go in your database with phpMyAdmin or something like that and create a backup of the table warning_types after that empty it then add all the warning types you'd like to use done......

i know it's kind of a dirty solution but it's all i can think off the add function works fine in here

[bosal]

no, i found the bug, i had none warning_alert warning_alertcomment

[GoTTi]

there is no instructions.txt file with the zip???

[bosal]

there is, in folder upload/docs

[Delphiprogrammi]

hi people,

looking at vbulletin.com 3.6 beta 1 this is hack is "near" to death.3.6 beta 1 will have a warning system by default and i always run the latest release availible.However i'll keep a 3.5.4 for "/testvb" so i can continue with this thing here

[EdQ]

Originally Posted by bosal

yah i updated my version i had a 1.0.4 ver. it works great

@EdQ

go to usergroups, edit admins, sup mod etc. and activate the checkboxes aws(Advanced Warning System) Permissions

Thanks, I didn't realize the upgrade added this.

[DannyBoy8406]

Is there a way to modify this hack so that the Alert Threads and Warning Threads are posted as posts in a thread instead of being individual threads themselves?

[Delphiprogrammi]

Originally Posted by DannyBoy8406

Is there a way to modify this hack so that the Alert Threads and Warning Threads are posted as posts in a thread instead of being individual threads themselves?

why on earth would you wanna do that ??

[GoTTi]

first quesiton:

all the postbit modifications...should i be altering the postbit_legacy also???

also the instructions say:

In Template postbit
FIND
------------------------------------------------------------------------------------------
<if condition="$post['signature']">(this procedure is the same for postbit_legacy)
------------------------------------------------------------------------------------------
REPLACE that with
------------------------------------------------------------------------------------------
<if condition="$post['signature'] AND (($vboptions[warn_sig_thresshold]<0 AND $post[warning_level]>=$vboptions[warn_sig_thresshold]) OR $vboptions[warn_sig_thresshold]==0)">

when i look in my postbit_legacy i see:

<if condition="$post['signature'] AND !$vboptions['shownsigs'][$post[userid]] AND $vboptions['shownsigs'][$post[userid]] = true">

what do i do?