Further data:
http://e2web.biz
It is on the same server.
Have you tried:
– checking through Troubleshooting WordPress 3.1 – Master List
– deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).
– switching to the Twenty Ten theme to rule out any theme-specific problems.
– resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.
It isn’t a plugin problem. I found the answer here -> http://www.tlswebsolutions.com/wordpress-3-1-upgrade-frontend-blank-site-backend-okay-iis/
You are wasting people’s time by continuing to tell them to disable plugins. Seriously, it dos not help their aggrivation to keep hearing such lame advice. This is actually a serious problem that needs to be looked at by the development team. Myself, I am running IIS 5.0 under Win2k. No, unless someone fronts me the money, I am not upgrading the server anytime soon. 😛
Seriously, it dos not help their aggrivation to keep hearing such lame advice.
Lame advice? Really? Gee – I wonder how I missed that in the 30,000+ topics I’ve helped out in?
Myself, I am running IIS 5.0 under Win2k.
Did you mention at any time that you were running WP under IIS? And a pretty old version of IIS at that? Or didn’t you think that might be a factor? Did you beta-test any of the 3.1 release candidates? Or did you simply assume that all core developers were psychic and/or had access to every server type on every OS under the sun?
