The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
|||||||
Advanced Warning System (AWS) Details »»
|
|||||||||||||||||||||||||
Advanced Warning System Version 3.5.0
The AWS version for vB 3.5 has been released. You can download it and get support in this thread: https://vborg.vbsupport.ru/showthread.php?p=770032 Advanced Warning System Version 3.4.16 (latest stable release for vB 3.0.x) LATEST ANNOUNCEMENT The AWS has its own Premium Forum here at vBulletin.org, so please use that for questions and discussion on this hack. The Permium Forum is located at : https://vborg.vbsupport.ru/forumdisplay.php?f=105 This Warning System owes its existence to Zero Tolerance's Warning Hack (https://vborg.vbsupport.ru/showthread.php?t=65336). I liked the idea, so I installed Zero's hack in my forums site. However, as in most cases, I was not fully satisfied with the way it worked, so I started customizing it. Other people in the thread above, asked questions, which I had already answered by my customizing work, so I answered, giving away those parts of the code, that I had modified. In the long run, I almost hijacked the thread and the hack from Zero, so I guess I owe him an apology. However, the mods I did have compiled a new, more complete warning system, with much more functionality. Several members from that thread, asked if this could be released as a new hack, so after discussing it with Zero, here it is. What it does? Well, it is a Warning System, which means it allows you (the administrative team of your site, in other words the admins, the supermods and the mods), to define offences, which the members of your forum should NOT commit. But as we all know, there are instances where members do not follow the rules. In that case, this warning system, allows you to issue a warning to the member who commited the offence. The warning has some points associated with it, as well as a period over which it is valid. When a member gathers enough points, he is banned from your forums, for a predefined period of time. That's mostly it, but below, you can find a short list of features: Full warning system with: - post- and non-post-related warnings - hierarchical warning schema - hidden or real warners - customizable maximum warning points - automatically bans members who reached the maximum warning points - customizable ban days - customizable ban user group and permanent ban user group - customizable restore user group, where users are restored after they get unbanned - customizable option for who can see the warning level of the members - automatically issued warnings for posts which contain censored words - automatically issued warnings for private messages which contain censored words - supports incremental banning periods - supports multiple warnings for the same post - warned members are notified either by Private Message or e-mail when they are warned and when one of the warnings they have received is either deleted or expired - maintains historical listings of issued warnings (even if deleted or expired) - customizable warning types - each warning type has predefined warning points associated with it - each warning type has predefined maturity period, after which it is automatically deleted - reports for admin, mods and members - cron job included to automatically remove matured warnings - uses vBulletin's cron job, to automatically unban banned users - all options are setable in your AdminCP - user warning points and number of bans viewable in your AdminCP User Manager. - statistics show warning per type, warnings per warner, bans per user. - Allows you to warn a user from your AdminCP/User Manager. - Large "Warn" sign, in posts which have received a warning, for mods, supermods and admins, to easily distinguish those posts. - Ability to remove user's avatar, signature or usage of the Private Messaging system, depending on the warning points he has collected. - Supports non-standard admins, supermods and mods user groups. - Allows you to save a copy of the warning send to the warned user, in a predefined forum. - Allows you to issue "Alerts" (warnings without warning points, for first-time offenders) - Allows you to add private or public notes for a user, either post-specific or not. Notes appear in the postbit, above each user's message. - etc. Admitedly, this is not an easy hack to install. It requires 20 new templates and modifications to some existing ones too. It requires five new tables and modifications to some others. It requires several new phrases. I've tried to make the installation, as easy as I could, by automating certain tasks in an automatic installer. The installer will add the new templates for you, add the new tables required and change the existing ones, and will add the required new phrases. You will have to manually edit the existing templates and the php files though. I also included an upgrade script, which will upgrade those who are using Zero Tolerance's warning hack (version 1.5) to this one. An uninstaller is also included, which removes what the installer installs. Please keep in mind, that this is a very difficult hack to install. For this reason, I strongly recommend that you back up your database before starting the installation. I also suggest that you keep copies of each file and template you edit, so that you can always revert to a previous stable condition. Finally, I strongly suggest that you always run the latest release. The zip file always contains both the instructions and the files required to install the latest version. If you have installed a previous version and want to upgrade to the latest, there is a text file attached, in the zip with upgrade instructions. Follow them. In this thread, you will also find a more detailed document describing the features of this hack, as well as a document describing its version evolution. Also keep in mind that the installer, will add the AWS templates only to your default style. If you want to use them in another one, you may try this Zero Tolerance's hack, which copies the templates to other styles you may have. Another thing, the installation instructions were written when vB was at release 3.0.3, so you may expect to find some differences, with the latest files and templates. As far as I can tell, I haven't faced any such case, but I post this reservation here, since I do not have the time to recheck all the instructions for compliance with the latest vB release. The hack has been installed and is working fine with the vBulletin version shown at the top of this thread. Finally, if you are using more than one style, the installer will install the templates only in the default one. If you want to use the rest of your styles, here is a hack, that will do this for you. This hack can also be integrated with Zero Tolerance's vBChat. However, since I am using a heavily-modified version of vBChat, I haven't included instructions, on how to patch the original vBChat files, in the documentation. If you are interested in having AWS issue automatic warnings when one of your user enters a censored word in a vBChat message, or if you want your moderators to be able to warn a user, who misbehaves in vBChat, please post a thread in this forum and I'll help you through. This is my first officially released hack, so please don't be to harsh with me, if I broke any rules or made any mistakes. The mods have been tested extensively, both by me and two volunteers (thank you gentlemen), but I am only human. Closing, let me thank Zero Tolerance, who got me started in this, and who owns a big part of the code of this hack. I definnitely couldn't have done it, without his code. Special Note For those who upgrade from Zero Tolerance's hack to my AWS, even though I have included a script which will do some of the work automatically, not everything is done by that script. Read the installation instructions carefully. You have to run the upgrade script first and then do several things manually. If you just run the upgrade script and just upload the files, the AWS will not work properly. If you have any questions, please do not hesitate to post here. Also, let me add here, that version 3.3.0 wouldn't have been possible without the contribution of Revan. And a couple of warnings: PLEASE DOWNLOAD THE LATEST ZIP FILE FROM HERE, BEFORE YOU START INSTALLING THIS HACK. JUST BECAUSE YOU DOWNLOADED IT A COUPLE OF DAYS AGO, THAT DOES NOT MEAN IT IS THE LATEST VERSION. MAKE SURE YOU DOWNLOAD THE ZIP, JUST BEFORE YOU START INSTALLING THIS HACK. LATEST VERSION Version 3.4.16 (released Thursday August 25th, 2005 GMT 18:18) A couple of bugs fixed in this version. One is related to the Notes feature, and it allowed plain users to see the notes entered, if the "Who can view warning points" setting was set to "All". Features.txt a new version of this file has been uploaded on April 4th2 005 GMT 09:30, which covers the latest additions to the hack. The original Features.txt file hasn't been updated since the first release of this hack, so it was time for an update. John Show Your Support
|
|||||||||||||||||||||||||
About Developer
Visit Web Site
DB Changes 
No support by the author.| Comments |
|
#652
01-11-2005, 04:33 AM
|
|||
|
|||
Quote:
DESCRIBE warnings Rgds 
|
|
#653
01-11-2005, 04:38 AM
|
|||
|
|||
|
Quote:
HTML Code:
<if condition="$bbuserinfo[usergroupid]==6"> do this </if> HTML Code:
<if condition="$bbuserinfo[usergroupid]==6 OR $bbuserinfo[usergroupid]==13"> do this </if>
|
|
#654
01-11-2005, 05:17 AM
|
||||
|
||||
|
Quote:
Code:
Host: localhost Database : lgk2 Generation Time: Jan 10, 2005 at 11:14 PM Generated by: phpMyAdmin 2.6.0-alpha2 / MySQL 4.0.15-standard SQL-query: DESCRIBE warnings; Rows: 10 Field Type Null Key Default Extra wid int(15) PRI NULL auto_increment warned_user int(15) 0 warned_by int(15) 0 warned_time int(15) 0 warned_reason text warned_post int(15) 0 warned_warning_id int(15) 0 warned_status char(1) YES NULL removed_by int(15) YES NULL removed_date int(15) YES NULL
|
|
#655
01-11-2005, 06:25 AM
|
|||
|
|||
|
Quote:
That does not make sense. Your table has the right columns, the SQL statement is trying to insert the right number of values, what on earth is this? Here is my warnings table description: HTML Code:
wid int(15) PRI auto_increment warned_user int(15) 0 warned_by int(15) 0 warned_time int(15) 0 warned_reason text warned_post int(15) 0 warned_warning_id int(15) 0 caused_ban char(1) YES warned_status char(1) YES removed_by int(15) YES removed_date int(15) YES Do me a favor, try to add a non-post related warning from a user's public profile. See if that produces the same error. Rgds
|
|
#656
01-11-2005, 07:26 AM
|
||||
|
||||
|
OK here it is.
Code:
Database error in vBulletin 3.0.5:
Invalid SQL: insert into warnings values('','145','1','1105435458','Ignore this I'm just testing','','1','N','A','','')
mysql error: Column count doesn't match value count at row 1
mysql error number: 1136
Date: Tuesday 11th of January 2005 01:24:18 AM
Script: http://www.letsgokings.com/bbs/Warn.php
Referer: http://www.letsgokings.com/bbs/Warn.php?do=WarnUserNoPost&return=user&id=145
Username: RinkRat
IP Address: 66.214.41.130
OK I just tried a warning from a thread and got this Code:
Database error in vBulletin 3.0.5:
Invalid SQL: insert into warnings values('','1742','1','1105435656','Just testing ignore this.','809396','11','N','A','','')
mysql error: Column count doesn't match value count at row 1
mysql error number: 1136
Date: Tuesday 11th of January 2005 01:27:36 AM
Script: http://www.letsgokings.com/bbs/Warn.php
Referer: http://www.letsgokings.com/bbs/Warn.php?do=WarnUser&id=1742&post=809396
Username: RinkRat
IP Address: 66.214.41.130
|
|
#657
01-11-2005, 07:53 AM
|
|||
|
|||
|
Quote:
PHP Code:
PHP Code:
Rgds
|
|
#658
01-11-2005, 09:35 AM
|
||||
|
||||
|
Quote:
Well, it took a little trial and error, but I got it to work. If you're interested, the code I used follows... Again, Admin is 6 & 13, Super Mods are 5 & 21, and Mods are 7 & 20: HTML Code:
<if condition="$hierarchical=='Yes'"> <if condition="($post[usergroupid]!=6 AND $post[usergroupid]!=5 AND $post[usergroupid]!=7 AND can_moderate($forum[forumid], '', $bbuserinfo[userid])) OR ($post[usergroupid]==7 AND can_moderate($forum[forumid], '', $bbuserinfo[userid]) AND $bbuserinfo[usergroupid]==5) OR ($bbuserinfo[usergroupid]==6 AND $post[usergroupid]!=6) OR ($post[usergroupid]!=13 AND $post[usergroupid]!=21 AND $post[usergroupid]!=20 AND can_moderate($forum[forumid], '', $bbuserinfo[userid])) OR ($post[usergroupid]==20 AND can_moderate($forum[forumid], '', $bbuserinfo[userid]) AND $bbuserinfo[usergroupid]==21) OR ($bbuserinfo[usergroupid]==13 AND $post[usergroupid]!=13) "> <a href='Warn.php?do=WarnUser&id=$post[userid]&post=$post[postid]'>Warn $post[username]</a> ? </if> <if condition="($post[usergroupid]!=6 AND $post[usergroupid]!=5 AND $post[usergroupid]!=7 AND ($bbuserinfo[usergroupid]==7 OR $bbuserinfo[usergroupid]==5)) OR ($post[usergroupid]==7 AND $bbuserinfo[usergroupid]==5) OR ($bbuserinfo[usergroupid]==6 AND $post[usergroupid]!=6) OR ($post[usergroupid]!=13 AND $post[usergroupid]!=21 AND $post[usergroupid]!=20 AND ($bbuserinfo[usergroupid]==20 OR $bbuserinfo[usergroupid]==21)) OR ($post[usergroupid]==20 AND $bbuserinfo[usergroupid]==21) OR ($bbuserinfo[usergroupid]==13 AND $post[usergroupid]!=13)"> <a href='Warn.php?do=ViewWarnings&id=$post[userid]'>View $post[username]'s Warnings</a> ? </if> <if condition="($post[userid]==$bbuserinfo[userid] AND $post[usergroupid]!=6 AND $post[warning_level]>0) OR ($post[userid]==$bbuserinfo[userid] AND $post[usergroupid]!=13 AND $post[warning_level]>0)"> <a href='Warn.php?do=ViewMyWarnings'>View your Warnings</a> ? </if> </if> </if> <!-- end of warning system -->
|
|
#659
01-11-2005, 09:40 AM
|
|||
|
|||
|
Quote:
One thing I would suggest, is to avoid using the Hierarchical Schema, and declare those additional user groups, as protected user groups, so that they can't be warned. I know that not using the hierarchical schema reduces the functionality, in the sense that a super mod cannot warn a moderator, but it also simplifies things, which in your case is something you would like. Correction: This solves your Warn sign issue. But it does not solve the hack's operation issues. There are more places where you have to do the same changes, like for example, when the "Warn XYZ" and "View XYZ's Warnings". The code there also uses the group information to decide if the links should be visible or not. Also, in the place where the warning points and the number of bans is shown. It's none of my business of course, but why are you using two groups for each role? Rgds Rgds
|
|
#660
01-11-2005, 09:50 AM
|
||||
|
||||
|
Quote:
Just throwing the few cents I got about this out there 
|
|
#661
01-11-2005, 10:07 AM
|
||||
|
||||
|
Quote:
I was going to say I noticed that the Warnings by Warners Statistic doesn't list anyone in the other three usergroups. If you get a chance, and have the time, I'd appreciate it if you could note where else I will need to make changes. I first tried adding an "OR" to each one, followed by it's counterpart, but that made it possible for all the staff to warn in every forum, and allowed the members to see the links. The way it is now, every staff member can see the WARN image, and the view links, but only the super mod, admin, and the specific mod for that forum can see and use the warn links. It may not be right, but so far, I absolutely love it. It took me a couple hours to install it, but I haven't received a single error message yet, and for me, that's an accomplishment worth celebrating. The two Admin usergroups are for webmaster and admin, which have slightly different abilities, but are still both admin. The rest of the usergroups were doubled a couple years ago when we decided to create a second usergroup for sponsoring members, sponsoring moderators, and sponsoring super mods, and everything has just been built around that ever since. I'm sure there was/is an easier method, but I'm a mechanic, not a coder, and this stuff is as foreign to me as cooking. lol.
|
 |
«
Previous Thread
|
Next Thread
»
|
|
All times are GMT. The time now is 07:33 PM.