New Spambam plugin

I’ve finally taken the time to update my spam protection plugin for WordPress, the original plugin worked well and stopped pretty much any automated spam. But I decided to update it because a few users were reporting problems on this site and other sites, for some reason it didn’t work with IE7. Rather than just fix it….

The latest plugin uses my PHP/JS randomisation techniques to create a key and protect against spam. I’ve took this bold move to see what affect it has and if the blog spammers will get round it because it no longer uses javascript cookies. My post on Javascript/PHP randomisation can be found here (with source code) the WordPress plugin can be found on the WordPress site.

9 Responses to “New Spambam plugin”

  1. Nick writes:

    Hi there,
    I’d like to suggest a feature, if you check my site you’ll see in the footer I like to show how much spam plugins block.

    If you insert
    $counter = get_option(‘spambam_spam_count’);
    $counter = $counter + 1;
    update_option( ‘spambam_spam_count’, $counter );

    we can have “Spambam has blocked x spams since installed” within our themes… it’s a cool way of show how effective each plugin is 🙂

  2. Gareth Heyes writes:

    Hi Nick

    Yes good idea I shall add that feature into the next release.

  3. Gary Harvey writes:

    Hi Gareth.

    I uploaded the plugin folder and activated it but get this error msg.

    Warning: join() [function.join]: Bad arguments. in /home/xxxxxx/public_html/blog/wp-content/plugins/spambam/spambam.php on line 43

    Warning: join() [function.join]: Bad arguments. in /home/xxxxxx/public_html/blog/wp-content/plugins/spambam/spambam.php on line 43
    We don’t allow comment spam here. Javascript is required to submit a comment.



  4. Gareth Heyes writes:

    Hi Gary

    It appears that your server doesn’t support sessions or uses a old method of sessions. You could try a run a find and replace the following lines:-

    1. $_SESSION[‘spambam_result’] = ”;
    2. return join(“”,$_SESSION[‘spambam_result’]);
    3. $_SESSION[‘spambam_result’] = $randomJS->result;

    1. global $HTTP_SESSION_VARS;
    $HTTP_SESSION_VARS[‘spambam_result’] = ”;
    2. global $HTTP_SESSION_VARS;
    return join(“”,$HTTP_SESSION_VARS[‘spambam_result’]);

    3. global $HTTP_SESSION_VARS;
    $HTTP_SESSION_VARS[‘spambam_result’] = $randomJS->result;

  5. Clyde Gill writes:

    I found this thread searching for this error string, “We don’t allow comment spam here. Javascript is required to submit a comment.” which is occuring sporadically when comments are submitted. Seems odd that it does not happen all of the time. I have 5 separate wordpress blogs running on one online server and one offline server, all using spam bam, and this is only occuring on one of the online server blogs. This error has happened to one of my contributors a few times and just now happened to me. All pc’s involved have java running.

    I wanted to check to see if you thought the code in the 4th comment above would work!? My error code does not include all the other ‘Warnings’ that Gary posted.

    I’ve used spam bam on my other blogs for quite some time now with great effect!

  6. Gareth Heyes writes:


    Hi, a new version is in development and should be released next week. It contains many improvements and should fix these bugs.

  7. Chelsea writes:

    “We don’t allow comment spam here. Javascript is required to submit a comment.”

    I’ve been experiencing the same problem. Many people complained of not being able to comment on my blog recently (even if they’ve been able to in the past).

  8. Gareth Heyes writes:


    Sorry about that, I know of this bug and I’m working on the new version. Would you mind beta testing it for me? If so I’ll post the latest version here

  9. HP Bryce writes:

    I am glad so many people are using what they know to stop Spam. Is this project still ongoing now askimet is out?