Yup, we did it. We used the automatic upgrade function in Wordpress to upgrade to Wordpress 2.8.3 and ended up with a white screen of death (WSOD) shortly after. Bummer.
Thought we’d post our fix to our particular problem since none of the posts we found elsewhere has this fix. Note: I’m not saying this is going to work for you.
We have not updated our wp-config.php since we first installed WordPress. We noticed in 2.8.3 (and probably earlier) that the format and settings in the wp-config.php is different. In our case, we manually took the 2.8.3 version of wp-config-sample.php, entered our specific information for the various keys and DB info from our original wp-config.php. After doing this we saved this to our WP root folder overwriting the old wp-config.php with this file.
Abracadabra! Problem fixed. So, does the automatic upgrade not touch the wp-config.php for changes? Well, apparently not and apparently I am supposed to read the readme.html file included in the WordPress 2.8.3 download. Of course, if you use the automatic upgrade functionality, you don’t see the readme.html file.
In our case, we manually downloaded the release after our WSOD problem started. After figuring out the problem, we saw that the readme.html tells you to do exactly what we ended up doing. Doh! That’s what we get for being IT professionals that fail to read the upgrade instructions before upgrading , which we do with our client solutions, but failed to do for our simple blog. 
Hope this helps you. Blessings.
Popularity: 2% [?]
