WordPress 2.7 Blank Page Problem (Upgrade & Fresh Install)

I have the same problem as certificateno.

I tried upgrading and a fresh installation.
Admin-panel is inaccessible. So the theme can’t be changed and can’t be the problem. As on a fresh install the default theme is used.
Often there are corrupt or outdated plugins a problem. But this can also be ignored on a fresh install as there are only akismet and hello. I even deacivated those just for a try but it changed nothing.
The page source is empty so you can’t really tell where it stops working.
You can see it here http://blog.voodoomedia.ch

Certificateno Would you post a URL please?

voodoo13 There seems to be a problem with your header file Fatal error: Call to undefined function language_attributes() in /home/httpd/vhosts/voodoomedia.ch/subdomains/blog/httpdocs/wp-content/themes/default/header.php on line 2

This information <?php language_attributes(); ?> is not being completed. I don’t know if this is the problem but header.php is used by many files.

I found in your phpinfo a very interesting detail – I reported the problem about very slow loading of the pages.

DD32 found that it could be a problem with cURL – and the interesting detail now:

On your server there is exactly the same version of libcurl:

CURL Information libcurl/7.10.6 OpenSSL/0.9.7a ipv6 zlib/1.1.4

I know this doesn’t solve your problem but I think we found a hint that this libcurl version is not compatible with WordPress 2.7 – or the other way round.

After the 2.7 upgrade everything works great, except that the <blog_root> page is blank. When other URLs are loaded, everything is fine, except whichever page is configured as the default (the content displayed for the <blog_root> appears blank. I can switch the default pages around. Once a page is not the default, it loads fine and whatever the new default is goes blank. I tried without the plug-ins, with the default wordpress theme, verified that the permissions are okay, reinstalled the 2.7 update, injected code in <blog_root>/index.php …

ini_set(‘display_errors’,’1′);
ini_set(‘display_startup_errors’,’1′);
error_reporting(E_ALL);

… to print any warnings, but I’m not getting any errors either. Nothing is broken except the [blog_root] and whatever page is defined to be the default content. I can switch the default content around – whatever was the default content displays fine from its permalink. The new default content shows a blank page from it’s permalink. The [blog_root] always shows blank, even if it’s configured to be the last ten posts. There’s no content missing. Any ideas?

http://optimalPortfolio.net/TaxPolicy/

I tried one thing that helped a little. I renamed [blog_root]index.php to __index.php so wordpress wouldn’t be able to find it. Then I added a redirect index.html from [blog_root} to one of the pages. Everything broke, but after I put it back, wordpress loaded the default page from its permalink (though it spent a really long time bringing it up for the first time). Seems like some sort of caching effect.

Anyway, the [blog_root] still shows up blank.

@taxpolicy – it’s working now. After renaming index.php to something that wordpress couldn’t find, trying to access a permalink (which of course failed), putting [blog_root]index.php back, AND reloading the [blog_root], it displayed just fine. Had to be caching of some kind.

Hello…Reading through this is rather interesting. After upgrading to 2.7 last week, what I have found is that some users can get in to the admin panel and others cannot. It is very consistent (but no obvious reasons for the two groups) — one user will always get the light blue screen of death (as we started dubbing it) and another never does. Fortunately all our admin people had no problems, but a good number of our author and editors and plain subscribers can’t get in. What perplexes me about that is that it would seem to contradict the notion that it’s something in the code as described above – I would expect php/wp 2.7 incompatibility to result in something across the board (which seems to be what most of yo have). We’ve got something quite different, some users affected and some not. I’ve poked thru the databases on the *_users and *_usermeta and not seen anything untoward, but I’m seriosly thinking some kind of database corruption.

I did get this error message at one point
Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate 35 bytes) in /my-wp-path/wp-includes/wp-db.php on line 636

which is basically one of the generic retrieval routines, not sure which query tripped that, of course.

Anyway, I am rolling back to 2.6 as I have no patience for even this much poking about, really, but hope maybe this sheds futher light. We tested pretty extensively with our different users on different browsers, clearing caches, cookies, etc. I did not attempt to change anything in the wp install itself apart from the upgrade steps. I can’t see how any of the above pertains, because they should be across the board and as I have said, only some of our users are affected.