Warning Hack V1.5

Version 1.5 Note: You must have v1 installed to upgrade, the upgrade process is small so there was no need to write out a fresh install.

It has come to my attention that a "decent" warning system isn't available here on vbulletin.org, which is quite a shame, and because forums like mine, and probably yours need a simple yet advanced warning system to keep things under wraps

Anyway, i thought i might aswell release what i made, prior to me getting off my ass... lol

Administration Features:
View Warning Logs
- Displays all warnings, warned user, warned by, link to the warned post, date, warning type, and the comment specified when the warning was given, and a remove warning link
(Remove will remove the log and also put the members warning level back down in accordance to how much it was increased by the selected warning removed)
Unban Banned Members
- A simple page that you should visit every few days, it will automatically ban any auto banned users by the warning system where there ban time has expired
Warning Options
- Here you can set the following:
-- Number of warn points before member is auto banned
-- Number of days a member is auto banned for
-- View Warnign Types
-- Add Warning Type
-- Add warning type has the following fields:
---- Name/Description/Warn Points Given

Forum Features:
Every post has "Warn [Name]" and "View [Names] Warnings"
These are only accessiable by a member group which is allowed to "moderate" (Moderating groups are auto detected)
Clicking the Warn link will bring you to a page where you view the user your warning, a link to review the warned post, members current warning level, and below the warning types, has a drop down menu to select the warning type, and a text field to put your comment for why this warning is been issued
Upon completing the warning form, the warned user will be Pm'ed from the person who warned them, with the comment put down and a link to the post

View Warnings link will display logs of only that specified user's warnings, the same features as the admin cp warning logs, only just for this user

Members can access only 1 page of the warning system, which is "View My Warnings", this link is added to the quick links drop down menu
Here they simple view there warnings, just like a moderator would, only without the remove warning link

V1.5 Features:
Protectable Usergroups:
No user's in these defined groups can be warned, or banned.
Root Admin Force Protection:
Userid 1 cannot be warned, canned be banned, this is not optional, this is forced for security.
New Unban Members Set Up:
Now displays all currently banned user's, what time they were banned, what time they are supposed to be unbanned. You may unban the user even if there time has not expired (You will be notificed if they have not served the time issued upon ban, but not stopped). Upon unbanning, you choose the members 'new' warning level and the user's usergroup to move them into
Set banned usergroup:
You can now easily choose from a drop down menu which usergroup user's are sent to if after been warned they are banned.

V1.5 Bug Fixes:
- User locations in 'Users online' shown as unknown if they are warning/viewing warnings (Priority: Medium)
- Unban members system renovated and now fully works (Priotity: Maximum)
- No mysql errors upon sending a pm if the PM table had been altered (Priotity: Maximum)
- New protectable usergroups to stop any group of your choice been banned (Priotity: Maximum)
- Last time visited didn't appear when error page occured (Priotity: Low)
- Un-used global in PM function (Priority: Low)

I hope you enjoy the system, my staff teamare very pleased with it and find it of great use, enjoy the hack

- Zero Tolerance

[sv1cec]

Originally Posted by Blam Forumz

Is it possible to make it so I can set out a system like this :

5 - Warnings = 3 day ban.

After those 3 days are up, then another 5 warnings = 10day ban



Thanks

/Blam

Well, not exactly, but you can make it so that

5 - Warnings = 3 day ban.
5 more Warnings = 6 day ban.

I could make the multiplication factor a parameter in warning_options, but it will have to be a multiple of the original ban days parameter.

etc.

[sv1cec]

Originally Posted by Blam Forumz

How can I stop my Super Mods warning my Admins?

Use the protected groups field. I assume that your admins/mods/supermods should all be there, so that they can't warn each other. As I said before, I do not use Super Mods, so the full hierarchical scale is not implemented.

Rgds

[beano33]

Here's a tip for those who use Super Moderators. The conditionals in the hack are written for Moderators as the primary usergroup. If you don't want to edit that, you can make everything work fine by changing usergroup settings.

For Super Moderators use the settings:
Primary Usergroup: Moderators
Display Usergroup: Super Moderators
Additional Usergroups: Super Moderators

As long as the primarary usergroup is moderators, everything in the hack works fine. Your Super Moderators will still be displayed as Super Moderators and have Super Moderator permissions doing it this way.

[sv1cec]

Originally Posted by beano33

Here's a tip for those who use Super Moderators. The conditionals in the hack are written for Moderators as the primary usergroup. If you don't want to edit that, you can make everything work fine by changing usergroup settings.

For Super Moderators use the settings:
Primary Usergroup: Moderators
Display Usergroup: Super Moderators
Additional Usergroups: Super Moderators

