What is the maturity period for those warnings? Do you have a maturity period in your warnings?

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

Hrm, don't have anything that allows me to set that. What tables / modifications would need to be added / made in order to get that to work? Didn't see it anywhere else in this thread.

Since this thread is getting quite long, and there are several posts with replies I gave to users, based on my modifications of this excellent hack, and after being prompted by a fellow member here, I spend a whole night, putting down some notes to explain what my version of the hack does.

Unfortunatelly, when I was making those changes, I didn't kept a log, so it is not possible to provide step-by-step instructions. Also, it is not possible to implement one feature and leave out another. The whole thing is offered as a ... packaged deal, LoL.

Please be patient, remember that last night I slept only one hour, preparing these things and making the code more "public", until yesterday, it was only for internal consumption.

OK, hopefully when this message is complete, there will be several files uploaded. These are :

1. mymods.txt - a text file describing what my mods do, in addition or in difference to the original hack (even version 1.5, which should be installed before starting to change things). This file contains also the description of the tables that my mods use. IT DOES NOT CONTAIN STEP -BY-STEP INSTRUCTIONS ON HOW TO MODIFY THE TABLES, IT JUST SHOWS YOU THE TABLES STRUCTURE.
2. Warn.php - my version of Warn.php
3. admin_warn.php - my version of the file, this one should be uploaded into your admincp directory.
4. kill_warns.php - a cron script to automatically delete warnings, whose maturity period has been elapsed. This should be uploaded into your include/cron directory and activated from the "Add New Scheduled Task" in your AdminCP. Make it so it is run once a day. My settings for that are:
Title: delete_old_warnings
Day of the week : *
Day of the month : *
Hour : 3
Minute : 3
Log Entries : Yes
File : ./includes/cron/kill_warns.php
5. templates.txt - a file which contains all my warn-related templates. Some of them may be the same as the ones of the original hack, but since I do not know/remember which ones I've modified, I included them all. It also contains instructions, on how to modify the postbit and the postbit_legacy templates. If you have some of the warn templates already, make sure they contain my code. If some of the templates I list, are not in your system, you have to create them.

One more thing I remembered, as I finished this: Since I am not using the table that the original hack had for the banned users, the "Unban User" option is no longer available. I let vB cron job do the unbanning. Please test it though, because I am not sure how well it works. For example, in my hack, when a user is banned, his original user group id is maintained in the userban record, in order for it to be restored when the member is unbanned. I am not sure if this works though. Let me know.

Added Friday Oct 8th Evening:

If one is to allow multiple warnings for the same post (for various offences obviously), the person issuing the warning, should be able to see what other warnings were issued for this post. So, I edited Warn.php a little, and a couple of templates. The changes are reflected at the files below.

Added Saturday Oct. 9th morning:

I forgot to mention that the Warning Points a user has received, are also shown in his profile. So that brings the total number of templates you have to edit to 20!!!!

I guess this is the best I can do to describe how I customized this beautiful hack, to make it more suitable to my needs. Credits should all be given to Zero Tolerance for the hack, all I did was lots of trials and (a whole lot more) errors.

I'll try to help anyone who has issues, but I cannot guarantee it guys, there are two 2.5 years-old boys in this family, and this can be a really messy situation.

Regards

----------
John

Absolutely wonderful, sv1cec! Thanks for the hard work, implementing these changes now. :) One question, is the maturity period a day variable? Meaning, if I wanted a warning to expire in 30 days, the maturity period would be set to 30?

Yes Sir, it is on a day basis, so for 30 days you enter 30.

Rgds
---------

John

My queries for the warning options are just not working. I'm trying to update from the original warning hack to the 1.5. Could anyone write something up real quickly for phpmyadmin that will delete the current warning options and readd the table with the necessary rows inside? I've spent 24 hours and I just can't seem to get it to work properly :(

Not sure if you got my email, John, but the warn maturity feature doesnt seem to work. I set one to be removed after 2 days. I even waited that long but didnt seem to have removed it.

M1th,

Please check that you have everything as described in the files a couple of posts above.

It seems it's working OK in my forums, so I am not sure what's the problem. Please check everything again.

And no, I haven't got any e-mail from you, sorry.

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

Could you make it possible for the next release to add warning permissions by usergroup? That would help so only mods, supermods and admins could warn users.

If I recall correctly, there actually is a hack for this somewhere in this thread.