Stephane Daury (stephdau)

I was going to suggest that maybe the Auto Approve Comments plugin could be of help, but I checked their code, and they actually don’t approve a comment if Akismet thought it’s spam.

On the other hand, maybe the approach they’re taking could be something you could replicate for your needs: they hook on wp_insert_comment, set $comment['comment_approved'] to 1, and update the comment.

That wouldn’t bypass Akismet per se, though. It would just negate it flagging something as spam.

To completely bypass Akismet, you can also leverage the fact that it won’t do anything in the way of checking for spam if the API key isn’t configured.

So, in an mu-plugin (or your preferred way to auto-run code), you could:

if ( ! is_admin() ) {
        add_filter( 'akismet_get_api_key', '__return_null' );
}

… for the users you want. That way, every time our plugin tries to use Akismet::get_api_key(), it won’t get one, and won’t check the API, etc.

The is_admin() test is there so that those users still get access to Akismet’s functionalities in wp-admin (like in comment moderation, etc).

Hi there,

Lack of minification reported by such tools isn’t really raising an issue per se, but more of an optimization suggestion.

Our view is that Javascript in plugins shouldn’t be minified, as we feel it obfuscates the code for anyone looking to learn, or contribute. Akismet being bundled with WP, many would-be developers start their path to learning plugin development by reading through our plugin’s code.

Note that there are many WP plugins, and server-level (Apache, nginx, etc) modules that can handle this automatically for your whole site.

Hi Adeline,

This sounds very strange, and that there was some sort of error with our payment provider (Stripe).

Could you please reach out to us via https://akismet.com/contact (choose “I have a billing question.”) with your API key and/or email address, and we’ll tend to this as quickly as possible, including refunding you for the extra charges.

With apologies, ad looking forward to resolving that unfortunate situation.

No, one will work as well, but it should be paired with one of our commercial plans.

All keys can now serve an unlimited number of sites, and the plan you choose will depend on how much traffic you’re expecting. See https://docs.akismet.com/akismet-api-usage-limits/ for more info.

• This reply was modified 3 years, 8 months ago by Stephane Daury (stephdau).

Hi there,

There is indeed no setting for it at the moment, but if one must, the feature can easily be disabled with a bit of code.

Hi there,

If you want to achieve this immediately, you should be able to leverage WP’s remove_action() on those two, and remove_filter() on this one.

We’ll discuss the potential to provide other ways to achieve the same in the future.

Hi Paul,

Since figuring out what might be happening could require some information that would not be desirable to post publicly (site URL, etc), could you please reach out to us from https://akismet.com/contact/ ? We’ll be happy to help you sort this out. 🙂

Marking this as resolved after 2 weeks with no reply from the requester.