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)

[ginger22]

This error:
[06-Jun-2007 17:44:59] PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /hq/site/foo/www/includes/class_dm_threadpost.php(656) : eval()'d code on line 1
Dissappear when I disabled postdata_start hook.
But, what happend if this be disabled? Or I need to enable this agayn?

Second error still here...

[Delphiprogrammi]

i tested it on my testboard with a post related warning and a non post related warning no errors at all (both of them didn't showed up) the postdata_start hook at wrong code PHP code in it true but you need to manually edit the plugin at that hook and no you need that hook or some data will be missing.I'll see later to package the fix as a plugin that you can import.This is not your fault but mine i forgot to mention you need to manually update that hook otherwise vBulletin will not update it

here it is imprt this through admincp => product system => download/ upload plugins

[ginger22]

The second error will be fixed?

[Silver_Seagull]

I am still getting errors on 4.4.7 after applying the fix and the updated files.

Parse error: syntax error, unexpected T_OBJECT_OPERATOR in C:\<path>\includes\class_dm_threadpost.php(656) : eval()'d code on line 1

and

Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in C:\<path>\includes\class_dm_threadpost.php(829) : eval()'d code on line 64

I've disabled all other hacks except this and I am still getting these errors, even on the default skin. Had to disable, since I don't have the old version lying around.

[Delphiprogrammi]

hmmmz,

I do drink much but it doesn't contain any alcohol.

this->validfields['title'][VF_CODE] = '$dm->set_info(\'orgtitle\', $data); return $dm->verify_title($data);'; 
$this->validfields['pagetext'][VF_CODE] = '$dm->set_info(\'orgmessage\', $data); return $dm->verify_pagetext($data);';

should be

$this->validfields['title'][VF_CODE] = '$dm->set_info(\'orgtitle\', $data); return $dm->verify_title($data);'; 
$this->validfields['pagetext'][VF_CODE] = '$dm->set_info(\'orgmessage\', $data); return $dm->verify_pagetext($data);';

i forgot a "$" $this is a PHP variable refering to the "current" object.The newly attached error_fix.xml contains the change and this time it's gonna work or you can shoot me

[ginger22]

Wow! Great! This work!
But i still get
[07-Jun-2007 09:57:54] PHP Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /hq/site/foo/www/includes/class_dm_threadpost.php(829) : eval()'d code on line 64

[ginger22]

And also: How can I do another language template?

[Delphiprogrammi]

Originally Posted by ginger22

And also: How can I do another language template?

You are free to Translate the phrases into any language you wish to use.. that's why the phrases system excist

as for the error message you still see that is coming from the postdata_postsave hook and that one is used by the automatic warnings feature which can be turned off in the system settings

The package availible for download has been updated to include the fix for the PHP error message and the original error_fix.xml is removed to avoid confusion

[ginger22]

Originally Posted by Delphiprogrammi

You are free to Translate the phrases into any language you wish to use.. that's why the phrases system excist

No, I mean, how can I create a language .xml file only for Language?

Originally Posted by Delphiprogrammi

as for the error message you still see that is coming from the postdata_postsave hook and that one is used by the automatic warnings feature which can be turned off in the system settings

Can you say, what exactly I should to do?

[Delphiprogrammi]

Originally Posted by ginger22

No, I mean, how can I create a language .xml file only for Language?

Can you say, what exactly I should to do?

• admincp => languages & phrases => {YOUR LANUGAGE} => translate phrases
• admincp => language.php?do=files => product advanced Warning System
• for each language you have installed vBulletin will display a corrosponding "translation box"
• please note you must be able to translate "from english"
• you will need the phrasetype id's used (you can see that in the product XML)

automatic warnings can be turned of by going to admincp => advanced warning system => manage system settings => use automatic warnings from posts and use automatic warnings from private messages set that to no

in case you get confused by the XML coding.You can also find the phrases you'll need to translate by quering your database like this

[sql]
SELECT * FROM vb3_phrase WHERE product = 'aws' ORDER BY fieldname DESC
[/sql]

if you use another table prefix (or none at all) you will need to replace that in the above example