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

[Scout]

Hello from Russia!

Members can`t read warn-lists?

[Snoop-It]

Originally Posted by Andreas

The vBulletin 3.5 product system does handle settings that are attached to products.
However, if you already have the settings from the 3.0 Version in your database, you will run into problems.

Running this query before installing the product XML should take care of this:
[sql]
UPDATE setting SET product='aws' WHERE varname IN ('warn_version', 'warn_hierarchical', 'warn_automatic', 'warn_automaticpm', 'warn_autocomments', 'warn_automatic_warner', 'warn_warner', 'warn_collector', 'warn_banned_limit', 'warn_points_before_banned', 'warn_warnings_before_banned', 'warn_banned_usergroup_id', 'warn_protected_usergroups', 'warn_troll_usergroup_id', 'warn_restore_groupid', 'warn_incr_ban_days', 'warn_max_no_bans', 'warn_bans_mature', 'warn_viewoption', 'warn_multiple_per_post', 'warn_send_em_warning', 'warn_send_pm_warning', 'warn_email_on_ban', 'warn_historical', 'warn_allowoffpost', 'warn_warnings_per_page', 'warn_textbutoption', 'warn_modoption', 'warn_sig_thresshold', 'warn_avatar_thresshold', 'warn_aprotected_usergroups', 'warn_pmcutoff', 'warn_admingroups', 'warn_smodgroups', 'warn_modgroups', 'warn_savecopy', 'warn_savecopyforum', 'warn_allowalerts', 'warn_allowalertscomment', 'warn_alertslifetime', 'warn_savecopyalert', 'warn_includepost', 'warn_allownotes')[/sql]

Sorry to say, but that didn't solve the problem and on my database in the phpmyadmin part... there arnt any of those warn_ tables.. apart from..

vb3_warn_notes
vb3_warning_types
vb3_warnings

And i ran the query any way and it didn't work - it just gave me an error. i dont want to uninstall the old version as mydata on those tables will be gone.. the settings the options the people banned / warned etc...

Help... :ermm:

[Andreas]

Send me a PM with ACP details.

[Andreas]

Query fixed
Should be installed now.

[Snoop-It]

:banana: should i install it?? or would you like to do it?? lols :nervous:

[Andreas]

Erm ... as stated it is already installed.

[Michael-DLR]

Hi!

Let me start off by saying this is the best hack for VB in my opinion and I appreciate Andreas and sv1cec for working on this hack for us.

I do have an issue and are in need of some guideance. Moderators and SuperModerators are receiving auto warns even though they are in the correct usergroup id's assigned by VB. The set-up explains not to put them in the protected usergroup which I did not. I have tried though adding the id to the protected usergroup to see if it would help and it did not.

Any ideas what I am doing wrong? Thank you.

[TJFweb]

Originally Posted by Andreas

@TJFweb
Hmm, feel free to provide better Templates
What exactly don't you like regarding them?

Hi,

This is no doubt a very good hack but I'll need to spend some time working out the necessary template edits (as I am using a non standard vB template) to get AWS to work. I think my custom style also affects the colspan of some of the tables in Warn.php.

[kangta]

Hello,

For some reason the install is taking forever for me. I go to upload the XML as a new product, and it sits there forever. I don't get the little expanding dots while it's installing or the finish notification or anything. I've just now figured out that the longer I let it sit, the more plugins/hooks get installed, not sure about templates, but I'll let it sit for longer than 5 minutes before interrupting it this time and see if it ever actually finishes.

Just wanted to point this out and/or see if anyone else was having the problem. I had the system for 3.0.x installed before we upgraded to 3.5.0. Didn't think of removing the old DB entries before I installed the new warning system, so that could have been part of my problem. Not sure at this point...

[TJFweb]

I've managed to get it installed on my board ;-) Just had to manually sift through the edits to make sure that everything gets inserted in the right place. It's just that I'm not very comfortable with instructions that involve replacing huge slabs of code because I use a lot of custom hacks and have a non-standard vB style running on my board which I don't want to mess up.

Here's a tip for everyone who's installed this (fixes the colspan on Warn.php):

Open warn_viewtype_end template:

Replace

<tr>
	<td class="tfoot" colspan="7" align="right">Warning limit before being banned: $vboptions[warn_points_before_banned] points. Initial banning period: $vboptions[warn_banned_limit] days.</td>
</tr>
</tbody>
</table>

with

<tr>
	<td class="tfoot" colspan="8" align="right">Warning limit before being banned: $vboptions[warn_points_before_banned] points. Initial banning period: $vboptions[warn_banned_limit] days.</td>
</tr>
</tbody>
</table>