Hey guys... sorry I haven't replied in a while. Moved jobs + a new baby and I've been insanely busy...

Before the month is over I will try and code a new version that addresses everyone's requests...

Welcome back! :)
If your not busy any more, please try to add the following:

Suggestions:
Allowing us to enter a ban reason in the settings of the AdminCP.
Option to disable site viewing. (Simply blocks the user from the site.)

congrats on the new job and baby

cool to see this imrpoved a bit more, it nearly perfect as it is. Just cut down the work if it ran the check after all the other checks are passed. Also put less strain on the database


since incorpating nospam and this addon we not had any spam

can anyone running nospam check the plugin and see where it hooks and what # its running at?

<hookname>register_addmember_process</hookname>

it use multiple hooks as it protect multiple areas.

on area it also protect unless the person has signed in in the contact us page.

Any chance this program protecting that as well.

Damien

any many thanks

There should also be an "Execution Order" # on that page...

Well, what started as a 5 line hack has - IMHO - reached the point where I think the feature set is quite significant.

I have fixed -
. reporting errors.
. the post IP = blocked IP issue (it is now 1.2.3.4)

I have made the following feature changes -
. added ability to specify error message someone sees when blocked.
. added ability to specify the group to add banned accounts to.
. added ability to specify a reason for being banned.
. added ability to specify a custom title for banned users.
. added the ability to place users in COPPA Users Awaiting Moderation queue - or another moderation queue.
- updated reporting to reflect new features.
. changed adminCP options order / titles / etc. to clean things up.
. changed the RBLs - # used, order, etc.

Basically, as I am testing it, out of the box the configuration will be:

Allow users to register, do not ban them, but place them in the moderation group.

If you enable banning it will automatically skip the moderation part.

If you choose to block registration it will never get far enough to mod/ban because the account isn't created.

I've finished those dev changes and am testing - I still need someone to tell me the hook order for those other hacks so I can have the checker fire AFTER they do... otherwise I should be uploading a new file within the week.

<plugin active="1" executionorder="1">
<title>Check if NoSpam! question has been answered correctly</title>
<hookname>register_addmember_process</hookname>

the plug in also covers searchs
new post by un reg users
searches by un reg users
contact us by un reg users

if you need any of the hooks for those or other hooks in nospam let me know and i will do my best

Just to clear this up - it does.

The hook of the plugin (there's now actually 2...) so the hook of the RBL checking plugin is at register_addmember_process... This is to allow blocking of registration. If you don't have blocking turned on then the first plugin still does the check and generates notifications...

The 2nd plugin needs to fire after the new member has been added to the DB so it runs at register_addmember_complete. Depending on the options selected it either bans or flags the new member for moderation.

Thanks for the update!
Edit: Is there a way so that it will completely block them out? Even from the home page? So, that they have no access whatsoever? (Like, as soon as the user comes on the website, it will check the IP) Or is that just too many queries?