WordPress is a state-of-the-art semantic personal publishing platform with a focus on aesthetics, web standards, and usability. What a mouthful.
Indeed what a mouthful, but what becomes of it when it becomes unusable? For the last couple of weeks, I’ve been floating around the support forums looking for answers to questions I have as well as trying to help others with things I may have already fixed, but it’s slowly becoming apparent to me that the problem is WordPress its self…
Now regardless of what the problem was, I’ve always been able to come up with a quick fix, sort of like a band-aid, to sort it out until I can seek “professional” help in the support forums, but now I have a problem that, as much as they think they are helping, is just down to fucked up coding by the developers. But wait, yes, I’m using 1.5 beta, and “beta releases shouldn’t be used by the general public,” OK, fine, so why do the general public have access to these nightly releases? If Joe Schmoe is running WP 1.2.2 and finds out that someone or other is running WP 1.5, of course he’s gonna want to upgrade, cause WP 1.5 comes with all these much better bells and whistles. Therein lies the problem, the average user (and I don’t mean to be condesending in this, simply because 18 months ago, I was the same) probably doesn’t have the knowledge needed to fix things when they fuck up, and they will fuck up…
The “company policy” when it comes to this is “back up your data via phpMyAdmin, change settings in phpMyAdmin, yadda yadda yadda” which for advanced users is all fine and dandy, but me, and I consider myself an advanced user, I absolutely HATE going into phpMyAdmin, it’s far, far to easy to screw around with something and end up with everything in your database flushed down the proverbial toilet.
Anyways, back to the problem at hand, I can’t login to my WordPress install, the only reason I’m posting this is because when I upgraded to WP 1.5, Firefox kept the login cookie and lets me in, if anything, god forbid, should happen to that cookie, then I’m up shit creek without a paddle… And I’m not the only one… In fact this is described as a major bug in the system and it’s been around for a while, and with almost a month of nightly releases under WP1.5’s belt, it’s still not fixed, let me repeat that… IT’S STILL NOT FIXED! What kind of system that advertises it’s self as, and let me repeat:
WordPress is a state-of-the-art semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
And it won’t even let you do the “simple” thing as logging in to the admin section… And the support forum is bursting with people to tell you how to fix it, except it’s not fixing it, and someone even said, I wish I could find the post now, that it “wasn’t such a big deal and the developers probably have more important things to worry about.” How off putting is that when you’re trying to fix this kind of error?
Which brings me back to my original point, the problem with WordPress is WordPress it’s self… Due to it’s open source nature, it will be impossible to have any kind of “official” technical support, so instead we have to rely on one another, but when you’re asking important questions and the responses are generally unhelpful, and sometimes insulting, what can you do?
EDIT (20/01/05 6:01pm): A particularly inflamatory statement has been removed, in the cold light of day it probably wasn’t the best thing to say and for those it offended I can only apologise profusely.
EDIT (17/02/05 11:58am): Toby Simmons has a great fix for login issue if you’re using Windows IIS