Support » Installing WordPress » Downgrading from WordPress 3.3 to 3.2.1

  • Resolved LMP

    (@loizos16673)


    I just upgraded to WordPress 3.3, only to discover that several of the plugins I use are now non-functional.

    Is there a *painless* way of downgrading to version 3.2.1?

Viewing 15 replies - 1 through 15 (of 25 total)
  • over-write the wp-admin and wp-includes and the root WP folder files EXCEPT wp-config with 3.2.1 files.
    log in to admin and upgrade db if prompted

    I wish that was my problem! I can’t publish any blog posts at all! What is up with this new version?? How can I downgrade to the previous version?

    TiffanyM
    start your own topic

    Worked like a charm and saved my day!

    Thank you Samuel!

    Cheers,
    J

    Thread Starter LMP

    (@loizos16673)

    over-write the wp-admin and wp-includes and the root WP folder files EXCEPT wp-config with 3.2.1 files.
    log in to admin and upgrade db if prompted

    Tried that. Got nervous when I saw the ‘Upgrade DB’ message, and restored the DB from a backup I made just before upgrading.

    Thankfully, everything now runs normally in version 3.2.1 🙂

    By the way, I know that testing even a small number of plugins for WordPress compatibility is an impossible task for the WordPress development team, but there must be a better way to discover incompatibilities than the old ‘walk-into-a-door-to-tell-if-its-closed’ method.

    Why don’t you make the WordPress update mechanism check automatically in the online plugin database for each installed plugin’s compatibility status, and give the user a warning if his/hers plugins are reported to be incompatible *before* applying the upgrade?

    Can you give a little more detail on how to actually do what you’ve suggested? Where and how to I over write files?? Thanks

    Thread Starter LMP

    (@loizos16673)

    Can you give a little more detail on how to actually do what you’ve suggested? Where and how to I over write files?? Thanks

    Maybe I can help a little.

    1. First you need to be able to access your web host through FTP or a file manager (most web hosts have one in their control panel). Something that will allow you to actually view the files and folders that make up your web site. After you figure out how to do that, go to the next step.

    2. Then you need to download WordPress 3.2.1 to your computer and expand it so that you can see the individual files.

    3. Then you upload all the WordPress v.3.2.1 files (EXCEPT the folder named “wp-content” and the file named “wp-config.php”) from your computer to your web site (through FTP or file manager) and overwrite the existing WordPress v.3.3 files when asked.

    Finally, when you next try to log in to the WordPress admin interface, you will see an alert that the database needs updating. You then allow the update to proceed, and presto, you’re back to version 3.2.1

    awesome! thank you so much this helped me restore my wordpress admin cpanel after a failed install of WP3.3.

    very logical and easy to follow. Thank you!!!

    I am having very much the same issue as described above, and tried the mentioned fix, but it did not work. The error message I got before (after upgrading to WP3.3), and am still getting is –

    Fatal error: Call to undefined function is_rtl() in /home/ewillms/public_html/wp-includes/general-template.php on line 2102

    grabbing my editor, and going to line 2102 all there is there is – {

    I need help if anyone can figure this out

    I’ve same problem as ewillms but in different lines.
    WP3.3 upgrade disabled very important plugins for my website and I feel stuck now. Can’t downgrade & there is no update yet for those plugins :$
    WordPress should give a warning before upgrading!

    Thread Starter LMP

    (@loizos16673)

    @ewillms & Tony.N:

    Assuming you replaced all the v3.3 files with the v3.2.1 files, I’m guessing that there’s an issue with your database.

    I suggest starting a new thread. I doubt that the WordPress developers will continue reading a [resolved] thread.

    hello LMP
    i updrade to v3.3 and found that my visual editer loss,so i follow your teaching :
    1. First you need to be able to access your web host through FTP or a file manager (most web hosts have one in their control panel). Something that will allow you to actually view the files and folders that make up your web site. After you figure out how to do that, go to the next step.

    2. Then you need to download WordPress 3.2.1 to your computer and expand it so that you can see the individual files.

    3. Then you upload all the WordPress v.3.2.1 files (EXCEPT the folder named “wp-content” and the file named “wp-config.php”) from your computer to your web site (through FTP or file manager) and overwrite the existing WordPress v.3.3 files when asked.

    Finally, when you next try to log in to the WordPress admin interface, you will see an alert that the database needs updating. You then allow the update to proceed, and presto, you’re back to version 3.2.1

    now i can downgrade to v3.2.1,but my visual editer only appear 4 item,and i still loss many visual editer item,

    and in your download link v3.2.1,there is no file named “wp-config.php”
    only one file named”wp-config-sample.php”and one file named”wp-cron.php”

    thank for your help

    @lmp – I just followed your instructions to restore one of my sites after the upgrade to 3.3 failed and I was getting blank screens when I tried to access anything under wp-admin. Thanks for that tip!

    I have the same problem. I followed all te steps above. But even after restoring the 3.2.1 version and all its files by FTP the following error message does net let me enter my wp admin interface.

    Fatal error: Call to undefined method Arras_Widget_Tag_Cloud::WP_Widget_Tag_Cloud() in /home/deb47295/domains/mazzelfilm.com/public_html/wp-content/themes/arras/library/widgets.php on line 404

    Your support is highly appreciated.

    The problem is fixed… sort of.

    I discovered the content was the problem. I eliminated the wp-content folder to enter in the WordPress admin interface. Now I am putting back the content bit by bit to get the site in its former design.

Viewing 15 replies - 1 through 15 (of 25 total)
  • The topic ‘Downgrading from WordPress 3.3 to 3.2.1’ is closed to new replies.