As long as the primarary usergroup is moderators, everything in the hack works fine. Your Super Moderators will still be displayed as Super Moderators and have Super Moderator permissions doing it this way.

Yeah, that's a good idea. But would they be able to warn moderators and not be warned by them? I guess not, since the protected groups are all treated the same.

Oh well, if I find the time, some day, perhaps. But I guess if this is added, then I'll have to spend some time coming up with proper documentation of changes, compared to the standard release, and maybe release the whole thing as a new hack, with thanks to the original author, Zero Tolerance, of course.

Rgds
-----------
John

[beano33]

Originally Posted by sv1cec

Yeah, that's a good idea. But would they be able to warn moderators and not be warned by them? I guess not, since the protected groups are all treated the same.

I tested that out. It works fine this way regarding protected usergroups. The problem I was having was that only mods and admins could view warnings anywhere, and I really didn't feel like going through the whole thing again to fix the conditionals for supermods. Since I only have a handful of supermods, this was an easy way to handle it.

Oh well, if I find the time, some day, perhaps. But I guess if this is added, then I'll have to spend some time coming up with proper documentation of changes, compared to the standard release, and maybe release the whole thing as a new hack, with thanks to the original author, Zero Tolerance, of course.

You might want to inquire about vBulletin's plans to release their next version so you don't end up doing a lot of work that may have to be modified. For all we know the next version may include a warning system.

[sv1cec]

Originally Posted by beano33

I tested that out. It works fine this way regarding protected usergroups. The problem I was having was that only mods and admins could view warnings anywhere, and I really didn't feel like going through the whole thing again to fix the conditionals for supermods. Since I only have a handful of supermods, this was an easy way to handle it.



You might want to inquire about vBulletin's plans to release their next version so you don't end up doing a lot of work that may have to be modified. For all we know the next version may include a warning system.

This whole issue of updates is really making me nervous. I am still at release 3.01, because I have made so many mods to my files/templates etc. that I do not dare to upgrade, I would hate to go through the same process again. Is there a list of files which shows which have changed between 3.01 and 3.03? Just thinking that this can occur every six months, when vB is releasing a new release, makes me crazy. I think I'll stick with 3.01, until something major is done.

As for your suggestion for the supermods, it is indeed very nice.

Rgds

[beano33]

Originally Posted by sv1cec

This whole issue of updates is really making me nervous. I am still at release 3.01, because I have made so many mods to my files/templates etc. that I do not dare to upgrade, I would hate to go through the same process again. Is there a list of files which shows which have changed between 3.01 and 3.03? Just thinking that this can occur every six months, when vB is releasing a new release, makes me crazy. I think I'll stick with 3.01, until something major is done.

I asked one of the vB people this in mid-September before I upgraded from 3.0.1 to 3.0.3 and was told it would be at least a few months before the next version and that I should update then unless I have a lot of custom programming in PHP. There's a list of file changes in the announcements forum at vbulletin.com. I was able to upgrade with only one major problem due to a search hack that we installed that modified search.php. vB changed it's search so if you have any search hacks installed, it's liable to conflict, so it's best to remove it before you start. The other issues just involved redoing the templates we had modified (postibit legacy, navbar, and a few I can't remember). It was simply a matter of saving the templates we had modded as text files and pasting them back in. They all worked fine with the upgrade. Custom templates and custom php files weren't affected.

[rex_b]

Originally Posted by sv1cec

As I said before, I liked the idea of a covered warner, so I did some changes in the database and the files/templates to make it a "consistent" feature of the hack. A text file is attached here, with the required modifications.

I hope you enjoy it.

While doing this, I also discovered a strange behaviour, in the Warning Options section of AdminCP. So, I changed the code a bit to correct it. The changes you should do, are described in the second attached file. All those who have implemented my "Allow multiple warnings for the same post?" option and the "Send PM to the warned member?" option, should do these changes, or else these features will not function properly.

Sorry for any inconvenience.

Finally, since the Warning Options part of AdminCP is getting a bit large as it is (it shows both the warning options, the defined offenses and allows you to add a new offence), I decided to separate them a bit, in order to make things more manageable. A third file is attached, which explains how to separate the Warning Options from the Warning Types.

I hope you enjoy.

Rgds
-----------
John

my templates look nothing like you ones you posted

[sv1cec]

Originally Posted by rex_b

my templates look nothing like you ones you posted

What version are you running? This whole thing is based on 3.01, but should work on later releases.

Rgds

[rex_b]

Originally Posted by sv1cec

What version are you running? This whole thing is based on 3.01, but should work on later releases.

Rgds

I'm using zero tolerances version and I didn't know there was another version within this thread. that's the problem I have.