WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Upgrading to 3.2.1 - blank pages, header errors, etc (10 posts) (29 posts)

  1. irifkin
    Member
    Posted 3 years 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.

  2. 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.

  3. irifkin
    Member
    Posted 3 years 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

  4. Okay, what PHP version are you running?

  5. irifkin
    Member
    Posted 3 years ago #

    PHP version 5.2.5.

  6. 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.

  7. irifkin
    Member
    Posted 3 years ago #

    Yes, JSON is enabled. Version 1.2.1 of JSON.

    Any other thoughts?

    Thanks again!

  8. Try the default, twenty eleven, theme.

  9. irifkin
    Member
    Posted 3 years ago #

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

  10. 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)

  11. irifkin
    Member
    Posted 3 years 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.

  12. 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?

  13. irifkin
    Member
    Posted 3 years 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.

  14. 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....

  15. irifkin
    Member
    Posted 3 years 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.

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

  17. mherzber
    Member
    Posted 3 years ago #

    I am in the same boat. I am getting seg fault error like crazy. I have already

    Try:

    - switching to the Twenty Eleven theme to rule out any theme-specific problems.

    - resetting the plugins folder by FTP or PhpMyAdmin.

    Then monitor the site for errors and see what happens.

    error log similar to

    [Tue Aug 02 22:51:03 2011] [notice] child pid 15707 exit signal Segmentation fault (11)

  18. irifkin
    Member
    Posted 3 years ago #

    Hi again,

    I tried a completely fresh install with a completely new database.

    I get to the the new setup page which takes me to /wp-admin/setup-config.php?step=1. When I fill in the details and click submit (which is an action to /wp-admin/setup-config.php?step=2) it prompts me to download a blank setup-config.php file.

    Somewhat interestingly if I type in the wrong db credentials in /wp-admin/setup-config.php?step=1 it will take me to /wp-admin/setup-config.php?step=2 where I can see the normal error message.

    Thoughts?

    Thanks.

  19. it prompts me to download a blank setup-config.php file.

    Okay, this means something's up with your server. PHP may be installed badly - which is really vague, and I am sorry about that, but ... look up 'PHP files downloading instead of displaying' in Google. There are a few possibilities :/

    You may be able to skate with upgrading to PHP 5.2.17 which is the latest of that branch, I believe.

  20. irifkin
    Member
    Posted 3 years ago #

    Here's something interesting.

    If I do a fresh install of 3.1.4 then upgrade to 3.2.1 it works fine.

    I then tried upgrading my 3.1.3 instance to 3.1.4, but it's not accepting my login credentials for some reason. If I can get that working, I'm wondering if it will upgrade to 3.2.1.

    Are you aware of 3.1.4 being a requirement to upgrade from (versus 3.1.3 or a fresh install of the latest)??

    Thanks again.

  21. Are you aware of 3.1.4 being a requirement to upgrade from (versus 3.1.3 or a fresh install of the latest)??

    None at all. That would be pretty counter to WordPress's usability, too.

  22. irifkin
    Member
    Posted 3 years ago #

    I then tried upgrading my 3.1.3 instance to 3.1.4, but it's not accepting my login credentials for some reason.

    I was able to login. Must be a session/cache type issue.

    But, then I did a manual install from 3.2.1 and it's back to the blank wp-admin pages…

    Hmm………

  23. I'm sticking with my 'Possibly janky PHP install' based on all issues reported :/

  24. irifkin
    Member
    Posted 3 years ago #

    Hi,

    I got distracted with other things, but I'm back!

    As you may recall I was running PHP version 5.2.5. I just upgraded to PHP 5.3.6.

    To keep things simple I'm trying a fresh install. If I purposefully put in incorrect DB info on setup-config.php (in Web browser) I get an appropriate error message. If I put in the right information though, it takes me to a blank setup-config.php page.

    Apache error log says:
    [Tue Aug 30 14:14:07 2011] [notice] child pid 19478 exit signal Segmentation fault (11)

    Any suggestions???

    Thanks.

  25. irifkin
    Member
    Posted 3 years ago #

    Scratch that previous message. I think I must have not restarted apache after upgrading PHP -- oops!

    A fresh install works now with the upgraded PHP.

    I'll see if I can upgrade my previous installation next...

    Stay tuned!

  26. irifkin
    Member
    Posted 3 years ago #

    It works! Thanks for pointing me in the right direction! I guess the WordPress documentation should note the new requirements for PHP version.

    Thanks.

  27. PHP 5.2.5 normally works. I can only speculate that your version had something weird?

  28. irifkin
    Member
    Posted 3 years ago #

    I'm not sure what "something weird" would be. I believe it was the standard PHP tarball from php.net. I'd be happy to send you the source files for our copy of PHP 5.2.5 if you'd like.

    Also, keep in mind our installation of PHP 5.2.5 worked fine for WordPress Mu 2.8 through WordPress 3.1.3.

    If other instances of WordPress do work with 5.2.5 maybe there is an option with the 5.2.5 install that I didn't do that comes with 5.3.6 by default.

    Anyways, I'm all set for now. Thanks.

  29. Lavinco
    Member
    Posted 2 years ago #

    I fixed my blank page problem by removing the final blank line in
    wp-content/plugins/all-in-one-seo-pack/all_in_one_seo_pack.php

    This has been a problem in the past with other admin login pages having blank lines at the end of php pages. Simply removing the last blank line usually fixes the problem.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.