Found the issue — Antispam Bee and Jet Pack comments doesn’t appear to play nice with each other sometimes. Jetpack (among other things) makes the comment section of the website nice. However AntiSpam Bee eliminates spam and IMO one of the better ones. You can turn off the Jetpack part for the comment section if needed. Go to Jetpack -> Setting and look for ‘JetPack Comments’ – deactivate. When this is done the rest of Jetpack remain in force like analytics and other necessary items, Antispamm bee works and you can leave comments – this is not ideal. While I’m not happy that Jetpack comments are deactivated as I think they are nicer looking, at least I didn’t have to deactivate the entire plugin. I hope the two plugin authors can make these two work together nicely soon….
Unfortunately, and as you figured out, Jetpack Comments are not compatible with any other plugin hooking into the WordPress comment form.
Since Jetpack’s Comment form is hosted on WordPress.com and added to your site via an iFrame, other plugins (like Anti Spam Bee) can’t hook into that comment form.
Until we find a way to allow third-party services to hook into Jetpack’s Comment form, you’ll need to deactivate either the comment module, or your other plugin.
You can follow our progress here:
https://github.com/Automattic/jetpack/issues/477
The issue is in Jetpack conflicting with Antispam Bee, ok, now, I don’t want to disable Jetpack plugin as I like the share facility it offers and I don’t want to disable Antispam Bee as the amount of spam I get by not having Antispam Bee is simple don’t worth the hassle.
If this is the same scenario you have in your WordPress based blog, with the same plugins and experiencing the same issue here is the work around.
The solution to solve the error invalid security token in WordPress comments is simple by disable the Jetckpack Comments in Jetpack settings. Really simple.
You can see more details here:
