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

[Milchi]

Originally Posted by dai-kun

The warning points doesn't get reduced even though I deleted all the logs and completely remove all the warnings. Is there a fix for this?

Still have the same problem

sv1cec, would it be possible for u to create and php file (without vbulletin functions) to calculate the correct amount of warnings points for all members and writes them to it? this would be a workaround to run as a task every night until andreas has a solution

[MissKalunji]

so this still doesnt work alogn with inferno?

[Xplorer4x4]

Umm why would it need to work with the Inferno Warning System?

[MissKalunji]

Originally Posted by Xplorer4x4

Umm why would it need to work with the Inferno Warning System?

not inferno system....but the RPG

i read in like the first post that couple ppl couldnt get it to work when u go into your rpg it would give you a warning error because it uses the sendpm()



https://vborg.vbsupport.ru/showpost....&postcount=257

[Xplorer4x4]

Ahh best to be thorough the first time around. But sorry I tried .

[sv1cec]

This issue has been beaten to death. There is a routine with the same name in inferno and in AWS. Rename one of the two to something else, and then fine every occurence of that name in the hack's files and change it to the new name.

Second, the cron job which is supposed to remove the warnings, as they mature, was not correct. It was using $vboptions instead of the new $vbulletin->options. I just uploaded a new file (kill_warns.php) which should work OK.

Folks, please understand that I no longer provide support for this hack, I've stated from the beginning of the 3.5 version, that I have lost interest in it, since the vB changes are too many and I do not plan to upgrade my board to vB 3.5, so I have no reason to work on this any more. However, I am doing all I can to solve the issues you bring up. This is not always possible, since I have no idea on how the new version of vB works or how the new version of AWS works (as far as the vB installation etc is concerned).

Hmm, can't seem to find where in the code the button is located??
Searched through all of the templates, but nothing.

That should be in your postbit and postbit_legacy templates.

As for the other issue you have, these phrases are at the functions_warning.php file in the /includes directory.

[MissKalunji]

Originally Posted by sv1cec

This issue has been beaten to death. There is a routine with the same name in inferno and in AWS. Rename one of the two to something else, and then fine every occurence of that name in the hack's files and change it to the new name.

Second, the cron job which is supposed to remove the warnings, as they mature, was not correct. It was using $vboptions instead of the new $vbulletin->options. I just uploaded a new file (kill_warns.php) which should work OK.

Folks, please understand that I no longer provide support for this hack, I've stated from the beginning of the 3.5 version, that I have lost interest in it, since the vB changes are too many and I do not plan to upgrade my board to vB 3.5, so I have no reason to work on this any more. However, I am doing all I can to solve the issues you bring up. This is not always possible, since I have no idea on how the new version of vB works or how the new version of AWS works (as far as the vB installation etc is concerned).



That should be in your postbit and postbit_legacy templates.

As for the other issue you have, these phrases are at the functions_warning.php file in the /includes directory.

well thank you

[vampireus]

When issue a warn, I get this error

Fatal error: Only variables can be passed by reference in /home/yancom/public_html/music/includes/functions_warning.php on line 600

It don't appear if I set "Save copy of Warning Message in a predefined forum" to No. Anyone can help?

Thanks

[sv1cec]

Have you defined a forum, in which the warnings will be saved?

[vampireus]

Yes I did, although there is an error, the warning still go through, only the copy of Warning Message not be sent to predefined forum