Proving My Hosting Company Wrong
Don't be shocked by the sudden bland appearance of this blog. All the content is still here - only I have deactivated all plugins (except the spam filter) and put it back to the default theme. This is to (probably, possibly) prove my webhosting company (HostingZoom) wrong when they claim that all the code 500 Server Configuration Errors I've been experiencing recently are due to a faulty script in WordPress - probably a plugin or the theme I was using.
So I almost want there to be errors even now to justify me not sticking with this boring design. Merel and I are experiencing the exact same problems on www.zeroblack.org which is also hosted under the same account and on the same server (but with a seperate WordPress install). The theme we're using there is admittedly an extensive one, but also an expensive one... so we assume it has been tested.
Anyway, I'll keep you posted and in the meantime, if you do get a 500-error, try refreshing a few times and then let me know. Thanks you for your patience.
March 22nd, 2008 - 10:30
I got a couple of 500 error just now, followed by some timeouts when I tried to reload the page. I think Hosting Zoom should look into their setup. In it’s current form this is about as basic a WordPress install as they come. And you installed it through their control panel, which to me means that serving it without trouble is part of their service. There are tons of things you can do to bring shared server to their knees, but using Cpanel to install a very basic, low traffic blog shouldn’t be one of them.
Posting this comment gave me another 500 error, I’ll try again…
March 22nd, 2008 - 18:48
Yes, this morning I couldn’t even leave a comment because of the errors. Now Hosting Zoom wants me te give them the URL of a clean installed WP so they can test. I have installed an additional WP here: http://suzero.com/testwp/
Please do go there and leave comments just to induce the 500 errors.
Thanks in advance!
March 24th, 2008 - 00:13
UPDATE: Even the testwp site got the errors. See the next blog entry to read Hosting Zoom’s reaction.