Comments

  1. Thanks for the post Ryan. I ran into the same problem tonight and wouldn’t have thought about just deactivating the plugins. Three seconds later and I could upgrade again.

    June 6, 2011 at 9:25 pm |
  2. Brilliant solution!!!!!! Thank you so much

    July 11, 2011 at 3:00 am |
  3. jonhjonh:

    Hello Ryan,

    good idea to post this! I have found that a lot of wordpress users have trouble with this. I had this exact same issue too, and your solution worked until 3.1.1.

    But now, trying to update to 3.2.1, it does not work. I deactivate 14 plugins, and try the automatic update, and it fails, giving me the error again. Havent found a workaround yet. If you do, would be interested to know.

    Cheers

    Jonhjonh

    July 15, 2011 at 7:03 am |
  4. You sir are the MAN!!!

    August 25, 2011 at 1:18 am |
  5. Joe:

    trying to update to 3.2.1.

    It worked fine for me. I used the BULK ACTION and turned off all the plugins and the update from 3.1 to 3.2.1 worked flawlessly

    August 25, 2011 at 1:31 pm |
  6. Aghper Jan:

    Thank you Ryan,I had the same problem after following your post i was able to successfully upgrade to the latest wordpress version.thank you

    September 1, 2011 at 8:25 pm |
  7. Works!! Many many thanks!!!

    September 3, 2011 at 2:43 am |
  8. David H:

    Ryan! A Merry Christmas to you!
    I was running a WordPress development version and could not update to 3.3 due to that fatal error in class-http on line 1426.

    Tried various “fixes” including php.ini turn off safe_mode and various memory configs.

    Then I found your suggestion. I had turned off a number of plugins but NOT ALL.

    Deactivated rest and got my Auto Upgrade lickety-split!

    Thanks for the tip!

    December 25, 2011 at 1:27 pm |
  9. Thanks for the great tip! Was able to get my update done in no time by turning off the plugins!

    Cheers and Happy New Year!

    January 5, 2012 at 3:35 am |
  10. Thanks for posting this. It worked great

    February 2, 2012 at 11:23 am |

Leave a Reply

You must be logged in to post a comment.