How Akismet Hosed My WordPress Blog
Lincoln Adams | August 8, 2007 @ 7:40 pmFor some time now I used to have this perplexing problem where I simply couldn’t access the administrative section of my blog without it timing out on me. I couldn’t figure out what was causing the latency issues, and I also noticed that if I tried to access it from a different browser or different IP address, the issue would usually clear itself up. It was an anomaly that only occurred every now and then, so I wasn’t too worried.
Then yesterday it started happening again. Only it got worse. MUCH worse. So bad in fact, that I couldn’t access the Admin page at all. Then I started getting 500 internal server errors after trying to access my admin from different browsers and different IP addresses. Nothing seemed to work.
I finally submitted a ticket to my hosting service, Hostgator. I was a little worried that I would get some half baked tech support dude, but these guys really rose to the occasion. After scouring over every nook and cranny of my blog, a network admin emailed me to let me know they they had been experiencing a lot of issues with WordPress blogs that day, and the only common denominator that they could find was that we all had Akismet installed. They since learned that it was an issue on the manufacturer’s side. The network admin then deactivated my plugin and asked me to check my blog again.
Instant access! Yaaaaaay! My admin page was now loading, and it was smoking fast too. I couldn’t believe it.
But now I had another problem. I no longer had protection from comment spammers, and my blog suddenly became open season for these scumballs. I was already getting comment spam while I raced to my options page and set all future comments to moderated status as a temporary fix.
I then went to the home site for Akismet (which is developed by Automattic,) to see what news there were regarding this issue that was apparently affecting quite a few WordPress based blogs.
Nothing. There was no update to speak of, and the Akismet blog itself hadn’t even been updated in a month. So I used their contact form to send them a polite note inquiring about this issue and how soon it would be resolved. No response. So not only did they hose the administrative portion of my blog, but they blow me off on top of that?
Suck it, Automattic. It’s obvious your support system isn’t worth a hill of smelly beans. This was a problem that had the capacity to lock out God only knows how many WordPress users from accessing the admin portion of their blogs, but this seems to matter to you, not at all.
I suspect this might have something to do with using an older version of the Akismet plugin though (I was using 2.0). When I upgraded to 2.02, everything seemed to work fine. But just by going to their website, you’d have no idea that there had been any updates since 2.0. There’s no changelog or even any other basic information, except for a download link for “2.0″ which in actuality was really 2.02.
This wouldn’t frost my cookies so much if it had been any other typical third party plugin, where you can only expect so much support from its developer. This was a plugin developed by the makers of WordPress itself, and one that required API access to their servers. If something goes wrong, it’s liable to create problems not just for them, but for your blog as well.
So… how about a little bit of courtesy here for us little people, mmmm-kay?
Related Posts:
- Hostgator Web Hosting - A Review (2)
- Thief Thief! (5)
- Stumbling My Way Home (8)
- Pre-Spring Cleaning (5)
- Plugins Gone Wild! (12)
Tags: akismet, anomaly, automattic, blog, blogs, bug, common denominator, downtime, half baked, hostgator, hosting service, ip addresses, issues, open season, plugins, spam, spammers, tech support, web hosting, wordpress
Categories: Blog Fog
(
Print This Post
| | 4,118 views )




(1 votes, average: 4 out of 5)




8 Responses to “How Akismet Hosed My WordPress Blog”
Quote
I’ve generally had decent luck with Akismet, but I’m back to running the Bad Behavior / Spam Karma 1-2 punch combo.
I find them very effective.
I do run an additional Spam Karma extension that passes comments through Akismet as well — but if akismet isn’t responsive, things just keep on working.
Quote
I liked Akismet because of its convenience, but I had no idea just how badly it could affect my blog’s interface when something goes wrong till now.
I think I may end up using Spam Karma too somewhere down the road, only problem is one of my plugins isn’t compatible with it. Worse yet, I can’t remember which plugin it was either.
Quote
Well, if you’d run fewer than 300 plugins….
At least toss in Bad Behavior. It blocks several thousand a week for me — and it catches them before SK or Akismet are even aware.
Quote
It’s actually already running, one of the many plugins I have installed.
Quote
It does not help you too much but the NucleusCMS community have no commercial core and so is more “classically open source”. The anti spam community got together and simply wrote plugins, piles of em in every form imaginable. There are two good captcha the one the core writers made and one I made that uses RE:Captcha. Some guys even came up with an anti-spam API that is in core for CVS (meaning next release it’s part of the framework) and the result is that a sort of survival of the fittest kicked in and for say the three or four plugs that sucked one or two ruled. Of those some had keen developers and others were picked up on by better coders and expanded.
I’m thinking WP needs far more competing plugins for spam. While Akismet is known to be very effective it is not the only game in town and as a default is very privacy intrusive.
Just my 0.02 * 4 worth.
Quote
I have to agree, seeing more competing plugins would provide incentive for developers to continue improving their products (and maybe their support as well).
Trackbacks
Quicktags: