2.9 my story.

  • so i hear all this great stuff from wordpress about 2.9.
    i login to my dashboard and see the prompt to upgrade. i hit auto upgrade and my site exploded.

    running the auto update destroyed the db i have which sadly just included hundreds of entries for a remix contest we are running. it took me awhile to see what the issue was, so after spending hours and hours running through disabling plugin folders, changing version numbers in sql, forcing db upgrades staring at a blank site screen and getting insufficient permission errors i finally had to have my host restore me.

    $125 later i am back to a version of my site that backed up in october. although i have all the contest entry files, i have no contact information for any of them due to the db getting destroyed.

    i have been using wordpress for years and run 3 sites using it, i also have 2 client sites on it. yes, shame on me for not backing up everything right beforehand, after all the successful years with WP, i just trusted everything would work. never again will i do that. is 2.9 ready for primetime? judging by the forum issues i would say not. don’t get me wrong, ultimately it’s my fault for not backing up, but i have never had so many issues with a wordpress release.

Viewing 10 replies - 16 through 25 (of 25 total)

  • My experience (after the previous nightmare that was upgrading from 2.7 to 2.8)…

    Upgrading five blogs on the same host from 2.8.6 to 2.9. Four went ahead without a hitch. On the last one, I got a 500 Internal Server error message from the webhosting service.

    Tried to get back in… kept gettting a maintenance message. Decided to upgrade manually. Worked without a cinch except for a message saying that the previous automated update did not complete (even though I was already using 2.9!). Eventually got rid of the message by doing an automated reinstall.

    Total time taken: 3 hours (including time taken to backup my databases prior to pressing the button). Not too bad considering the few days my sites were down when I did the last big upgrade from 2.7 to 2.8 ??

    Do the WP developers have any idea how most users hate the upgrades? Really despise and dread them?

    I hate the upgrades.

    WordPress is always change for the sake of change. I install a new version, fix whatever is wrong with my database afterwards, (it’s usually something like the size of the database or something minor but annoying) and then 2 weeks later, another upgrade, more fixes, etc. What are all these upgrades gaining the user but more headaches? For about a year now I’ve wanted to stop upgrading but then the plugins stop working or something else. The users don’t need all these upgrades. The developers are drinking too much Red Bull or something is making them overly hyperactive. Please, please stop “improving” something that works and let us just USE it.

    I’m not upgrading any more. I’m sick of all these problems every single time!

    At the moment I can’t even use my admin panel and can’t find a way to fix it. Maybe I’ll just move to Typepad or something that isn’t upgraded so damn much.

    I’m using wordpress for years and never had major issues. What I learned from senior webmasters to wait when new upgrades are released and carefully read the forums of wordpress specialists. Main problem I see, the different server configurations of all those providers around the world. At our region, almost all servers have, “safe mode on”. So the wordpress developers can hardly test all those different scenarios when a new wordpress engine is installed on a specific server. Is the wordpress software able to properly write all those entries into the database or are some functions blocked by the server configuration? Are too many plugins causing trouble? At the last upgrade to 2.8.6 I had to ask my provider to extent the server’s cache memory from 16 MB to 64 MB. Now it says, 2.8.6 is using at an average 31 MB cache memory. Could be like any OS, that requires 20% free memory cache to function properly, that the wordpress engine doesn’t work properly when it’s getting tight with cache memory.
    Good thing is, all issues are solved so far, just be patient. Some things take a bit of time to be identified.

    IO installed a fresh 2.9.1 WP for a site (www.thereikishare.co.uk). Everything went ok as a fresh site did. the 500 error I get is with plugins. There arew some plugins, that take a few activations for them to activate. Others that are reporting as working with 2.9 are not activatying at all.

    I’m new to WP, and only have a few sites, all fresh installs, and no updates. Is my 500 error as plugin compatability problem, or a 2.9.1 problem??

    Thanks ??

    How does a version jump from 2.8.6 to 2.9/2.91? It’s like celebrating a birthday and jumping from 25 to 31.

    Version.Release.Modification Level is how the numbers work. With WordPress, a change in Modification Level means bug fixes, usually security-oriented.

    A change in Release means new functionality and maybe some look/feel.

    A change in Version is a major initiative, usually accompanied by a new Vision.

    And thus it has always been. I started my Computing career in 1971, and IBM already had the same numbering system for their software.

    Interesting, thanks for the clarification Adiant ??

    I am one of those who are having an “issue,” and who doesn’t appreciate being yelled at by Otto.

    get a grip – nobody yelled at you

    If you folks don’t want to upgraqde – don’t. But don’t come back here whining your site was hacked when there is a security release.
    All upgrade problems can be avoided/overcome by backing up – that simple.
    Sorry if you’re really sensitive and think i’m yelling.

    Dear all samboll – I’m still on a learning curve but enjoyed all the stories and the tips! I did backup my MySQL database but now that I need it I can’t figure out how to use it… but hope I can get my Dashboard & blog site back up in the meanwhile & hopefully with samboll’s help…

    I’m very curious as to why anyone would think Otto42 was “yelling.” Besides the fact that his response was written, not spoken, he didn’t reply using ALL CAPS or any exclamation points.

    Regarding new versions of wp: Every problem I’ve experienced since I started working with wordpress two years ago, including dozens of installs and upgrades, I’ve always traced back to a mistake on my part. I don’t mean forgetting to backup anything or read the forums, I mean I did something wrong and the fault was completely mine.

    May I also remind everyone that plugins and themes can’t be updated to be compatible with the next version of wordpress until it actually exists? Therefore, any you have installed should be considered outdated until proven otherwise.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘2.9 my story.’ is closed to new replies.