Skip to Content

Wordpress 2.5.x a Major Disappointment

Yes, I had another post first planned and then ready, but my change to Wordpress and then upgrading to 2.5 and 2.5.1 has been such a nightmare that it has negated each and every reason why I changed over to this "blogging" platform in the first place. It seems as if every fix that is integrated via updating produces a myriad of other errors ... and that's no matter how closely you follow the various instructions. I had switched to Wordpress for health reasons and right now Wordpress is making things worse. Simple as that.

As of now, I can neither upload images into my posts (I can, but only by sidestepping Wordpress altogether) and ever since I upgraded to 2.5.1 the problems with that issue have increased, including new issues like a broken feed. I'm reluctant to list the other issues I have which persist, but I can only add three custom fields if I add one, then save, and then add the other two. Took me a while to figure that one out. The visual editor? *Groan* (but that problem WP has been carrying around for ages, so no surprise there. There's more, but you can find all of it over at the Wordpress forums.

There's no point in pulling out my hair and investing more time into this right now, so I just have to put this whole relaunch on hold and wait until the Wordpress team has gotten a grip on things to be able to post regularly again and then, in the summer, hop over to another platform. Sorry about that, but there's nothing else I can do right now.

I do have a couple of thoughts though on this whole thing:

After having spent I don't know how many hours on the "support" forums, I can only say that I have never ever - with any software (not even with Windows) - experienced such open (and at times a bit more sublime) arrogance as with some posters over there. Just have a look yourself and watch how posts get deleted, threads are closed, beginning users are left with a myriad of either unanswered support requests or are given the standard reply of checking the sticky posts (or whatever) that haven't fixed issues for lots of people. Sure, it's all free and run by volunteers, but other sites are doing a better job at it. Believe me. I know.

It's become a mantra of sorts to stonewall many support requests with "YOU are the culprit / YOUR server is / EVERYTHING but WP / ..." instead of at least acknowledging that there must be something wrong with the Wordpress backend.

I'm not even going to comment on the interface issues that have many people stumped. Just have a look at this here which is exemplary (in a much toned-down way) of what's currently going on. It all seems pretty hopeless right now. You could also look at this next to that or just about any other list of fixes that don't work for some or many people. Lots of examples in the support forums. Still, I'd rather you just sat down and watched a good film. This one here is on endless repeat.

I actually downloaded and installed Wordpress to be able to return to a regular posting schedule, but the opposite was the case. Wordpress is actively preventing me from doing the most basic things a blogging program / CMS is supposed to be helping me with. Instead, I've spent all of three days on support forums, trying to find workarounds for the most basic tasks, have time and again tried the same fixes without any results, have actually deleted the whole shebang and reinstalled it clean as a whistle. Still, nada.

It stumps me completely that Wordpress has been able to mess things up in such a major way. 2.3 worked fine and I refuse to believe that testing was extensive beforehand. All of it seems like a rush job compared to major upgrades I experienced with my past software of choice. I now understand the people over at Expression Engine who calmed everyone down each and every time, stating that they weren't done with the testing yet. And once they did roll out the update, issues were resolved in a matter of hours. I also believe that that did not have anything to do with EE not being free; it had something to do with real commitment to an excellent product. And that's all.

So, I'm giving up for now.

Stay tuned for any developments ... if they ever appear in my feed.
Right now, I sincerely doubt it.

I have already now decided to abandon Wordpress as soon as possible (I should have heeded the warnings many experienced users sent my way prior to my switching platforms) to try a different route (anything else really), but I just haven't got the time. I'm right in the middle of the busiest weeks of the year and I don't need Matt Mullenweg's software to take the last free hours that I have left.

Related Posts

  1. WordPress: Spam Magnet
  2. Version 2.0 Approaching!
  3. Version 2.0
  4. Help Me Improve This Site
  5. Picking up speed …
  6. Expression Engine
  7. Web Design Is A Pain In The Ass
  8. A Forced Hiatus
  9. Featured on pMachine.com
  10. Vrrrooom (Site Update)

