Tags: blog, wordpress, security, plugin, comment, comments, anti-spam, antispam, spam, spambot, spambots, protection, user, users, template, secure, h …
There have been many new good ideas of fighting automated Spam in WordPress. Most of these Plugins (like the antecessor of NoSpamNX: Yawasp) change the name of one (or more) of your comment field. On the one hand, this is indeed more effective, but on the other hand, this goes to the expense of compatibility. Therefore, NoSpamNX does not change any of your comment fields, but still claims to be very effective.
NoSpamNX automatically adds additional form fields to your comment form, invisible to human users. If a spambot fills these fields blindly (which most of all spambots do), the comment will not be saved. You can decide if you want to block these spambots or mark them as spam. Furthermore, you can put common spam-phrases on a local Blacklist or (if you have multiple Blogs) on a global Blacklist. This comes very handy when fighting against “handmade” Spam.
NoSpamNX works best with a WordPress default theme (e.g. TwentyEleven, TwentyTwelve, etc.)
Make sure your theme loads
comment_form in the Comment-Template (comments.php) according to the WordPress Codex – see http://is.gd/1lezf – otherwise NoSpamNX will not work properly!
The best way to deal with this Problem, is to uninstall the Plugin via the WordPress Backend and re-install the Plugin.
Update to at least Version 3.14. Since this Version the Options are not rested when the plugin is updated.
NoSpamNX does not work with OpenID.
NoSpamNX does not work with BuddyPress.
Yes, but you have to activate the plugin for each site individually.
Yes, just add an IP-Address (e.g. 10.23.23.4) in the Blacklist or use CIDR-Notation (e.g. 10.43.8.67/28) to block IP-Ranges.
No, the plugin focus on automated Spambots only and I have no plans of changing that. There are some really good Plugins in the WordPress Plugin Repository which can do that for you.
Due to the functionality of NoSpamNX false-positives are nearly impossible. There ‘might’ be problems when using WordPress Cache-Plugins, but none have ever been reported. If you are uncertain, mark Spambots as Spam instead of blocking them.