That was actually the sole reason that I put that hook (comment_post_redirect) in there… just never got around to writing the plugin to use it.

Default notification is JS alert() because that’ll work most generally, but I included an alternative notification method that you can use if your theme has the comment_form hook.

If the die on 213 isn’t often triggered, then I’d probably drop a conditional right after line 216 (akismet_delete_old();) in order to make this happen. I think a plain old die would be good enough for me at the moment, considering that redirects are kind of dark-gray magic to me. (I get the general principle, but the specifics of their handling in WP bedevil me.)

Gerard, I don’t think this would be that big a flag, since I’m not sending anyone any e-mail. I’m just throwing what is, in effect, an error page back at the web browser. I suppose that I could eventually get fancy and return an HTTP error code and page, maybe a 417.

Sounds like a generally good idea, Amber, except the way the Akismet WP plugin is written, there are a few exits scattered about, and identifying just the right one is a bit tricky for me. I think I’ll probably do something based on Alexander’s suggestion.

Mine just looks like this:


if($akismet->isSpam()) {
// Save the suspicious comment in the spam table
/*** Insert query goes here ***/

// Delete the buffer
ob_end_clean();
exit("Akismet thinks your comment is spam. E-mail me (amber at tangerinecs dot com) if that's not the case.");
}


With the amount of comment spam these days, I check my moderation queues less and less. Comment spam really increases the cost of blog ownership, and if you don’t start to ignore it, you’ll spend your life in moderation hell!

In line 204 through 214, the spam comment gets put in the spam queue. In line 212 you could add a redirect yourself which notifies the user of bad things happening.

Hope that helps. I doubt you could make a plugin that notifies the user without hacking the Akismet Plugin itself. Akismet adds itself as the first action in the comment preprocessing queue. If you could put a custom action before that, you’d probably be best off by storing the comment in a session, letting Akismet do it’s job and on the next page check whether the comment has been actually posted or not. Akismet doesn’t exactly provide any API hooks from what I can see.