Version: 1.3, by Zero Tolerance
Developer Last Online: Nov 2023
Version: 3.5.2
Rating:
Released: 08-04-2005
Last Update: 01-07-2006
Installs: 564
DB Changes Uses Plugins Template Edits
Additional Files
No support by the author.
Well this was created purely for my own self and staff needs, but i'm sure you guys and gals will need a warning system to keep control over any member that doesn't wish to follow your rules.
The previews pretty much tell you all the features available, one that isn't shown is that the graphical representation of warnings will be displayed in a members profile, so that you may warn members via their profile or post(s).
v1.1 Updates:
- You can now enter a "Reason To Show User" input, this message is shown for users who are banned.
- Minor gramatical error in the ACP options.
v1.2 Updates:
- Missing template added (minor)
- WOL Fixed (minor)
- Unable to warn user via profile more than once if warn duplcation was not allowed (high)
- Ability to remove warnings
- ACP option to allow/disallow staff to remove warnings
- Warn log stretched page if it was large
1.3 Updates:
- Bug Fix: Warning points to be given were not consistant with maximum points allowed (the drop down menu went from 0 - 10 no matter what)
- Bug Fix: Those who cannot recieve PMs (either via turning it off themselves or due to other permissions) resulted in an error when you tried to warn them, this no longer happens but the PM will not send.
- Added new flexible warning expirations 'Hour' (Allows you to make the warnings expire in hours aswell as days/months)
- Added extensive flexible ban times (Now allowed to ban a user for x hours/days/months)
- Added post modifier notice (Allows the staff member to automatically add a notice to the top of the users post, allowing others to see that the post was warned)
Enjoy
- Zero Tolerance
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
you want to open the postings that are warned from within the warning log and not the thread, in which the warned posting is?
Code:
look in template warn_log_row for:
<td style="white-space:nowrap;"><if condition="$Log[w_post] > 0"><a href="showthread.php?$session[sessionurl]p=$Log[w_post]">$vbphrase[review_post]</a><else />N/A</if></td>
replace it with:
<td style="white-space:nowrap;"><if condition="$Log[w_post] > 0"><a href="showthread.php?$session[sessionurl]p=$Log[w_post]#post$Log[w_post]" target="new">$vbphrase[review_post]</a><else />N/A</if></td>
if you wanna have it openend in a new window showing the posting in the thread it was done.
replace it with:
<td style="white-space:nowrap;"><if condition="$Log[w_post] > 0"><a href="showpost.php?$session[sessionurl]p=$Log[w_post]" target="new">$vbphrase[review_post]</a><else />N/A</if></td>
if you wanna have it openend in a new window showing only the posting.
remove target="new" if you want to open in the same window as the warning logs.
looks quite nice, even though I didn't install yet....
What I'd really like to see is an option to scan registrations for doubles.
There was that Hack for vB2, called 'Who might this new user be' which checked several registration infos against the user database. One of the features was the ability to check the passwords - I think most of the double registrations we caught back there in vB2 were because of similar passwords - and it calculated a percentage rate of how suspect this new registration was.
As this hack seems to be a bit alike the old functionality would just fit greatly into it. So you could a) have the current features of this hack and b) check if banned users are registering again to continue their bad behaviour.
That would keep lots of them out - talking experienced
Hi there - I have installed and it works great. I did notice however, that if the user has PM turned off, the following error is generated when you 'Warn'
Fatal error: Unable to proceed with save while $errors array is not empty in class vB_DataManager_PM in \includes\class_dm.php on line 758
What would be wonderful, of course, is to have the system email the user instead
Works great otherwise - thanks for releasing this.