WordPress: Invalid Security Token

So I learned from a wanna-be commenter here that efforts to post comments here (am I being redundant by now?) were failing.

Instead of the comment posting, this error message resulted instead: Invalid security token. Bad. Deal.

I did some research in the course of two days. πŸ™

I learned that Jetpack Comments does not play nice with Antispam Bee. That’s good to know…but I don’t have Antispam Bee.

I disabled some other plugins, including Live Comment Preview. Nope — the problem continued.

So I disabled Jetpack Comments. Too bad. πŸ™ But at least now people can comment here again! (I suppose that will open the floodgates to the comment spammers again. If so, Akismet can earn its keep once again.)

PS: To those of you who tried commenting and experienced the invalid security token problem, I’m sorry. πŸ˜₯ Please try again now!

Update on October 30, 2012 at 7:43 am — I forgot to mention last night that, before deactivating some plugins, I tried using a different theme.

13 thoughts on “WordPress: Invalid Security Token

  1. This is a not-logged-in comment to observe that the Twitter-logged-in comment that was after the Facebook-logged-in comment vanished as the WordPress-logged-in comment was posting! πŸ™

  2. Not logged in again. Now two Twitter-logged-in comments are showing…but they’re requiring moderation. So let’s see if they show up and stay put if I approve them… πŸ™„

  3. OK. I reactivated Fast Secure Contact Form, logged out, and tried twice to post a comment. No success. So I logged back in, deactivated FSCF, logged back out, and here I am again…though this time Facebook-logged-in.

  4. Hmm.. fixed already. I must disable jetpack comments, replied in a post, then enabled again to get it working. It was not a twitter/wp.com issue but the integration with my blog. Maybe because I was running a localhost (xampp-lampp) version of the blog and the plugin can’t access http://localhost/mysite – this invalidated my production (real) blog

  5. Hi Mark, thanks for the post, it was really useful.
    I only found out because I wanted to share a comment from previous post shared in LinkedIn and I came across with this error message.
    It is upsetting to think that maybe visitor maybe have gone away because of this error.
    I don’t want to loose the features offered by Jetpack and don’t want to loose the features offered by Antispam Bee, I hope they fixed it soon.
    I have just disabled the Jetpack comments feature and it worked ok.
    I have shared the experience in a post in my blog as well.
    I hope it helps others with in similar situation too.

Comment? Sure!

Above all, love God!
%d bloggers like this: