Viewing 10 replies - 46 through 55 (of 55 total)
  • I have 2 suggestions for the instructions. First the instructions suggest considering Maintenance Mode plugin. Then the instructions say deactivate ALL plugins prior to starting the upgrade process. That seems to be a conflicting instruction. Second, it seems to me the instructions should have the download of the new files as the first step. There is no reason to deactivate all your plugin and then wait to download the files before moving on…

    I would upgrade feature where blog admin can click the “Upgrade” button and upgrade the blog from within admin area of WP,without downloading and uploading new WP files etc.

    I recently upgraded successfully to 2.3.2, but I have noticed that my blogroll widget has disappeared from my sidebar. Moreover, in the ‘widget’ tab in ‘presentation’ there is no blogroll widget available. Does anyone know what’s likely to have happened and how to put my blogroll widget back in the sidebar?

    By the way, I too feel this is somewhat ‘over my head’ as earlier comment said. You can check (I think) that the new version is upgraded by looking at the bottom of any admin page, where the version should be displayed

    My internet connection is outrageously slow (0.25Mb) so I cannot upgrade to 2.3.2 via FTP. Installing 2.3.1 via Fantastico and cPanel works fine.

    With a new installation (no posts), is it possible to just replace the 16 files that have been changed without anything breaking? Will that make it effectively WordPress 2.3.2?

    Thanks in advance!

    Another option is to wget the latest version in SSH,unzip and replace current files,again in SSH.

    I am also experiencing the following problems after upgrading from 2.3.1 to 2.3.2:

    I can not edit any posts.

    I can not write posts (it just goes to a blank page with the menu and the footer)

    I am using K2 and it seems to break the K2 sidebars — I was able to fix it with the Disable WordPress Widgets plugin.

    Anyone know of fixes or workarounds to at least write posts or edit them?

    WAIT, THIS JUST IN: I solved my problems by getting rid of 2.3.2 – I found that I still had a copy of my 2.3.1 site. I overwrote 2.3.2 and all is happy in the world!

    I am having the same issue as some of the others: After several attempts to upgrade to 2.3.2, my Admin Dashboard still says I need to upgrade to 2.3.2. I have now done the entire process three times, including following EVERY step in the detailed instructions. All three times when I ran the “upgrade.php” page, it said there was “nothing to update”.

    BTW…everything seems to be working FINE…I am just concerned that WP is not recognizing the update.

    Any suggestions? THANKS!
    Troy

    Thread Starter MichaelH

    (@michaelh)

    @tallensr

    At the bottom of any admin screen it shows the version of the WordPress files you have installed. If it says 2.3.1 then you do not have a completely intact set of 2.3.2 files uploaded to your host.

    Please consider deleting the WordPress files and reuploading as per Steps 7 and 8 in Upgrading_WordPress_Extended.

    There are no database changes from 2.3.1 to 2.3.2 so executing the upgrade.php is not really required–though it hurts nothing if you do it.

    Resource:
    Uploading WordPress to a remote host

    I am having same issue upgrading 2.3.1 to 2.3.2, only this is with a blank installation of WP (nothing has been set up yet, no catagories, no plug ins, standard installed theme). As in first time its been installed for this particular web site … The site itself is 10 years old, but the WP instalation is not even a week old yet.

    I’ve followed the instalation instructions and still get told that its been upgraded yet the Dashboard tells me I need to upgrade.

    I’ve trashed everything save the config.php file and uploaded the 2.3.2 update and still get the same deal, that I still need to update!

    if you please what is going WRONG?

Viewing 10 replies - 46 through 55 (of 55 total)
  • The topic ‘Version 2.3.2 is available’ is closed to new replies.