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. :cry: 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.

This entry was posted in Tech Stuff and tagged , , . Bookmark the permalink.

12 Responses to WordPress: Invalid Security Token

  1. Mark Roth says:

    Jetpack comment, no log in

  2. Mark Roth says:

    Jetpack comment, Facebook log in

    (yes, I’m testing, OK!) :(

  3. Jetpack comment, Twitter log in

  4. Mark Roth says:

    Jetpack comment, WordPress log in

  5. Mark Roth says:

    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! :(

  6. This is another Twitter-logged-in comment…

  7. Mark Roth says:

    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… :roll:

  8. Mark Roth says:

    Now I’m logged in as the site owner and I approved the Twitter-logged-in comments and they’re showing up above. OK. Good. :D

  9. Mark Roth says:

    OK. I reactivated Fast Secure Contact Form (plugin) and logged out of my AC account so I could test this.

  10. Mark Roth says:

    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.

  11. I’m facing exactly this problem now… Never had this error before, using Jetpack for 2 months now. I dont have antispam bee plugin installed either.

  12. 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

Comment? Sure!