That being said, this is a slightly more powerful 3.5 version of that rewritten from scratch.
Features Include:
-Ban a spammer with two clicks.
-Delete all threads by a user (soft or permanent, ACP configurable)
-Delete all posts by a user (again, soft or permanent, choice is yours)
-Permit or deny mod/super mod access through ACP
-Email the spammer saying pretty much haha, caught you sucker (default email can be configured using ACP)
-Email the webmaster informing him/her of the attack
-Option to move all soft deleted threads to a specified forum (for safe keeping in case IP addresses or whatnot are later needed for legal proceedings or whatever)
Most everything here works with vB native functions (i.e. delete_thread, etc.), so forum, thread, and post counters are automatically updated.
Install
Installing is quite simple. Simply upload the included files (three of them, decimator.php, includes/functions_decimator.php, and images/misc/spambutton.gif) preserving hierarchy, do precisely ONE template edit (a copy and paste job if there ever was one ), and import the product file, and voila! you're done and ready to take on any spammer who comes your way.
Other Stuff
**UPDATED!!!
Spam Decimator 2.0.0 is slated for a late June 2008 release, with a features list to follow.\
Spam Decimator 1.5.1 for 3.7.x is posted as a vB 3.7 add on.
Thanks to everyone here at vB.org for being a fine community to be a part of. Thanks to Marco for helping me out in one of the changed variables for 3.5 threads, really helped a lot . Thanks to my staff over at Pigskin Heaven for putting up with me while I was working on this.
That's basically it. Enjoy, and as always, click install
Changes:
1.0.1 - Fixed problems with xml product file, validated for use with vB 3.5 Gold release.
1.0.2 - Fixed mod/super mod access bug as well as fixed templates for non-vB default styles.
1.0.3 - Fixed all known remaining bugs, rewrote email system to properly parse emails using native vB functions.
1.0.4 - Attempted to fix bug I can't find...updated main template.
1.0.5 - Fixed no mod access bug.
-RD
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
That function, shocker, rebuilds the forum counters. Any idea why that'd be acting up? It's a native vBulletin function...
BTW, I will be working on a version 2.0 with all of this stuff cleaned up and a few new features this week, basically a rewrite of the original code with a lot more options added as well as a couple of planned new features. The following NEW features are IN at the moment, and I am open to suggestions:
-Start new thread in forum X when Decimator is used
-Multiple usergroups per permissions level (i.e. more than one mod group can be used)
-Better email message to webmaster (currently only the user who used SD is in there)
-Option to not allow use on a user with more than X posts, or to protect certain usergroups from use within the script (previously only done within the template).
Again, open to more suggestions...
-RD
of course the problem is not with the function :P but is how the function is used... i think when you set the option to move to a forum to NO, it uses the function with no content, like build_forum_counters() so it gives you an error...
or maybe when the user set the forum number to an unexistent forum, it crashes the function
Hello,
one of the original options I suggested for the original incarnation of this hack would be to show some information about any users which share the IP address of the spammer. Specifically their user name, their user group, and if banned, their banned reason.
The current version shows any IP matches that may occur, but it only shows their usernames. I can change that if you like, however, the banning of IP's would be a little tricky due to that way that variable is stored...
The current version shows any IP matches that may occur, but it only shows their usernames. I can change that if you like, however, the banning of IP's would be a little tricky due to that way that variable is stored...
-RD
More information would be good. AT least then we can see at a glance if it's a re-offender and then go in and do the business on their IP.
I use to get timeouts (under large forum) when apply decimator to some user with more than 10 or 20 messages. (Checks ON: ban user, delete threads, delete posts. OFF: ip check, email webmaster)
Tried to fix adding this to decimator.php, but isn't working:
@set_time_limit(0);
A little bit of an update, I've hit the hell quarter in my computer science program, so release of 2.0 is tenatively slated for mid July '06, by which time I should have had enough time to fully test the new features.
BTW, this also means that I'll still be able to take feature requests until about mid June. For the current feature list for 2.0, scroll up a few posts to about 88 or so