11 Responses to “Wordpress 2.5.x a Major Disappointment” Leave a reply ›

  • wow you do sure cry a lot. for all your problems with wordpress you could of went to php.net and figured out how to corect the code, but you would rather go into detail how not even windows has this bad support. you must be 13 and have 0 ideas on business, you complain when you could find yourself a solution, very sad, we can see why your economy is bad, you all act like children

  • Thanks for that polite and mature comment.
    Sounds much like the other pointers to solutions I've gotten.

  • I totally agree with everything you are saying. Wordpress 2.5 is a nightmare. It's corrupted my database and basically nuked my blog which was working fine on 2.3. I refuse to spend 3 days in bogus support forums, and trying to return to ver. 2.3 is a mess also...I can't even log in. Maybe it's time to nuke 3 years worth of work. Thanks Wordpress.

  • Lori,

    what can I say? I just went over to your site and saw ... nothing. At least my stuff still shows up (besides the feed items, which cuts off most of my readers from my site ...).

    Tonight I'm going to hunt around other resources to solve my feed problem and the other issues I'm just going to live with until I have time to switch to something else again.

    Hang in there, Lori, and the best of luck with your site.

  • I love the way people who decide to have a go at a blogger never leave a link for you. Quite amusing isn't it? Good response though
    :)
    Personally I think the post was well thought out and written for what it's worth. I have NO intention of upgrading to 2.5 anything until it's stable.

  • anonymum;

    yeah, I thought of deleting it for a second but then decided to leave it here as an example of well, ... an example. I have been a member of so many forums these past 10 years and more that you get used to that kind of spam.

    Re not upgrading: Correct me if I'm wrong, but I thought they're not supporting the 2.3 branch anymore? Not that I read up too much on that. In light of the spam insanity I'm experiencing with WP as well, I'd hate to leave a couple of future security holes open. What's your take on that?

  • I know nothing about Wordpress, so I can't comment on that, but I think rijula's post is way over the line - and I'm not even commenting on the bad grammar. If you have nothing positive to add, like trying to find a solution, just leave and post somewhere else I'd say.

  • Right on. :)
    No need to worry though. We have all learned to at least ignore this kind of stuff, more or less.

    I hope I can fix the feed issue soon. So far, no luck. I want to push more posts out there, but it's pretty pointless with all the problems right now.

  • Ah, fixed the feed.
    Don't ask me how, but it works again. :)

  • As you know I'm a member of the same forum you are, and there are people there who host up to 40 blogs and refuse to upgrade because of the bugs. I'm relatively new to the admin side of things, however, when people I trust, like those I've mentioned, are refusing to upgrade, and given many of them have a solution for anything that may go worng, I'm not overly concerned at this point.
    My instincts tell me there is much "spin" happening on many things w/press at the moment. I'm at the point where if they don't fix the bugs in 2.5.x and I do have some problems with my current version, I may be tempted to go to the dark side and use *gasp* blogger! Or at least look at other options.
    I've always been a big advocate of W/press because of ease of use. A person could not know what a blog was, go to w/press.com and be up and running inside 20 mins. Not so much these days.
    There is much unrest among w/press users, and not just those on the free site. They're peole that have supported w/press from day 1 and do their own hosting for many users and have 4 or 5 blogs of their own to boot.
    They should have kept it simple as it's always been. I have blogs on w/press.com, so I do have 2.5.x, and I'm not at all impressed like many others.
    My aoplogies for the saga btw...once I get going I have trouble shutting up!
    Going home now :-)

  • No need to apologize for any saga. As you've seen, my posts suffer from totally excessive wordiness, to boot (that's triple-emphasis right there). :)

    I can't say much about Wordpress other than I think it doesn't work for me, really. Coming from Expression Engine - which was far too convoluted for me to get good results quickly - I'm used to publishing software that works well. Wordpress doesn't.

    I just don't know if I have the energy to redo my site yet again. If you read through some past posts on redesigning this site (category: Site) you'll see where I'm coming from, health issues and all.

    Now that the feed is fixed, I'll just keep steamin' along here ... until the next bug shows up. With my rather short-lived WP experience, it certainly won't be all that long until that happens.

    Don't be a stranger 'round here.

    Cheers!

Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>