Anmerkung: diese Seite gibt es auch in Deutsch.
Note: If you have used Yawasp before, it is inevitable that you undo the changes in your comments.php. You can find appropriate instructions here.
1. Functionality
2. Installation
3. FAQ
4. Versions
5. Details
6. Translation/Feedback
7. Download
8. Donate
1. Functionality
NoSpamNX is the successor of Yawasp (Yet Another Wordpress antispam plugin) and is a plugin to protect against automated comment spam (spambots). While Yawasp changed the names of the form fields in the comment template, NoSpamNX works without these modifications, but is equally effective. By eliminating the need for modifications the form field need maximum compatibility with other WordPress plugins or browser is ensured.
When calling the comment form NoSpamNX adds extra fields (hidden before the “normal” user) automatically to your comment template. When a comment is saved, these fields are checked. For additional protection, the order and the values of these fields change periodically, so that no spambot can adapt to a specific blog adapt.
Now the user must no longer fill out any additional fields in the comment form, and you can focus on blogging and your readers comments.
NoSpamNX is a real lightweight. It does not need JavaScript, Cookies, Sessions or modifications on your template, but still is very effective.
- Unzip Plugin
- Copy the nospamnx folder to wp-content/plugins
- Activate plugin
- Feel free to adjust settings (WP-Admin -> Settings -> NoSpamNX)
3. FAQ
When i activate the plugin, the hidden fields are visible!
Make sure that the template you are using calls wp_head() before the closing HEAD tag (). See http://is.gd/tazh for more information.
What is the difference to other anti-comment-spam plugins?
Spambots are stopped within the plugin. You don’t see them and most important you don’t have to moderate them!
Does the plugin block Ping-/Trackback Spam as well?
No, the plugin focus on automated spambots only.
What about false-positives?
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, try puting catched Spambots in moderation queue or mark as Spam.
4. Versions
See Changelog.
5. Details
The plugin does not block track- and pingback spam.
6. Translation/Feedback
The plugin contains German and Englisch language support. I’m glad to add more languages. The .po file is included in the plugin and need to be translated accordingly. Send the new translation to nospamnx AT svenkubiak DOT de. This address is perfect for any feedback. Of couse, you can use the comment function on this page as well.
Download from Plugin Repository
If this plugin saves you as much time as me, you can donate to support the work. Thanks!
Es ist richtig, dass die Einstellungen...
It seems broken. The extra fields are visible, and I had to add custom css to make them invisible.
@freespace
Didn’t had Problems with the CSS so far. Which Browser did you use? Do you have an example Page where i can take a look at the broken code?
Existe una versión en español? Do you have an spanish version?
@MAN
Spanish translation is available since version 1.3
Just wanted to note that the style sheet which hides the extra fields will not be linked unless your template calls wp_head() or you link to it manually. Seems kind of obvious, but it took me a few minutes to figure out. An extra bit for the readme, perhaps?
@joshua
Thanks! This explains why some users reported that the hidden fields were displayed! I will add this to the FAQ
Hi Sven, how you doing? I use wordpress 2.6 and the theme I’m using (3k2redux klee) does have the wp_head function (no additional comment field is visible on the comment section). However, I keep receiving spams on my comment panel (in my admin page) while the counter NoSpamNX does not increase (no other anti-spam plugin activated). In addition, when I have Akismet activated at the same time, Akismet does catch new spams (it adds them to the “Spam Akismet” comment subpage) while NoSpamNX does not increase its counter (meaning it did not block none of these new spams). To give you some statistics, while the Akismet detected about 900 spams (99% real spams indeed) the NoSpamNX counter is about 50. Is there any particular reason for NoSpamNX to not work properly? (I’m using the default settings for NoSpamNX). Thx, Leo.
Hi Leo,
as the default options from NoSpamNX block Spambots i am wondering how Spam does get into you Spam queue? However, i have the same effect when using Akismet and NoSpamNX actiaved at the same time. As Akismet does block some Pingback Spam, NoSpamNX doesn’t. This increases the Akismet Counter while the NoSpamNX counter stays the same. There might also be some Spammers that but Spam into your blog manuelly. This Spam gets also catched by Akismet (sometimes).
Still, the really interessting thing is, how you get Spam in your Spam queue while NoSpamNX is operating in “block mode”. Are you sure there is no other Antispam-Plugin activaed?
Sven
I don’t have any spam queue actually. If NoSpamNX blocks a spam I can’t see the spam (i’d like to, just to take a look, but I think it is not possible), while if it is not blocked I see it in my comments queue naturally. By the way, if I choose “Mark as Spam” where does the spam goes, where I see it marked as spam (if I don’t have Akismet activated)? I don’t have any other anti-spam plugin besides yours and Akismet.
So, if I understand you well, you are saying that if NoSpamNX is active and Akismet not, the only spams I’m supposed to still receive in my comment queue are the spams made manually? Regards, Leo
@Leo
[...]So, if I understand you well, you are saying that if NoSpamNX is active and Akismet not, the only spams I’m supposed to still receive in my comment queue are the spams made manually?[...]
Besides Ping- and/or Trackbackspam, yes!
[...]By the way, if I choose “Mark as Spam” where does the spam goes, where I see it marked as spam (if I don’t have Akismet activated)? I don’t have any other anti-spam plugin besides yours and Akismet.[...]
Sorry, i forgot. The Option “Mark as Spam” requires WordPress 2.7 – otherwise Akismet is required. Will put that notifiaction in the plugin when i release the next version.
cformsII (http://www.deliciousdays.com/cforms-plugin) on user error (empty field etc) will show the hidden fields if ajax is used.
to stop this change this
else
return str_replace ('</textarea>', '</textarea><input type="text" name="'.$nospamnx['nospamnx-2'].'" value="'.$nospamnx['nospamnx-2-value'].'" class="locktross" /><input type="text" name="'.$nospamnx['nospamnx-1'].'" value="" class="locktross" />', $template);
to this
else
return str_replace ('<fieldset class="cf_hidden">', '<fieldset class="cf_hidden"><input type="text" name="'.$nospamnx['nospamnx-2'].'" value="'.$nospamnx['nospamnx-2-value'].'" class="locktross" /><input type="text" name="'.$nospamnx['nospamnx-1'].'" value="" class="locktross" />', $template);
Nice pluggin. I like this technique, and may use it with some custom applications.
What about using this plugin on multiple servers?
With all writes happening on a master server and reads happening on slave servers. Is there a chance that the ‘keys’ between the front-end servers will be different than those on the write server?
If they are, than ALL submitted comments will be blocked.
@Ben
Do you mean using NoSpamNX with WordPress MU?
@Paul
But this would not add the hidden fields to your normal comment form anymore?!
Sorry, no – I mean that we have a blog serving off of multiple servers with a ‘Master’ server/database. So the plugin would be installed on multiple front-end servers, but would need to pass through the ‘Master’ plugin before being written to the database.
So my question is whether the keys generated on the ‘Slave’ servers would match the keys on the ‘Master’ server – if they don’t, then all submitted comments would fail the test as a result and would be blocked.
@Ben
Do the blogs have each a own table in the database or are the blog infos stored in one big database?
If every blog has its own database with its own options table, than it would definitly work.
Mysql master, where all writes are done – then replicated to the frontend servers – so front-ends are reading from identical data.
All writes are on the master.
@Ben
This should work as well. But due the replication all blogs will have the same values for the hidden values.
Thank you – and by the way – I am very impressed with the logic you are using.
Hello,
I installed it on wp 2.3.3 without problems.
Do you know if it works with 2.3.3 or you only haven’t tested it with 2.3.3?
Thanks,
JuliusB
@JuliusB
I did not test it with 2.3.3. and the current version uses hooks which are available since 2.1. But i might use hooks that are implemented in a later WordPress version in upcoming releases.
Thanks.
Another follow: I have noticed on a test install that the script is delivering a 500 error when it rejects a POST. Considering the amount of spambots that have hit the test system, this creates a lot of panic. With these ‘false’ 500 errors it looks like our server has a problem – so this would not be an acceptable side effect.
I am wondering if this is a problem with our deployment or with the script itself.
Thank you,
Ben
@Ben
I can reproduce this error sometimes when using Interner Explorer, but never with Firefox. However, i can’t reproduce this error every time, so i can’t pinpoint this problem to a specific function from the script. I *thik* this is a problem with WordPress and Interner Explorer. If you could help me out with some more detailed information (Browser, WordPress veriosn, etc.) i’ll take a deeper look.
I hope this is not too long of a string for you – here is some stripped logs:
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.0″ 500 500 “http://test.domain.com/?comments_popup=7208″ “Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
[ip] – - [date] “POST /wp-comments-post.php HTTP/1.1″ 500 500 “http://test.domain.com/?comments_popup=7715″ “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]”
I did not notice before, but Opera seems to be the predominant problem. We are using Version 2.6.5
@Ben
Thanks for the infos. I will have at look at it and get back to asap.
@Ben
I couldn’t reproduce the error with Opera (9.64), Firefox (3.0.10) or Internet Explorer (8). I found a solution for an Error 500 Bug, but it was for WordPress 2.7. Anyway, could you check if maybe PHP is running out of RAM.
I am not seeing any memory errors in the logs and there is plenty of memory on the machines themselves [8gb] and the only page generating the error is comment submit page. If I deactivate the plugin, the errors stop.
Side note, that may be relevant – the time-scheme for blocking IP addresses is missing in the admin area. In other words, we cannot set the time that a IP should be blocked for.
@Ben
From your logfile i’m guessing you are using comment with popup? If yes, does the error occur if you are using the “normal” comment form?
Could you pass me a screenshot concerning the ip addrresses?
Yes, this particular one is using a pop-up. I would rather not post the link in a public forum at the moment. I have noticed that almost all the errors are going to same post, but from hundreds of different IP addresses and with the same browser version – a bot no doubt.
@Ben
I impleneted the support for the comment popup recently, so there might be a bug. I will look into it.
@Ben
I think i found the problem and a solution, but i need to test it a little bit more before i can release it. For now, you might want to try the devlopement version at http://downloads.wordpress.org/plugin/nospamnx.zip – let me know if you still have problems with this version.
I am still getting the same errors on my test with the new software.
I have loaded the older version on another blog [with less traffic] without a pop-up comment and will look at the logs in the morning.
Thank you.
@Ben
I will try a new fix later on.
@Ben
Could you try the current development version at
http://downloads.wordpress.org/plugin/nospamnx.zip
Sorry i wasn’t clear enough about changing the replacement lines earlier
for it to work you need to change the comment.php in your theme to add an empty tag
I guess you could also use the cforms “wp commment feature” to manage comments and maybe not have to change you comment template – not sure since I don’t use cforms for comments just contact, survey etc
not sure if it would be worth hte time or trouble, but you could put a option setting in the control panel to be able to change the tag the replace function focuses on
@paul
I hope its okay, if i removed your comments except for your last one.
I added the feature to deactivate nospamnx on certain pages/posts. If you have a page/post with a form, just deactivate nospamnx on this page. No need to modify anything
perfectly ok to edit – I was really tired after a long day
I did notice the omit page/post thing but it is a case of i am just designing the site not using it and having the client pay attention to any page or post that he puts a form on needs to be omitted is probably asking too much of his little brain.
and it is not always a contact form (surveys etc) so comments need to be available also
great plugin btw
To those who still see the hidden fields but do have wp_head() loaded correctly:
I fixed this by checking the permissions of the /wp-content/plugins/nospamnx: it has to be executable. chmod 755 is the right one, worked fine for me.
Hello,
I use the all-in-one-seo plugin and after I installed and activated No SpamNX I noticed that all titles of posts became the same. The problem was solved after I disabled NoSpamNX.
Here is the log file from all-in-one-seo, if it helps you:
2009-06-01 14:40:07 another plugin interfering?
2009-06-01 14:40:07 detected output handler All_in_One_SEO_Pack::output_callback_for_title
2009-06-01 14:40:07 detected output handler NoSpamNX::addHiddenFields
2009-06-01 14:40:21 another plugin interfering?
2009-06-01 14:40:21 detected output handler All_in_One_SEO_Pack::output_callback_for_title
2009-06-01 14:40:21 detected output handler NoSpamNX::addHiddenFields
2009-06-01 14:41:33 another plugin interfering?
2009-06-01 14:41:33 detected output handler All_in_One_SEO_Pack::output_callback_for_title
2009-06-01 14:41:33 detected output handler NoSpamNX::addHiddenFields
2009-06-01 14:42:00 another plugin interfering?
2009-06-01 14:42:00 detected output handler All_in_One_SEO_Pack::output_callback_for_title
2009-06-01 14:42:00 detected output handler NoSpamNX::addHiddenFields
@Yanis
I’m using all-in-one-seo as well, but never had this error. Looks like all-in-one-seo is output buffer as well. Could you pass me a screenshot with your all-in-one-seo settings so i can take a look at it?
Hi Sven,
I have just emailed you the screenshot.
Yannis
@Yannis
I looked at the screenshot and could reproduce the problem – even the same error log message. Except that on my blog the titles were okay (not the same). As a short fix you could disable the all-in-one-seo option “Rewrite Titles”. I will have a deeper look at this.
Brilliant plug-in! Thanks so much for a simple, effective and unobtrusive solution.
Just wanted to thank you for a great plugin.. saves me lots of time.
Tested NoSpamnx v2.0 and found that if you are using domain mapping in Mu the Referrer check against “SiteURL” returns ‘failed’. Some doamin mappings ar non-standard; depending upon one’s choice of method or plugin. Might be a better way to go having a fill-in box in NoSpamNX Settings so that users can set a URL that they want matched, no matter what SiteURL says.
Other than that, it’s working great. Thanks.
Hi,
I change this beta version to work with wpmu.
The modified file is in: http://meublog.org/nospamnx.zip
Please if you like give me this credits:) and my site meublog.org
@Alexandre
Could you drop me a fee lines on what you changed?
Most important is the way to get the options. In WPMU you have for example get_site_option than get_option. So i make four functions to get, save, delete and update the right options based in wp or wpmu.
Next is the admin page, in this version if is wpmu the only show the admin page if is site admin. If not nothing is show.
So, i think is that. I put a post in mu.wordpress.org to other people test but no one repond my post until now.
Do you now if this plugin is compatible with wordpress hashcash?
@Alexandre
Okay, i will do some tests with your modifications and put it in the next release. As for hashcash i dont know if it is comptabile. Either way, i wouldn’t recommended using 2 (or more) plugins doing the same thind.
@Alexandre
I made some changes to your modifications. As i dont have a WordPress MU installed could you please take a look. If everthing works, i will put the changes in the next release.
Thanks!
Hello!
I’m to translate your plugin to belorussian language. when You publish this?
@FatCow
Sure. Just send the files to nospamnx (at) svenkubiak.de
i’m sent
Thanks!
It have Chinese,very good!
Nice, I used something like this on tfsnewworld.com, however I only used a single static one, and I also renamed the comment php in that old version to keep automated spam bots from directly ‘accessing’ the file and adding comments directly to the posts.
I will be using this on my WP site.
@Sven Kubiak I’m send translate files to nospamnx (at) svenkubiak.de, but you don’t publish my translate. hm.m.. “I’m glad to add more languages.”..
@FatCow
Please wait for the next release.
The plugin seems to catch chatcatcher plugin twitter trackbacks. Any thoughts?
Hi great plugin, i wanted to suggest a couple of ideas for it.
It would be nice if there was an admin option to not use the plugins own stylesheet so we can add the class to our own stylesheets, like a checkbox we can tick to disable the default stylesheet.
Also as the plugin gets more popular could spam bots be written to recognise and ignore the class name .locktross, if so maybe have an admin option where we can enter our own class name for the input fields.
Thanks.
Is there a way to get the messages blocked by NoSpamNX to be sent to the pending queue, except for ones with certain words (I dare not say them here, or my comment will probably be blocked) which can be sent directly to the Spam folder?
@Darwin O’Connor
No, at this time this is not possible.
Sven Kubiak: “Please wait for the next release.”
Sven, you REALLY ignore my work. i’m have translate you plugin 3 month ago, but you write “in next release”? it’s your feedback?
Thanks!
The plugin does not pass XHTML 1.0 Strict validation.
Specifically, the lines:
if (rand(1,2) == 1)
echo ”;
else
echo ”;
Should be changed to:
if (rand(1,2) == 1)
echo ”;
else
echo ”;
(If it doesn’t render correctly, you need to add paragraph — [p][/p] — tags before and after the code being “echo”-ed in lines 99 and 101 of nospamnx.php to maintain XHTML 1.0 Strict compatibility.)
Drat. The lines didn’t render correctly. Oh well.
If my description is inadequate to explain what needs to be done, please feel free to contact me by email.
Moin,
ich wollte mal fragen, ob es Sinn macht NoSpamNX und Askimet gemeinsam, also parallel zu nutzen – oder sollte man besser nur ein Antispam-Plugin benutzen, weil die sich sonst ggf. einander bei der Funktion behindern könnten.
@Jan
Ich habe selbst lange Zeit Akismet und NoSpamNX parallel benutzt. Das die beiden Plugins sich die die Quere kommen, kann ich nicht bestätigen. Mittlerweile habe ich aber Akismet seit mehreren Monaten deaktiviert.
@Nick I was going to write the exact same thing! I’ll second the vote for a tickbox to disable the plugin’s stylesheet and allow users to add the class to our main style sheets.
Great plugin!
@Living on Dividends
I have some other things in mind for Version 3.0, but this feature will definitly make its way into the next release.
I would like to suggest that make the next upgrade of NoSpamNX incorporate statistics and logging.
I would like to be able to see a log of IP addresses, and the number of times each one has tried to post.
Also, it would be neat to have an option to submit malicious IP addresses detected to a composite blocklist website of sorts.
And, it would also be neat to see some kind of visual statistics layout on the number of bots blocked per day, and per article comment page, etc.
Thanks for your great plugin. It is really a fantastic solution and the idea is simple yet effective.
@Tanner Williamson
Actually the feature for logging and blocking IP-Adresses was built-in some time ago, but i removed it as the same IP-Adresses were blocked anyway. Not due to the IP, but due to the hidden fields.
As for the statistics, i dont see this features in any further version. Sure, a stastic would be nice, but it would be to much work for just a “nice statistic”.
Furhter development will focus on reducing the code and improving blocking of spambots.
Hi, if you move the wp-content directory and its contents to a different location the plugin still trys to load the stylesheet from the origional default wp_content location.
It seems PLUGINDIR is not showing the correct location.
I only set the WP_CONTENT_DIR and the WP_CONTENT_URL in my wp-config.php i didnt set the plugin directorys as this is apparently optional and the themes, plugins and uploads folders all moved with the content directory keeping the same structure.
Thanks in advance.
@Nick
This problem can be avoided with version 3.0 (no release date yet), when you can add your own stylesheet.
Sven, I would like to thank you for making NoSpamNX. Because of NoSpamNX, I have been able to find several legitimate comments in my Wordpress Spam folder.
With this plugin, Akismet now puts 5 spams/day in the Spam folder instead of 50. So I’m able to sift through the spam to find the legitimate comments. I’m sad knowing that before I had NoSpamNX I would lose the occasional comment to Akismet.
Of course it’s a bother that a few spammers have found techniques that get around your plugin but the fight will continue on!
I’m making a $10 donation to you via Paypal. Rock on!
@Lee
Thank You!!!!!
You have a very funny mistake in your post.
NoSpamNX works without these modifications, but is equally in effective.
ineffective means doesn’t work.
you mean “equally effective”
Hi,
I have tried nospamnx 2.7 from here and 2.9 from the wordpress webpage. I’m running the latest stable wordpress version with a custom theme.
But if nospamnx is active it blocky every comment.
If I activate nospamnx it adds this line to my webpage:
and replaces this line:
with that line:
Do you have an idea what could be wrong?
Thanks!
Sorry for my last comment. The blog removes HTML code. You can see the HTML code which nospamnx adds to my weblog here: http://www.schiessle.org/tmp/nospamnx.txt
Is there something wrong?
@Bjoern
Are you using openID? NoSpamNX does not work with openID.
@sven: yes, i’m using openid… I will disable openid and try it again. But that’s really bad.
Any plans to make it work with openid?
Thanks!
@Bjoern
NoSpamNX version 3.0 is on its way, but with no openID Feature. Which openID Plugin do you use? If i find some time, i’ll take a look into it.
@kubi: I’m using this plugin: http://wordpress.org/extend/plugins/openid/
But I would also swtich to another Free Software OpenID plugin if it works with nospamnx. As long as the plugin supports wordpress login via OpenID and people can make comments with their OpenID. That’s the only two OpenID features I need.
Would be really great if you could make something happen!
Thanks a lot!
Hi Sven!
I see that you removed the option to check logged in users and other options in the 3.x version of your plugin.
How are handled this things now?. I.e. logged in users are checked now or not?.
Best regards,
Samuel.
@Samuel
Yes, i removed the option to check the login and register form, which (on user feedback) were to buggy to keep them alive. All-Users are checked now, whether they are logged in or not.
Sven, ever since version 3.x the hidden fields appear in my form. I had to go back to 2.9 which works seamlessly. 3.4 has the same effect. What could be causing this? Regards, Hector
@Hector
I changed the Name of the CSS Style as of Version 3.0, which i at first thought was the problem. But there seems to be another problem. Anyway, just deactivate and active the plugin OR go to settings -> nospamnx and reset the css name.
Just saw the prior “fix” that worked. Thanks
Clicking the “restart” button in the CSS plugin options fixed it. Thank you, Sven, and keep up the good work! Greetings from Spain
Are you going to re-enable the ability to block spambot registrations as users? Because it was working nicely until you disabled that feature (that’s the whole reason I installed nospamNX in the first place). Now I get 3-5 spam registrations a day again. So I’ll be going back to version 2.9 until you put that feature back. And I really don’t want to put a stupid captcha there.
@SoulRise
The Function did not work very well in certaint Blog-Configurations, which is the reason why i removed it. But, you can still use the 2.9.
Hello,
I have a similar problem as Bjoern. I re-did my comments.php and now the plugin blocks every comment as spam: “Sorry, but your comment appears to be spam.” As soon as I disable the plugin, comments are allowed.
I assume it’s something I did, but I can’t see anything in my comments template that would cause this. I love this plugin but I can’t keep using it if it rejects every comment. Any advice or pointers would be helpful.
@Bjoern
Sorry, but at this time is see no way to make NoSpamNX work with openID.
@JP
Your theme is probably not loading the hidden fields. Check if your comment-template loads “comment_form”.
It seems as though NoSpamNX is marking something as a spam, and akisnet is also marking it as a spam. Is there a way that if it is marked as spam by NoSpamNX to skip akisnet?
Sven — you’re right, and adding the call into the template seems to have worked. Thanks!
I have just upgraded to the latest version and now my site referrer check is broken and my comments seem to be considered spam, even when I’m logged in. Any thoughts
@Christopher G. Hill
Deactivate and activate plugin.
Thanks, and the 3.8 upgrade went flawlessly
Is there a way to “whitelist” certain domains? I have at least one false positive that I don’t want caught
@Christopher G.Hill
What do you mean by “domain”? Domains like the URL in the comment form?
Yes, thank you (particularly ubervu . com, topsy . com and mrtweet . com
No, you can’t whitelist domains. But i know were these false positive come from. Just wait for the next update
THanks, I appreciate the quick responses.
Das Update auf NoSpamNX 3.9 (vorher: 3.6) zerschießt WordPress MU (v. 2.8.6):
PHP Fatal error: Call to undefined function delete_site_option() in …/wp-content/plugins/nospamnx/nospamnx.php on line 426
Any chance you can make this work for mobilepress? I really love the widget, but the fields show in mobilepress, which is an important aspect of my site.
Let me know if there is something I need to do to make them invisible. I tried adding to the index and header files, neither seemed to work.
Thanks!
Would like to see you setting updated so that when an update comes out and one uses the auto update, your setting don’t go back to default..
@The Frosty
It would be rather easy to implemend that, but imagin an update comes with a failure and you still have NoSpamNX in “blocking” mode. Your comment form would be broken. This happended some time ago, when settings weren’t reset after an update. However, as of version 3.10 only the Blacklist won’t be reseted after updating.
I like your plugin but you need to change the wording for the css overwrite. It currently reads:
“If you do not want NoSpamNX to include this CSS-Stylesheet, enter the name of your Stylesheet in the textfield below”
What it should say is the following:
“If you do not want NoSpamNX to include its own stylesheet, enter the name of the class (e.g., .hidebox) you’d like to associate it with in the field below and to your global stylesheet (i.e., the one loaded by wordpress).”
I had to dig through the code to find out how to stop your plugin from calling its own stylesheet. The fields look for a class (i.e., .hidebox), not an actual stylesheet (i.e., style.css).
Thanks again for the plugin, its working great
@WS
Thanks! Already changed it
this is the only antispam that works flawlessly for me. no more (hundreds of) spam to manage daily.
is it possible to make it work with other forms as well?
like, the registration form, contact form.
also new blog registration form on wpmu.
tnx
I’m using this plugin since its YAWASP times and I can say it is the most innovative and effective way to fight spam.
I have never visited my blog’s Akismet page anymore to delete spam. There is no need for that anymore.
I wish you could port it to Drupal since I’m switching most of my sites from WordPress to Drupal.
Thanks !
Thanks for this excellent anti-spam plugin, but i’ve got a question to ask.
I choose marked as spam no block. However, I can only see ‘NoSpamNX has stopped 4 birdbrained Spambots’ in the control panel page while no spam comments in the spam list.
How can this option take effect? ‘Cause i just wanna make a double check to avoid miss-killing sometimes.
I only use Nospamnx, no akismet.
Thanks!
@NickYe
Which Version of WordPress/NoSpamNX do you use? Do you have the Referer-Check enabled?
wp 2.9.1 and nospamnx3.11, both latest.
Referer-Check disabled.
This plugin actually takes effect, the only problem is i can’t see spam in the spam list. They were all blocked even if i enabled the ‘marked as spam’
@NickYe
Do you user any Plugin that “connects” to the comment form? I saw a JS Script right unter your comment form, something like wp-thread-comment.js.php?jsver=common …
Yes, I have several other plugins connetcting to the comment form. Maybe it’s because the conflict among them.
Anyway, it works.
@NickYe
Suddenly it works? That’s strange….