I completly rewrote the mod banning system and added an admin banning system as well.

[Rose]

Very nice.

[Dean C]

Lmfao Slynderdale. Your a legend i swear. Where do you get all the time to do this and not email me my little mini-hack hehe This looks awesome though - it really does! I hope you released it before vb3

- miSt

[Erwin]

I have also extended the vB banning system, with a complete integration of the warning system, suspension system, banning system and reporting system, all based on points. It's all automated as well - just click a button, and points are removed, PMs and emails sent, and usergroup changed.

[sparky2]

Atop this thread you asked "How do you like it?"
The interface is beautiful, but the "reason" field is way too small to be practical. Needs to be datatype mediumtext, with a textarea form field in the editing interface.

What's the context of your interface screencaps? AdminCP--}EditUser
???

FWIW, I hacked something less elegant & had to rework it 4-5 times to suit our moderators. One of the things they asked for was to have "Ban Duration" reported. That way, the earlier incidents can serve as precedents. By referring to past disciplinary actions, they can see what "timeBan" duration is appropriate (and be consistent in their enforcement of the forum rules).

I'm tempted to just chuck the script I wrote & go with yours.
I had just added fields to the user table, so each new time-based ban for a particular user overwrote the data from previous "incidents". I'm not keen on the idea of having six selectboxes required to set the date; in our implementation, a moderator just types a decimal number (can be 0.1) into a textbox to indicate the time (in hours) they want to assign for the temporary ban.

Two other suggestions for you:
First, the Report (grid) should include the DATES of previous bans.
If a person was warned before for the same behavior
(a moderator may not even know about it; may have been a different mod earlier) knowing whether the warning was issued last week or last year is an important piece of info.
----------
Second, it would be really helpful if the report had two "views":
current bans in effect, and all bans ever issued (dateline DESC)

What really motivated me to post to this thread was wanting to discuss banning, in general. It's a losing proposition & just becomes a cat-and-mouse game between the habitual troublemakers and the moderators.

The vBulletin developers factored in a "moderate new posts" permission setting, but it's not flexible enough (and too time-consuming to manage). Instead of forcing all posts in a particular subforum to require moderation before being publicly visible, or having to "reassign" a user into a different usergroup, for which "posts require moderation"...

maybe we should tie this into the Time-based "banning" feature, so that when a user gets a "formal warning", his account is tagged "posts require moderation" for the specified "ban" period... and afterwards, (automatically, once the dateline for the ban is exceeded) the account tag allows posting but keeps the member account on a "watchlist" for moderators.

Maybe?

[Slynderdale]

Originally posted by sparky2
Atop this thread you asked "How do you like it?"
The interface is beautiful, but the "reason" field is way too small to be practical. Needs to be datatype mediumtext, with a textarea form field in the editing interface.

What's the context of your interface screencaps? AdminCP--}EditUser
???

FWIW, I hacked something less elegant & had to rework it 4-5 times to suit our moderators. One of the things they asked for was to have "Ban Duration" reported. That way, the earlier incidents can serve as precedents. By referring to past disciplinary actions, they can see what "timeBan" duration is appropriate (and be consistent in their enforcement of the forum rules).

I'm tempted to just chuck the script I wrote & go with yours.
I had just added fields to the user table, so each new time-based ban for a particular user overwrote the data from previous "incidents". I'm not keen on the idea of having six selectboxes required to set the date; in our implementation, a moderator just types a decimal number (can be 0.1) into a textbox to indicate the time (in hours) they want to assign for the temporary ban.

Two other suggestions for you:
First, the Report (grid) should include the DATES of previous bans.
If a person was warned before for the same behavior
(a moderator may not even know about it; may have been a different mod earlier) knowing whether the warning was issued last week or last year is an important piece of info.
----------
Second, it would be really helpful if the report had two "views":
current bans in effect, and all bans ever issued (dateline DESC)



What really motivated me to post to this thread was wanting to discuss banning, in general. It's a losing proposition & just becomes a cat-and-mouse game between the habitual troublemakers and the moderators.

The vBulletin developers factored in a "moderate new posts" permission setting, but it's not flexible enough (and too time-consuming to manage). Instead of forcing all posts in a particular subforum to require moderation before being publicly visible, or having to "reassign" a user into a different usergroup, for which "posts require moderation"...

maybe we should tie this into the Time-based "banning" feature, so that when a user gets a "formal warning", his account is tagged "posts require moderation" for the specified "ban" period... and afterwards, (automatically, once the dateline for the ban is exceeded) the account tag allows posting but keeps the member account on a "watchlist" for moderators.

Maybe?

Hmm, real good ideas, ill implement them with my current hack before release, especaily the previous ban records, Instead of adding the data to the ban list in the screen shot above, ill make the total ban count a link that opens a window to show all detailed ban data for that user.

[filburt1]

Looks nice but FYI the mod CP of vB3 pretty much has the same features now.