• Hello,

    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 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, but if I specify index.php it’s blank (instead of redirecting). With debug on it complains about headers already being sent from pluggable.php.

    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,
    Ian

Viewing 14 replies - 1 through 14 (of 14 total)
  • Try:
    – switching to the default theme by renaming your current theme’s folder in wp-content/themes using FTP or whatever file management application your host provides.

    resetting the plugins folder by FTP or phpMyAdmin.

    – re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress.

    – re-running the upgrade manually using wp-admin/upgrade.php.

    Thread Starter irifkin

    (@irifkin)

    Hi,

    Thank you for your reply.

    I reverted back to 3.1.3, switched to the default theme and tried again. Same behavior.

    I tried removing all plugins again. Same behavior.

    I tried a fresh download of WordPress 3.1.3 downloaded from www.ads-software.com except for wp-config and wp-content (themes, and blogs.dir). Same behavior.

    I tried running the upgrade from wp-admin and that also shows the same behavior.

    Thoughts?

    Thanks again.

    I tried a fresh download of WordPress 3.1.3

    Uh? You should be uploading a fresh copy from WordPress 3.2.1

    Thread Starter irifkin

    (@irifkin)

    Typo in my previous post. Yes, a fresh copy of 3.2.1 is what I tried.

    Sorry for confusion! Any ideas?

    Ian

    With debug on it complains about headers already being sent from pluggable.php.

    Does that still happen with Twenty Eleven active?

    Thread Starter irifkin

    (@irifkin)

    Hi again,

    I just double checked. I do not see the error about pluggable when using the Twenty Eleven theme, but it still doesn’t work. Going to /index.php now redirects back to / like it should, so maybe that part was theme related.

    On the homepage it looks fine except for a message in a sidebar that says:

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

    I can click around the non-admin part of the site and see posts and pages.

    If I go to /wp-admin it’s blank.

    I can go to /wp-login.php which loads fine and I can authenticate successfully. It redirects me to /wp-admin which is still blank. Going to /wp-admin/index.php prompts me to download the index.php file which is blank.

    Going back to / it looks OK and I see my admin menu at the top, but the links (all to specific .php files in /wp-admin) all prompt me to download a blank file instead of loading the page.

    I hope this helps better explain the issue.

    Thanks again.

    Thread Starter irifkin

    (@irifkin)

    FYI, we use the Multisite functionality (by sub-directory). It seems that I can’t see the front-end of the other blogs after I upgrade either. The wp-admin pages for the sub-blogs show the same behavior as noted above.

    Thanks.

    I’d suggest posting in the Multisite forum.

    Thread Starter irifkin

    (@irifkin)

    I wasn’t thinking it’s a multisite issue and didn’t realize there was a special Multisite forum.

    Thanks.

    Thread Starter irifkin

    (@irifkin)

    Hi,

    If anyone wants to see my ramblings in the other forum you can find it here: https://www.ads-software.com/support/topic/upgrading-to-321-blank-pages-header-errors-etc-10-posts

    This actually was not a Multisite issue. I tried a new regular installation and was still seeing the blank page errors. Ends up that the WordPress documentation is out of date regarding the required version of PHP. I upgraded PHP and it works!

    Regards.

    Ends up that the WordPress documentation is out of date regarding the required version of PHP.

    Link for the incorrect documentation?

    Thread Starter irifkin

    (@irifkin)

    Link for the incorrect documentation?

    https://www.ads-software.com/about/requirements/

    This claims it will work with PHP 5.2.4 unless I’m reading it incorrectly. I was running 5.2.5 and it did not work. I upgraded PHP to 5.3.6 and it works.

    Regards.

    WordPress has been tested on PHP 5.2.4. Perhaps there was something funky in your previous PHP version install?

    Thread Starter irifkin

    (@irifkin)

    Hi,

    I’m not sure what “something funky” 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

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