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.
I tested this function out, I went to another, created a user (test) and made a post, then I went to my main computer, logged in as Administrator, open the post, clicked on the spam button, on the next pace, when I clicked the decimate button Iget this error?
Fatal error: Existing data passed is not an array
Called set_existing in /home/lukemax/public_html/forum/includes/functions_databuild.php on line 164
Called build_forum_counters in /home/lukemax/public_html/forum/includes/functions_decimator.php on line 107
Called move_spam_threads in /home/lukemax/public_html/forum/decimator.php on line 176
in /includes/class_dm.php on line 235
Am I missing something?
I had the same problem and fixed it by changing the default setting of 1 in the "Threads moved to Forum" setting to a real forum. In my case I set up a spam forum as a child forum in the moderators forum. Changed the forum id from 1 to 73. Now SD works as advertised. Thanks a million for this mod. Life just got that much easier. :up:
suggestion: when doing the ip address scan also display postcount and usergroup (banned?). this would make it easier to identify ips that are used for spamming only
Hey, I've been using this a while and it's great. Just now setting it up on 3.6.4 which I've just upgraded to, not sure if it will work yet, but I wanted to ask:
Is there some way to keep the spam button from showing up on users with at least X posts? Most spammers we kill off have only ~20 posts max, so I set up a conditional:
But there is a problem - the spam button shows up on people with under 80 posts, and also on people with over 1000 or so. I'd rather not have the chance that one of our 1000+ posters would get accidentally decimated by a drunk mod, because it would be a serious pain to fix. Is there a good way to do this so the button only shows up below X posts?
Thanks for all your work writing this, it's saved us a ton of time.
Anyone come up with a workaround for this yet? Ive twice had a mod nuke the wrong member this week and had to go through and manually undelete all the posts. I'd hate for a member with +1000 post count to get nuked by mistake.
We had a problem with this plugin inserting the nofollow tags when a user passed the 1,000 post mark. The problem was a comma inserted into the number of posts (e.g. 1,000). We fixed it by changing this line in the plug in:
PHP Code:
if (is_member_of($post, 5, 6, 7) OR $post['posts'] > 50)
to this (which strips the unwanted comma from the post count):
PHP Code:
if (!(is_member_of($post, 5, 6, 7)===FALSE) || str_replace(",","",$post['posts']) > 50)
I haven't tried it yet, but plan to tonight or tomorrow.