Upgrading 2.2 -> 2.2.1 broke site

  • I see bits of PHP code at the top of my page after upgrading to 2.2.1 (from 2.2). https://www.umbralechoes.com/blog/

    Starts with: >'; die(); } } ?> ]+(/.*)|i', '$1', $link ); } function wp_parse_str( $string, &$array ) { parse_str( $string, $array ); if ( get_magic_quotes_gpc() ) $array = stripslashes_deep( $array ); // parse_str() adds

    It’s as if PHP stopped parsing at a point it shouldn’t, and then just spat out the code. I did forget to disable all my plugins before upgrading, so after I saw that issue I moved all my plugins to a different directory, but I still get this problem. When I went to the initial upgrade script, the same code got spat out at the top of the page, then it said that no upgrade was necessary. Anyone have any clue what could be going on?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter UmbralEchoes

    (@umbralechoes)

    As further info, I can confirm that running the upgrade script is what causes this. I just tried a fresh install of 2.2 (using my old database and wp-config.php file). Everything worked fine. I copied the 2.2.1 files over. Site still worked fine. I ran the upgrade script, and the above behavior occurs.

    Also, here is my server information:

    Operating system Linux
    Kernel version 2.6.21-3_1.BHsmp
    Apache version 1.3.37 (Unix)
    PHP version 5.1.6
    MySQL version 5.0.27-standard-log

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Try getting a fresh copy of 2.2.1 from here and using that one. If you see random PHP code, then it likely means you have corrupted files somewhere, somehow.

    Given the fragment you posted, it appears that you have a corrupted copy of the formatting.php file.

    Thread Starter UmbralEchoes

    (@umbralechoes)

    I’ve tried downloading 2.2.1 multiple times, and installing into a completely fresh directory on my server (though using the same wp-config.php file). The blog then works perfect fine… until I try to run the upgrade script (wp-admin/upgrade.php), and then I start getting the funky PHP code at the top of the page. If it’s not necessary to run the upgrade script when upgrading from 2.2 to 2.2.1, then I just won’t bother with it. Still seems odd that the upgrade script would break the site, though.

    Thread Starter UmbralEchoes

    (@umbralechoes)

    Strike that. Just copying the 2.2.1 files over (and not running the upgrade script) causes this issue for me, after all plugins have been disabled. Guess I might just have to see if I can find exactly what files were changed between 2.2 and 2.2.1, and modify them manually myself.

    As a note, I tried downloading 2.2.1 onto 2 separate computers and uploading it to my website, just in case there was something wrong with one of the computers (bad hard drive sector, whatever). Same thing both times.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Upgrading 2.2 -> 2.2.1 broke site’ is closed to new replies.

Tags