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)

[tehPARADOX]

Edit #2: Nvm

[tehPARADOX]

Hi guys, it's me again.

This modification has always been semi-working on my 3.8+ installation. The only problem that I noticed is the cron job that is set to automatically remove expired warnings, wasn't doing it at all. The job would run, but the warnings weren't removed. Tried running manually and I noticed the first error. After I fixed that error, I encountered another error. And one more after that.

Since then I've been going through Admincp > Advanced Warning System > View Warnings Log. And removing the expired warnings individually. As you can tell, this is quite troublesome. But I diligently kept up with it for a year because I felt this modification was much more useful than the default infraction system.

Well anyways, I managed to be able to find and fix all the errors regarding the cron to successfully remove expired warnings like it should.

Open "kill_warns.php"

1. Line 45
Find:

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

Replace with:

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

2. Line 114
Find:

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

Replace with:

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

3. Line 163
Find:

                $warnerdata = $vbulletin->db->query_read("SELECT username, email FROM " . TABLE_PREFIX . "user WHERE userid = $vbulletin->options[warn_warner]");

Replace with:

                $warnerdata = $vbulletin->db->query_read("SELECT username, email FROM " . TABLE_PREFIX . "user WHERE userid = '{$vbulletin->options['warn_warner']}'");

[maxie]

Hope this mode will update into 3.8.x or 3.8.4

[puddlove]

Would it be at all possible for this to be updated to work on 3.8.4? Looks really useful.

[puddlove]

Originally Posted by TSR

Delphiprogrammi, i tried reporting this to the site in the txt, it was down for me.
Here is 1 the 1 main error i have seen through some testing.

1) on warning, the site admin username shows up in the private message listing area. However, when you open the pm the selected hidden warner id appears correctly.
So again, in pm the correct hidden warner id is working, but if you view all the pms in your box, it shows who it came from.

If i remove the warning via admincp, the hidden warner id works in private message listing and in the private message.

* 2 images attached*

I'm having the same problem as TSR here. Apart from that, everything works fine.

If you warn a user, in the User CP PM area it shows the admin username rather than the username of the hidden warner account. When you click to read the actual PM, the hidden warner username is shown correctly as it should be. It's only in the main User CP PM area that the incorrect admin username is shown instead of the hidden warner account.

Anyone know how to fix this? It can be done - I managed to fix it 2 years ago to always show the hidden warner account in all areas. I think I edited the Warn.php file. But unfortunately, I can't remember how I did it, and I lost the edit. Someone please help!

[Elixar]

Any chance of this being upgraded to 4x?

[ozzy47]

Originally Posted by Elixar

Any chance of this being upgraded to 4x?

Can't you use the infraction system to do this?

[sv1cec]

While I am not the author of this hack, I am the original author of the Advanced Warning System, back when vB was at 3.0.xx.

Believe me, the infractions system that vB currently has, leaves a lot to be desired, compared to AWS.

I have managed to implement most of the AWS features in vB 4.2.2, but I didn't spend the time to make it an installable hack. My moderators were all over me, when we moved from 3.0.xx to 4.2.xx, so I had to do my best to give them a working version of AWS. I also don't have the faintest idea of how to make an installable package. So yes, I have it working in 4.2.2 (at least 80% of the original hack) but no, I can't release any of it.

Sorry!

[Delphiprogrammi]

Hi,

Well this has not been ported because i thought everybody whas using the infraction system which is much more advanced.

I still have a /testvb/ where i can try things out i'm on 4.4.2 PL 3 not planning to go vb 5 .

I'm not promosing anything yet but i'll see what i can do i just didn't realize people where still using this .


I've had a quick look and there are a few things changed since vb 3.x.x

• fetch_template calls must be replaced with the vB_Template class

• the template syntax changed so all templates must be adjusted accordingly

[sv1cec]

Hey Erik, good to see you back here!

I have some templates that I can send you, in case you are interested in continuing the development of AWS. Just let me know.

As I said, I have it working on my site, but not in a condition I can release to the puclic.