• Resolved sacredpath

    (@sacredpath)


    Automattic Happiness Engineer

    Does anyone know what I would have to do to roll back to 2.3.1 from 2.3.2? I have a couple people that I maintain blogs for, and since I upgraded them to 2.3.2, they have been having problems editing draft posts and pages, and with widgets. Disabling all plugins has not helped, neither has clearing browser cache and cookies. The are both on XP and have Firefox 2.0.0.11 and IE7 available to them. Both of their computers are current on updates. Neither of them were experiencing any problems before I upgraded them to 2.3.2. I’ve even uploaded 2.3.2 again on each thinking perhaps there was an FTP issue or file corruption, but that did not work.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter sacredpath

    (@sacredpath)

    Automattic Happiness Engineer

    Just in case anyone needs to know: php version 4.4.7, Apache version 1.3.39 (Unix), MySQL version 4.1.22 standard

    Never any problems with this configuration with 2.3.1.

    Just delete the 2.3.2 version and reupload the 2.3.1 version from http://wordpress.org/download/release-archive/

    No database changes transpired from 2.3.1 to 2.3.2

    I thought there were security issues with 2.3.1?

    That’s the only reason I bothered to upgrade.

    Thread Starter sacredpath

    (@sacredpath)

    Automattic Happiness Engineer

    @michaelh
    Thanks for the quick reply and information. I’ll try a few other things before reverting them back to 2.3.1. One is uninstalling and reinstalling Firefox to see if that will help. I should hope there will be a 2.3.3 upgrade coming out soon that will take care of the issues. There seems to be a few.

    With 2.3.2 on my blog I’m not having any issues, but then I’m on Mac.

    I upgraded from 2.3.1 to 2.3.2 using Fantastico – Host Monster, but the blog posts and recent posts won’t show up in the front home page. I have tested the current theme with 2.3.2 version to other blogs and it works perfectly.
    I think that it must be data base error with 2.3.2 version. Can anyone help me?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Reverting from 2.3.2 to 2.3.1’ is closed to new replies.