Hmmm. I’m not sure what is causing this, but I’ll look into it for you. I may not have time until next weekend though sorry.
Support for multisite signups is still experimental, although my attempt to test it on the weekend indicated that it was working just fine.
Thanks for the prompt reply.
Plugin is working quite well so far with about 90% spam catch rate our side. The add new user via backend is the only issue I’ve noticed so far running on WPMS.
90% is quite bad. In my own experience it usually blocks about 99.9% of the spam. Do you know if the spam is from blog post comments or perhaps it is from a contact form or registrations?
Also, how much spam are you getting in total?
Thats from blog posts comments, we have the plugin installed on just over 100 sites at the moment, spam amounts to about 1000 to 1500 per site on a daily basis, there would be about ~100 that makes it through.
Unless my math is off, then that means it’s blocking 99.9% of the spam, which matches my own experiences with it.
Have you tried using Akismet as well? That should help weed out a few more too. The two plugins should work perfectly well in coordination with each other since they use totally different methods to block the spam.
Your math is off, 1000 comments @ 99% = 10, 1000 comments @ 90% = 100
Due to our weak exchange rate we cannot afford the akismet licence, we were exceeding 500k calls per month which made it too expensive.
Ah, I thought you meant there were 100 in total getting through, not per site.
When you are running Spam Destroyer you will make significantly less calls back to Akismet since the spam gets blocked before it gets there.
I’m thinking of adding in an extra layer of spam protection for people like yourself who have trouble getting rid of the spam. 90% really isn’t acceptable.
Personally, I’m very happy with the plugin – it’s the best alternatives to akismet that I’ve tested.
Ed
(@coopeh)
Hi Ryan,
Just to let you know, we updated to the latest version on the 18th and it stopped anyone being able to register a blog if they were logged in on a Multi-Site install. I’ve disabled the plugin for now.
Part of a stack trace for you:
2.9645 9542008 -> Spam_Destroyer->check_for_post_evilness() /wp-includes/plugin.php:173
2.9645 9542184 -> is_user_logged_in() /wp-content/plugins/spam-destroyer/index.php:206
2.9646 9542184 -> wp_get_current_user() /wp-includes/pluggable.php:727
2.9646 9542184 -> get_currentuserinfo() /wp-includes/pluggable.php:54
2.9647 9542232 -> WP_User->exists() /wp-includes/pluggable.php:729
2.9648 9541360 -> next() /wp-includes/plugin.php:176
2.9648 9541360 -> array_pop() /wp-includes/plugin.php:178
2.9650 9538432 -> extract() /wp-signup.php:202
2.9654 9538376 -> wpdb->__destruct() /wp-includes/wp-db.php:0
2.9654 9538376 -> shutdown_action_hook() /wp-includes/load.php:0
Cheers,
Ed
Thanks Ed. I had to make a change due to it breaking manual user registration and I guess that broke the registration on the front-end.
I’m doing some upgrades at the moment and as part of that, I want to make sure it works well with multisite, bbPress, Gravity forms, BuddyPress plus some other things. Whereas at the moment I’m only listing those things as experimental due to problems such as the one you have just experienced.
I’ll try to remember to post back here once I’ve completed the upgrades.
In the mean time, you could reinstall the old one. I’m not aware of any security flaws in it, just that it was preventing people from signing up new users via the admin panel.
