Upgrading to 3.2.1 – blank pages, header errors, etc (10 posts)

  • Resolved irifkin

    (@irifkin)


    12 years, 8 months ago

    Hello,

    I posted this originally in the main forum but was directed here.

    I am trying to upgrade from 3.1.3 to 3.2.1. I normally do a manual installation, but I also tried the automatic installation.

    After the 3.2.1 files are in place, I cannot get to any admin pages. In fact when going to a directory like wp-admin it appears blank, but when specifying a wp-admin PHP page (e.g. wp-admin/index.php) it prompts me to download the file — which appears blank.

    The front page of the blog loads as well as posts and pages. When using themes other than twenty eleven I get some other errors and weird behavior. I’m getting not founds when navigating to sub-blogs (multi-site by directory). Not sure if that’s because of their themes or this larger issue. When going to a sub-blog’s wp-admin pages I see the same behavior as the default blog at /.

    We have a few plugins and even tried disabling (and completely removing them) before install, but we’re still seeing the same error.

    Is anyone else encountering this? Any suggestions?

    Thanks.

Viewing 15 replies - 1 through 15 (of 28 total)
1 2
  • Andrea Rennick

    (@andrea_r)

    12 years, 8 months ago

    Blank is a php error. You need to look for error logs on the server and read them.

    Disable all your plugin. Yes even any in the mu-plugins folder if you used it.

    I’m getting not founds when navigating to sub-blogs (multi-site by directory). Not sure if that’s because of their themes or this larger issue.

    That would be the htaccess in charge of that. look and see if that file got blown away or moved during the upgrade.

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    Hi,

    Yes, PHP error, but specific to this version of WordPress. Rolling back to 3.1.3 it works fine. In Apache error log I see the following:

    [Mon Aug 01 20:57:17 2011] [notice] child pid 12595 exit signal Segmentation fault (11)

    I disabled all plugins and even temporarily deleted them completely and still see the same.

    htaccess is still in place.

    Any ideas?

    Thanks

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    Okay, what PHP version are you running?

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    PHP version 5.2.5.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    That SHOULD be okay, though check to see if JSON is enabled. You can make a phpinfo() page and scan that to see if your PHP was installed with JSON. That should work anyway on 3.2.1 and PHP 5.2.5 but it’s worth checking.

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    Yes, JSON is enabled. Version 1.2.1 of JSON.

    Any other thoughts?

    Thanks again!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    Try the default, twenty eleven, theme.

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    Tried twenty eleven theme. Same result (/wp-admin pages are blank).

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    Look in the error log (NOT the Apache one, the one for your site that stores the php errors). There should be SOME error in there.

    (a seg fault implies you have a bolloxed install, BTW)

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    Look in the error log

    Not much in the PHP error log. No messages when going to the /wp-admin pages. When going to the front page at / I see the following error:

    PHP Notice: Undefined index: filter in wp-includes/default-widgets.php on line 382

    (a seg fault implies you have a bolloxed install, BTW)

    Perhaps that’s related? Any suggestions?

    Thanks again.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    Haven’t seen that error since 2.8… Wow.

    As you can’t get to the wp-admin page, how did you switch to twenty eleven?

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    As you can’t get to the wp-admin page, how did you switch to twenty eleven?

    I reverted back to 3.1.3, changed the template, then re-upgraded to 3.2.1.

    Haven’t seen that error since 2.8

    Any idea how it was solved then?

    Thanks again.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    They fixed it in WP core (which is part of why my mind boggles).

    Are you manually upgrading?

    How would you feel about installing a fresh 3.2.1 version in a subfolder and see if THAT works? Maybe you have a DB issue….

    Thread Starter irifkin

    (@irifkin)

    12 years, 8 months ago

    Hi,

    I normally manually upgrade. I also tried the automatic upgrade though.

    Could be a database issue, especially with all these attempts!

    This is a test instance so I’m not too concerned even about losing my data, but I’ll want to make sure I can upgrade before I attempt on my real/prod instance.

    Thanks.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    12 years, 8 months ago

    That’s why I said to make a second, separate install.

Viewing 15 replies - 1 through 15 (of 28 total)
1 2
  • The topic ‘Upgrading to 3.2.1 – blank pages, header errors, etc (10 posts)’ is closed to new replies.