My health has been in question over the past few days. Nothing serious, I’ve just got a cold that refuses to actually get going. I’ll get the sore throat, which will disappear and then reappear, along with the full nose, which would gdo the same. Ergh. Not good.
Anyway, in response to Noscere’s post, I’m going to post some of the WordPress plugins I use, just so you know what goes on “behind the scenes”. Note that I won’t mention security related plugins here!
First up is Akismet. Nothing really much to say about this particular little utility. It saves me having to delete spam, and with just over 45,000 spam comments at the time of typing, it’s saved me some work!
Secondly, there’s iMax Width, and no, it’s nothing to do with the branch of cinema. It forces any image I post on here to a maximum width of 500 pixels. Normally, this is the case anyway, as most of the photos I post come from Flickr, which automatically have a width of 500, but I’ve seen on a couple of occasions, I’ve posted one of the bigger sizes, meaning that if this plugin wasn’t there, the page would look like shite. And what do you mean by “it does anyway”?
Next up is Stapress reloaded. When work stalled on the original Statpress plugin, several spin-offs were released. This is just one of them. I’m not sure if work has halted on this too. Either way, it doesn’t really matter, it’s still usable. Unfortunately, it seems that this is the number-one cause of slowness on the site, as the database size grows quickly.
And then, we have Twitter Tools. I must admit to still not fully understanding Twitter. Why would I want to limit myself to 140 characters to say something? And if I want to send someone a private message, I don’t want that 140 characters eaten in by whoever’s user name it is. I use it mainly for giving a quick twitter update, announcing a new blog post (which I’ll probably do with this one), and for quickly creating a bit.ly link, should I want to pass the link to someone else. I’m sure someone will give me a reason why twitter is so… erm, needed. Saying that, when a celebrity is reported to be dead, it’s the first place I look.
WordPress Database Backup is pretty much redundant to me, as since installation, I have other backup mechanisms in place. I don’t think I’ve used it in about 2 years. It’s infinitely slower than my other methods, and I only keep it in place for emergencies.
And if it isn’t our old friend, Google XML Sitemaps up next! (You can tell I’m really starting to struggle for introductions to these) which creates an XML sitemap readable by Google, presumably so it understands the site better. Or something.
Last up, because I can’t be bothered to do anymore, and I can already see Chad’s eyes glazing over is WP tags to Technorati, and is the reason there’s two sets of tags in here. I assumed it would help the blog get “noticed” (though I always seem to complain or get overly paranoid when it does get partially popular), and was installed after the “tags” feature was added to WordPress. I’m not sure if it provides any benefit anymore, as the plugin hasn’t been updated since the iron age, and the amount of hits I get from technorati is negligible, so I’m not even sure if it works anymore.
To answer the questions you weren’t thinking of, no I don’t use any type of cache plugin. It caused me headaches last year, and to think this blog generates any type of server load that would require cache usage, would simply be delusion on my part. The only time I’ve generated noticeable server load was when I posted that Jeremy Beadle had died about 2 years ago. It soon quietened down as soon as word started to spread across the interwebs. Obviously, with the introduction of the afore-mentioned twitter, I wonder how many people do the same as me, and just bypass Google altogether….
Right, that’s it for now. Hopefully, I’ll get my body in order shortly. I’m off work for the next few days.
