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)

[students_forum]

Originally Posted by Magnumutz

Delphiprogrammi has started being active again, let's hope he can update this wonderful mod !

cyber stalking I see ... you must be desperate!

[jmurrayhead]

Originally Posted by Delphiprogrammi

hi folks,

I have some spare over the weekend and i will install this on my 37.3 testboard and see what happens

Mr. Delphi, how was your weekend? Any progress?

[Delphiprogrammi]

Originally Posted by jmurrayhead

Mr. Delphi, how was your weekend? Any progress?

Yes the protected usergroups feature is indeed not working finding the problem cause will be quite impossible as that would require me to digg through more then 3800 lines of PHP code so this is not the news you all wanted to hear but i guess it's time for a switch to the vBulletin infraction system

[jmurrayhead]

Originally Posted by Delphiprogrammi

Yes the protected usergroups feature is indeed not working finding the problem cause will be quite impossible as that would require me to digg through more then 3800 lines of PHP code so this is not the news you all wanted to hear but i guess it's time for a switch to the vBulletin infraction system

This is horrible news...

[Magnumutz]

Oh NO !!
Switching to the infraction system is such a great loss

[sv1cec]

Delphi, welcome back.

The protected user groups should work fine, the check is made near the top of Warn.php in the function check_user. The function itself is located in functions_warning.php.

[Delphiprogrammi]

hi,

I'll be honest here.I just cannot understand how the new profile pages work i mean there is some explanation here but it's still not clear to me and aws that ....

[sv1cec]

Now you know why I hate the new coding scheme that vB is using these days?

Sorry buddy, I wish I could help. However, I think there are ways around it. Maybe you can add a block at the end of profile page with the warning buttons and the warning information. I do not know. It seems that vB is trying to make our lives more difficult, rather than facilitating coders.

[tehPARADOX]

Originally Posted by pnosko31

I was looking over this mod as i was thinking of using it and discovered in mysql it creates a table called vb_warningtype and in the file in some spots it tries to use the database vb_warning_types - that may cause some problems you are having

Can anyone possibly help me with this situation?

I have recently noticed old warnings are not getting removed automatically via Cron.

EDIT:
Manually executing the cron job: kill_warns, shows that warningype table doesn't exist. Looking over mysql, the table is named warningtype.

So I edited kill_warns.php:

    LEFT JOIN " . TABLE_PREFIX . "warningype wt ON(wt.warningtypeid = w.warned_warning_id)

to:

    LEFT JOIN " . TABLE_PREFIX . "warningtype wt ON(wt.warningtypeid = w.warned_warning_id)

Tried running the cron again, this time I received the following error:

AWS - Kill warnings 

Fatal error:  Call to undefined function convert_array_to_bits() in /home/xxxxx/public_html/forum/includes/cron/kill_warns.php on line 114

Line 114 shows this code:

        $user = array_merge($user,convert_array_to_bits($user['options'],$vbulletin->bf_misc_useroptions));

Any help would be appreciated.

[sv1cec]

Unless DelphiProgramming has changed the names of the tables, the name for the Warning Types table should be "warning_types".

If that's not the case, I would suggest you contact Delphi.

As for the unvalid function call, at the top of the kill_warns.php file you have to see the following lines:

        require_once('./global.php');
	require_once('./includes/functions_user.php');
	require_once('./includes/functions_newpost.php');
	require_once('./includes/functions_warning.php');

Please note that this is from the old AWS (for vB 3.0.xx) I haven't worked on the code after that, Delphi has.


That part of the code you quote (the one with convert_array_to_bits) doesn't exist in my code.