Moderators Functions - One-touch Spam Ban and Cleanup

*** Staff note: The author of this modification has passed away in a diving accident. We wish his family all strength in dealing with this tragic issue. ***

One-touch Spam Ban and Cleanup




The main purpose of this mod is to clean up after a spammer. With a minimum of fuss it will:

• Delete all threads started by the spammer
• Delete all posts made by the spammer
• Delete all PMs sent to other members by the spammer
• Delete all calendar events made by the spammer
• Ban or delete the spammer as you like
• Ignore permissions - posts can be deleted in areas that a moderator may not have access to.

The option to activate this tool appears in the drop-down menu in the postbit, as well as on the profile page. From here it is a "one-touch" operation, with the small exception that you must press a confirmation button before the cleanup is made.




See the screenshot for the various options, but some of the more interesting ones are:

• You can specify individual users (in addition to groups) who can use this tool. This means certain trusted, non-moderator users could have the ability to clean up spam and ban spammers.
• You can specify users or groups who are protected - they cannot be deleted by this tool.
• By default, users who have registered more than 30 days ago are also protected from this tool (spammers tend to be caught and removed fairly soon after registration)
• You can turn the various deletion targets (threads, posts, events, PMs) on or off
• Select between hard delete or soft delete

This mod is similar to some older mods, but improved in a number of ways:

• You also have the choice to alter the standard ban and delete reasons before you press confirm.
• Deletes more types of spam (PMs, events)
• Simple, quick, effective
• Single file import (.xml) no file edits, no template edits, no .php files to upload
• Should work on all versions of 3.6.x and future versions

Installation

Download and import the .xml file via AdminCP -> Plugins & Products -> Manage Products -> Add/Import Product. Remember to click overwrite if upgrading

Configuration

Once installed, check in your AdminCP under "VBulletin settings" and look for the configuration group called "One-touch Spam Ban & Cleanup Options". The default options should be fine for most people.

How to use

If you have rights to use this tool (i.e. are an admin or moderator, or have configured it for the relevant user or group ID) you should see the option appear on the member profile page, or in a drop-down on the postbit (see attached screenshots for an example). The idea is that as soon as you see a spammer select the "One-touch Ban & Clean" option to remove all trace of the spammer.

Support




Support will be given to those who have:

• Read these instructions (and followed them) and
• Clicked install

Version history

1.0 - initial version (28.08.2007)
1.1 - security fix (21.09.2007)
1.2b - Beta Fix to work with vb3.7.0 (20.05.2008)

[AdrianH]

Originally Posted by nova4708

I tried using this on a spammer, and it said it was going to use the action against MY ADMIN ACCOUNT! It was trying to delete the ADMIN, not the SPAMMER!

I'm using 3.7

I would not recommend this product!

Don't see how that is possible as it will only point to the user id that you have chosen.

I tested this today by creating new 5 users and adding some posts by each of them,it worked perfectly every time.

Providing you add the template edits for v3.7 listed in this thread there should be no problem.

[cash7c3]

So after a recent upgrade to 3.6.10 this tool no longer works. I have tried uninstall, reinstall, checked for security token, etc etc and I always get this message.

This user is protected. You may not use this tool on this user.

any ideas or suggestions?

[Gersfan]

It's not working on my profiles or dropdown box either,

Any Help?

I'm using 3.7

Thanks,

[AdrianH]

Originally Posted by Gersfan

It's not working on my profiles or dropdown box either,

Any Help?

I'm using 3.7

Thanks,

The answer is already given in this thread at least 3 times, you need to add the security token and edit a template.

[AdrianH]

Originally Posted by cash7c3

So after a recent upgrade to 3.6.10 this tool no longer works. I have tried uninstall, reinstall, checked for security token, etc etc and I always get this message.


any ideas or suggestions?

Read back through this thread ,the answer is given by a few members already.

[tekguru]

Working fine for me in 3.7.0 so far.

[cash7c3]

Originally Posted by CareyCrew

Read back through this thread ,the answer is given by a few members already.

didn't i say that i'd added the security token?

PHP Code:

<input type="hidden" name="securitytoken" value="$bbuserinfo[securitytoken]" /> 


thanks for the suggestion though, I read back through 16 pages and haven't found the source of my problem

[fib]

I dont want to claim I am right but if the user is protected it is pehaps because they are part of a group that is or that they have made enough posts to be beyond the number of posts it is relevant for - or is that another tool I use?

just thoughts no time to check now but can in a few hours if you still have an issue

[Gersfan]

What's the sercurity token fix?

I've made the template edit alright,

[cash7c3]

Originally Posted by fib

I dont want to claim I am right but if the user is protected it is pehaps because they are part of a group that is or that they have made enough posts to be beyond the number of posts it is relevant for - or is that another tool I use?

just thoughts no time to check now but can in a few hours if you still have an issue

usergroup trying to ban isn't protected, disabled the maximum time. no luck, completely stumped on this one, no idea why it stopped working. even gone as far as manually installing instead of installing from xml, same thing . . . thanks for the suggestions

edit fixed
somehow after upgrade ended up with two onetouchban templates -- one in the normal location after new posting templates and the other in custom templates section. Got rid of the double now working fine in case anyone runs into the same prob