Thanksgiving Plugin Update

There was one overwhelming piece of feedback from version 1.0 of the Akismet plugin for WordPress, that people wanted to be able to see the content of the comments marked as spam. This also manifested itself in a lot of “false false positives” being submitted to the system, where a comment would look legitimate except for hidden links or bad content at the end that Akismet would correctly catch but would look like a legit comment from the limited information on the Spam screen.

Well now with version 1.1 of the Akismet plugin (which you can download here) we’ve given it an interface more like the moderation screen in WordPress so you can review the whole comment before deciding to mark it as not spam.

This is an optional update, if you’re happy with the version of Akismet plugin you’re using now feel free to continue with it.

If you have any more great ideas, please contact us and we’ll try to work it in to a future version.


  1. Pingback: Akismet Thanksgiving Update at
  2. Correct me if I’m wrong, but isn’t the version of Akismet included in the WordPress nightlies already at version 1.11? Is that newer or older than this 1.1 update?

  3. 1.11 is the latest, it’s what you get when you click the download link. It is the latest in the 1.1x series. 🙂

  5. Pingback: Incoherent Babble » Blog Archive » Those Lousy Akismet Devs…
  6. Pingback: Ancora su Akismet at Midnight Cappuccino
  7. Pingback: » Blog Archive » Akismet Plugin Updated
  8. Pingback: ionfish § Bright Chaps
  9. Pingback: Only for Akismet » Thanksgiving Plugin Update
  10. I installed this on WP 1.5 and now, in the Manage / Akismet Spam screen, I get this instead of the list of caught comments:

    Fatal error: Call to undefined function: get_post() in [path to public_html directory]/eric/thoughts/wp-content/plugins/akismet.php on line 251

  11. Pingback: La mate por un yogur » Akismet ya muestra el contenido del spam
  12. As a followup, the plugin appears to be working– it’s catching messages, and a non-spam comment got through since installing it. I just can’t look at the list of caught spam, due to the aforementioned error.

  13. Thanks for an amazing plugin Matt! This really makes my life easier!

    Right now the version is set to 1.12. Care to tell us what’s happend since 1.1?

    And I think I’ve got the same problem as Seth and Nick right above me here. It shows me a lot less comments than what it tells me it’s cought.

  14. Pingback: Akismet: Give your WordPress Luck, Fate, and Destiny | GreatNexus Webmaster Blog
  15. Is anyone else experiencing this: Every single comment is being caught by Akismet and marked as Spam. This happened under both 1.1 and 1.2 of the Plugin.

    I completely deleted Akismet from my WordPress blog this morning and it was STILL catching comments as Spam even though it was not supposed to be around.

    When I put Akismet back and re-activated the Plugin, it “showed” me some of those messages it somehow refused to post when it was deleted from my server.

    What is going on? Where is Akismet hiding in my WordPress installation? I dont’ seee any .htaccess entries.

  16. Things are magically back working again and comments are not getting caught as Spam. I didn’t do anything on my end to change this but I’m thrilled all is well once again.

  17. For the people who are showing less spam to moderate then the number caught, that’s normal functionality. Akismet only displays unique spam messages. If it’s a duplicate, it won’t display it. Before the update it used to show how many of that particular message it caught; unfortunately it doesn’t do that anymore. Hopefully they’ll add that number back so it’s less confusing for new users.

  18. Pingback: » Blog Archive » Akismet ouvre son API
  19. I’d like to see on which post the suspected spam has landed. Sometimes, depending on context, cryptic comments can be considered as spam or as legit stuff.

  20. Pingback: [LINICKX].com/blog » Akismet is soo good I didn’t even know it !
  21. For the people with the get_post error, you need to upgrade to WordPress 1.5.2 or higher.

Comments are closed.