• Are there any issues to rolling back a 2.1 upgrade back to 2.07? There seem to be a lot of issues with 2.1, and I’m wondering if perhaps waiting until the bugs are sorted out might be better. I’m lucky that I backed up absolutely everything from my server, and unless someone knows of why I shouldn’t do this I think I’m going to.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Unless you have a backup of your database, rolling back would be difficult.

    Most of the “issues” with 2.1 are plugins not working the way they used to. There’s some minor issues regarding category display, but for the most part it’s stable and good. If you’ve already upgraded, it would probably be better to just fix whatever issues you have and roll with it.

    Thread Starter thelazygeisha

    (@thelazygeisha)

    Hi Otto42,

    I do have a backup of my database, and after I posted this I discovered that the upgrade script makes changes to the wp database tree, so rolling back would be more involved than I’d like. However, as for the issues, I think they’re more involved than just plugins not working.

    There are major issues with the wysiwyg/Code View post editor & feed generation. I know others have more specific issues related to their sites, but the post editor is a universal problem for all of us.

    The issue: You cannot seem to to toggle between wysiwyg and code view (formerly known as HTML view). Personally I think the post editor was fine the way it was and see no reason why it was changed, and it’s enough of a problem to make me consider rolling back.

    So this is an issue that I’m unable to fix on my own. If anyone has any data on how to correct this I’d really appreciate it. Thanks.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    the post editor is a universal problem for all of us.

    Want to bet on that? Works great for me. ??

    The issue: You cannot seem to to toggle between wysiwyg and code view (formerly known as HTML view). Personally I think the post editor was fine the way it was and see no reason why it was changed, and it’s enough of a problem to make me consider rolling back.

    I can toggle back and forth between the two just fine. I think you may want to make sure that your browser is not blocking some of the javascript files from loading properly. Some people reported that Greasemonkey was messing them up a bit on the editor.

    Also you’ll want to verify that all the .JS files in the 2.1 ZIP file were uploaded to your host properly, otherwise anything could be wrong with the editor.

    As for why the post editor was changed, the reason was that it was *not* fine the way it was, creating lots of mistakes in the code and generally everybody hated it because it did not work properly. The new one is actually much improved, and seems to work much better, on the whole.

    The only problem I have with it is that the scroll bar is slightly out of frame when I’m in the Code view. But it’s still half visible and usable, so it’s not a deal breaker or anything.

    Hi folks,

    If I could figure out a more central place to post this, I would…hopefully someone with some pull will read it.

    I’m also rolling back from 2.1 to 2.0.7. I’m having horrible WYSIWYG errors (edit link dialog boxes coming up blank), everything is running more slowly, and the list goes on.

    But all that isn’t what’s chasing me off. What’s doing it is the consistently defensive and snotty tone that pops up when someone raises an issue. 2.1 is *not ready for prime time*, and jumping up and down and saying “Yes it is, it works fine for me” isn’t going to get it there.

    Yes, yes, I know. Unhelpful post. Fine. Take it down.

    dont get oo discouraged i upgraded and i’m having huge issues, i followed every upgrade step to the letter in the detailed instructions and i got one response from a member describing how to roll back my version. So i feel your pain i am more than a bit unhappy.

    sfcrotty: the consistently defensive and snotty tone that pops up when someone raises an issue

    Hmmm…
    https://www.transycan.net/blogtest/2007/01/24/to-upgrade-or-not-to-upgrade-to-wp-21/

    Moshu: Would you care to elaborate on the meaning of your reply? I don’t want to misinterpret your comment.

    What I meant: I don’t think everybody is that defensive about 2.1.

    deleted by author. combative and unhelpful.

    Thread Starter thelazygeisha

    (@thelazygeisha)

    “Want to bet on that? Works great for me. ;)”

    I’m not a betting woman Otto42, but I would agree with sfcrotty here when he observes the defensive tone some people seem to take when others question the stability and usability of 2.1

    Now we’re onto 2.1.1 and as bad as I think 2.1 is, I rolled back my 2.1.1 install because it was worse.

    Here’s the thing Otto42, most of us don’t know each other must past a name we read on the screen. You don’t know my level of technical expertise and I don’t know yours, so it doesn’t help to inject attitude into what can often be a very frustrating experience.

    I’m not trying to mother you here, but manners would be appreciated.

    Several people that I actually do talk to have all indicated a real regret in upgrading from the 2.0xx series to 2.1 – that is a fact. From developers who cannot understand why WP would mesh categories and links together to some of the crazy changes to TinyMCE.

    Thanks.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘2.1 back to 2.07?’ is closed to new replies.