Administrative and Maintenance Tools - Advanced Warning System 3.6.7

Advaned Warning System

This is a port of aws and i release this with permission...(yes i did ask the original author)

This version of the warning includes

• 1 vbulletin 3.6.x product file (XML)
• 1 admincp navigation XML
• 1 functions file(functions_warning.php)
• 3 images
• 3 cronjobs
• 1 modcp file to allow moderators to view warnings information without having to give admincp access(mod_warn.php)
• 1 admincp file to manage the system options(admin_warn.php)
• 1 XML to control permissions(bitfield_aws.xml)

For a completer list of the system features you can refer to this

This version will also require vbulletin 3.6.x to run.If you run 3.5.x or any other release then 3.6.x you will see a message.

This system is tested for a long time and i believe it's stable enough for a public release HOWEVER since this is a major hack and i'm just human please consider this first public run still as "beta"

instructions ow howto install can be found in the docs directory within the zip

statistics

• 25 plugins
• 27 templates
• 5 new MySQL tables
• 3 standard vbulletin tables alterd (user,post,and usergroup)
• 827 phrases
• 47 settings

updates

A problem has been found where no link is provided to view your own warnings(normal users) in the member profile only i fixed this.To get the fix you will need to reedit your "MEMBERINFO" template and reimport product-aws.xml (set allow overwrite to yes)

15-9-2006
I moved the cron jobs from the install/uinstall code to the product file.
version check url now uses https://vborg.vbsupport.ru/misc.php?...rsion&t=124477

to upgrade read upgrade.txt in the docs directory

24-9-2006

a product depency whas added the system will no longer install on PHP 5 (in response to continued error reports on that PHP version)

to report a possible bug

please go the system bugtracker here you can use the folowwing account

username:bugreporter
password:awsbug

no need to register yourself


30-11-2006
People on PHP 5 can follow this instructions to avoid the PHP version related error message BUT remember you are on your own if you do this.I won't upgrade my PHP until PHP 5 is there main stable release (www.php.net)


1-1-2007
A bug has been reported in the system.This bug whas causing vbulletin to throw an error when you try to use admincp => users=> add a new user

Fatal error: Call to a member function clean_gpc() on a non-object in class_dm_user.php(2385) : eval()'d code on line 35

Solution

Edit plugin "AWS:warn link in usermanager" and replace all code with this

PHP Code:

$quicklinks["../Warn.php?" . $vbulletin->session->vars['sessionurl'] . "do=WarnUserNoPost&id=" . $vbulletin->GPC['userid']] = $vbphrase['aws_warn_user_admin']; 


i'll update the package when i get home


Another Bug is fixed

This release includes a fix for the problem "call to member function on a non object class_dm_user.php)" when you try to add a new user manaually (after submitting the form)

[NFLfbJunkie]

Okay I think I fixed my above problem, but now have another one. My test registered user, even with the aws permission set to allow user to view warnings, I am getting that the user is restricted from doing so.

[Delphiprogrammi]

Originally Posted by SilverBoy

I solved one problem

if($_GET['do'] != 'viewmywarnings')
{
    if(!can_moderate())
    {
        print_no_permission();
    }
}

again you have capital letters missed

yes indeed that will throw up a standard vBulletin permission denied page it should be

PHP Code:

if($_GET['do'] != 'ViewMyWarnings')
{
    if(!can_moderate())
    {
        print_no_permission();
    }
} 


Junkie this will also fix your problem it's in Warn.php starting line 81

[NFLfbJunkie]

Made the changes and everything now works. Thanks.

[Delphiprogrammi]

Originally Posted by SilverBoy

I tried removing warning and redirect works ok.

now I can say the problem of seeing other users warnings exist because the user is the starter of the thread and get warning in it !!! (but only in the first page of the thread)

another point

when give a user warning we missed warning level in "Current warnings info:" I think it is important to be there.

again for errors when give a warning with pm, the old version of this hack was ignored pm lenght and if the user can read pm

again my tests are showing to me that the system works as intended.If you issue a warning to the member "testmember" only "testmember" and mods (and up) can see the details about the warning.It is possible warning points and such (the counters) are visible but then you have set the viewingoption to all

I can add an option to set an emailadress that will show up in emails send out by the system this way you will not reveal personal email adresses but all your mods will have toi have access to this mailbox

[SilverBoy]

iam sure its set to mgm

[Bellardia]

There is a glitch in the AWS options.

The number of warnings before ban will not change, it stays at 10. No matter how many times I save it, it changes back to 10.

[Delphiprogrammi]

Originally Posted by Bellardia

There is a glitch in the AWS options.

The number of warnings before ban will not change, it stays at 10. No matter how many times I save it, it changes back to 10.

hmmz that is working fine in here will do some tests through

[EdQ]

Originally Posted by sv1cec

The members can not see the details of the warnings, they can see how many warning points other members have and how many warnings, but not the details.

The cron job will either render the warnings "Inactive" or it will remove them all together. It depends on your settings in the AdminCP. If you are using the Historical option, warnings are never deleted completely. They always remain in the members accounts, so that (a) they act as reminders for the members and (b) they show the members past history to the admin team. If you want the warnings to be completely deleted, you may select not to maintain historical data.

I tried not maintaining the historical data. The warnings drop of when they mature (which is what I want) But now the bans drop off when the ban ends. Not when they mature.

Is there a option for this?

[Delphiprogrammi]

Originally Posted by EdQ

Is there a option for this?

Bans maturity periodEnter the number of days, a ban remains in a member's account. If set to '0', then the bans remain in the members accounts for ever. If set to a different number, a cron job will reduce the number of bans in a member's account by one, after so many days pass, from the day that ban was applied.
Attention: This does not mean that the user is unbanned. If you have a banning period of 7 days and you have set the bans maturity period to 5 days, the ban will be removed from the user's account after 5 days, but he will still be banned for another 2 days. In a production system, this option should always be much larger than the number of days a member is banned, when he reaches the ban limit.
This option obviously applies only to non-permanent bans.

admincp => Advanced Warning System => Manage Warning Options => Banning Options => Ban Maturity Period

[EdQ]

Originally Posted by Delphiprogrammi

Bans maturity periodEnter the number of days, a ban remains in a member's account. If set to '0', then the bans remain in the members accounts for ever. If set to a different number, a cron job will reduce the number of bans in a member's account by one, after so many days pass, from the day that ban was applied.
Attention: This does not mean that the user is unbanned. If you have a banning period of 7 days and you have set the bans maturity period to 5 days, the ban will be removed from the user's account after 5 days, but he will still be banned for another 2 days. In a production system, this option should always be much larger than the number of days a member is banned, when he reaches the ban limit.
This option obviously applies only to non-permanent bans.

admincp => Advanced Warning System => Manage Warning Options => Banning Options => Ban Maturity Period

I understand that, but does it matter if I use historical data?

I prefer not to so the warnings will come off when they mature. It seems when I use historical data, warnings are not removed when they mature. Just the warning level.


I am not sure if I am getting my point across.

Using historical data.
Warning Level is removed when matured
Warning is never removed (Not what I want)
Warning Bans stay until matured.

Not using historical data.
Warning Level is removed when matured
Warning is removed when matured
Warning Bans are removed when the ban ends. (Not what I want)

What I would like to see if either the warning or ban matures. It drops off the users account.