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

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.

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

Okay, what PHP version are you running?

PHP version 5.2.5.

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.

Yes, JSON is enabled. Version 1.2.1 of JSON.

Any other thoughts?

Thanks again!

Try the default, twenty eleven, theme.

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

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)

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.

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?

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.

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

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.

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