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

[Bubble #5]

Originally Posted by MGSteve

what it fixed was not being able to remove the first post.

Yes it allows you to remove PART of the first warning, but not all of it (see thumbnail).. Also, the e-mail that is sent out after that removal has a faulty link given as shown below:

The post for which you were warned, and whose warning has now been removed, can
be seen here:

Array[bburl]/showthread.php?p=52

[Luggruff]

Hmm, I've got a problem with the script, and am clueless why it is.
I've set the number of warnings before ban to 4 (then he's banned 3days), and after 4 more warnings, the user is to be banned 6 days, then 9 and so on. It's only that when the user finally is unbanned, he's banned again after only one warning.

Any solution?

[sv1cec]

Gentlemen,

Please understand what "Remove" means. It means "Artificially Mature", it just removes the warning points, as if the warning had matured. The warned member still has a warning in his record (unless you are not using historical records).

If you want to completely remove a warning (in case it was issued by mistake, for example) go to your AdminCP and use the "Completely Remove" function.

[sv1cec]

Originally Posted by stevew

It does seem to be the "bug" spoken of in this thread, i am also getting





But i still havent found an actual solution to it in this thread, so i had better not test the warning system on anyone else :nervous: I already have one casualty....oops lol



regards


I have found a couple more bugs, this time in the admin control panel, when i goto a users profile and click view warnings, it goes to this url

http://www.software-help.co.uk/modcp/admin_warn.php?act=do_finduserwarnings&userid=7

Which gives a page not found error, which i know the reason for but dont know how to solve it

I need that button to point to this url

http://www.software-help.co.uk/modcp/mod_warn.php?act=do_finduserwarnings&userid=7

Would appreciate a little nudge in the right direction on that




Also, while in mod cp looking at a user profile still, "warn user non post related" button, when i click that, it gives this error

regards and ssorry for being a pain, i am new to all this, but i am very willing to learn

Check the HTML code you have posted. The admin_warn.php is supposed to be in admincp directory, while in your error it appears that the program is searching for it in modcp. Have you set up the admincp directory in your board?

[Bubble #5]

Originally Posted by sv1cec

If you want to completely remove a warning (in case it was issued by mistake, for example) go to your AdminCP and use the "Completely Remove" function.

OK thanks for the tip sv1cec, we will rename 'remove' to something else.

Do you have any idea on how to fix the e-mail problem? :surprised:

[sv1cec]

Originally Posted by Bubble #5

Do you have any idea on how to fix the e-mail problem?

Have you define the bburl in your vb options? IT looks as if the URL to your board is missing.

Originally Posted by Luggruff

Hmm, I've got a problem with the script, and am clueless why it is.
I've set the number of warnings before ban to 4 (then he's banned 3days), and after 4 more warnings, the user is to be banned 6 days, then 9 and so on. It's only that when the user finally is unbanned, he's banned again after only one warning.

Any solution?

When a member is banned and then unbanned, the warning points he has collected are still in his account, they are not removed, just because he got banned and unbanned. The warning points are removed, as each warning he has received matures. So, if none of his warnings has matured when he receives the next warning, he is banned again. That's the way AWS works.

[Bubble #5]

Originally Posted by sv1cec

Have you define the bburl in your vb options? IT looks as if the URL to your board is missing.

Yes. ACP>Options>Site Name / URL / Contact Details> Forum URL.

[sv1cec]

Well, it could be something in the template (warn_em or warn_pm), but I can't check it anymore Xplorer4x4 has closed the test site that he had provided me with, so there is no way I can check it out.

Sorry!

I was looking at the templates, as they are in the warn.xml distribution file, and there seems there are some issues there.

For example, in warn_em template, there is this code:

The post for which you are warned can be seen here:
<if condition="$vboptions['warn_includepost']==1 AND $thread3!=''">
=======================================
$thread3
=======================================
<else />
$thread2
</if>
The admin/moderator who warned you, entered this comment:

Obviously, this should look like:

The post for which you are warned can be seen here:
<if condition="$vbulletin->options['warn_includepost']==1 AND $thread3!=''">
=======================================
$thread3
=======================================
<else />
$thread2
</if>
The admin/moderator who warned you, entered this comment:

The same should be done in warn_pm. Wherever you find $vboptions you should replace it with $vbulletin->options. This problem can be present in other templates too, so please check them out.

As for the email problem, I am not sure if the above will help you. The link to the warned post, should work fine from what I see in the code, if bburl is defined.

[stevew]

Originally Posted by sv1cec

Check the HTML code you have posted. The admin_warn.php is supposed to be in admincp directory, while in your error it appears that the program is searching for it in modcp. Have you set up the admincp directory in your board?

Hi there m8, i solved the problem, i changed the name of the mod_warn.php to admin_warn.php, it is in the correct directory, the mod_warn php file was uploaded to the modcp directory where it was supposed to be, the problem i was having is if i go into the MODCP and click the link it directs me to

http://www.software-help.co.uk/modcp/admin_warn.php?act=do_finduserwarnings&userid=7

The problem with that re-direct url is it directs to the modcp directory and the admin_warn.php file, which is not in that directory, so something isnt right, the files are in the correct directory, but as i said i changed the mod warn files name to admin_warn and now the modcp functions work


Still have other problems though :smoke:

[sv1cec]

This is definitely not the right way to solve your problems. Something is wrong with your installation, and with your change, I sincerely doubt if you are going to fix it.