Part 1 – General

Step 1

Design your error page as a static HTML page.

Step 2

You can upload the error pages to anywhere on you server, but I recommend putting them either in the root directory, or in a folder in the root.I put mine in a folder in the root called “errors.”

Step 3

Add the following line of code to your .htaccess file in the root of your site.

ErrorDocument 404 /errors/404.html

And for the other error messages, simply uplad the other HTML files and add another line in your .htaccess file and change the error code to whatever you need, like:

ErrorDocument 503 /errors/503.html

in my example code, obviously, I’ve got a folder called “errors” in the root directory of my blog, and I named my error message html files as the same name as the error I want to display.

Live Example

The easiest error page to test, (as well as the most used) is 404, or “Not Found.” Simply type in your URL, then a forward slash and then a bunch of jibberish, like this:

http://www.bittbox.com/fghjkdfghdfgkjh

And that’s it. If you are having trouble seeing your error messages, you might check your file paths in your .htaccess file, as well as the file paths to images in your HTML and/or CSS, depending on how you have it setup.

Part 2 – Custom 503 “Service Unavailable” Page using WordPress and the Maintenance Mode Plugin

Step 1

Obviously, have the Maintenance Mode plugin installed and activated. Maintenance Mode lets you display a custom message while your site is down, whether your upgrading, or making a new theme, or simply doing maintenance of any kind. Nowadays, wordpress shows an error 503 (most likely your server default) “Service Unavailable” error when you do an automatic upgrade, so customizing this 503 error can make you rest a little easier when you need to upgrade your worpdress. (which wordpress users know, happens often.)

Step 2

Copy your 503.html error you already made in Part 1, and put it in your wordpress theme directory. Then rename it to 503.php. Even though it’s most likely a simple html or xhtml file, the Maintenance Mode plugin needs a “php file extension, and it has to be in the same folder as all of your theme files. (don’t forget to move any images, and check image URLS during this process, as well as any image URLs in your CSS for your 503.)

Step 3

In the WordPress Dashboard, go to Settings > Maintenance Mode and select the custom 503.php option under “Splash Page Theme.”

Done

In order to test the custom 503 that will display when you do upgrades (as long as maintenance mode is active before you upgrade) you can just activate it for a minute to see what it looks like, but you have to either log out, or use a different browser where you aren’t logged in to your site.

Conclusion

Custom error messages can be cool, and I recently learned a little about how to make them, so I thought I would spread the knowledge. It was way easier than I previously thought, and all you need is FTP. As I mentioned earlier, some customizations may be available from your host admin panel, but using the .htacess method, you can add as many as you want, and therefore have more control.

Here’s a link to the most common Apache Error Codes»

Here’s a link to all Apache Error Codes »

A few days ago I submitted a trouble ticket when some software on my GoDaddy server locked up, and a few hours later, they replied stating that they had resolved the issue, and charged me $75. Great……wait, what? My site doesn’t work anymore!

I hadn’t changed a single setting on my server and the BittBox homepage wouldn’t load. So I called GoDaddy again, and another 6 hours go by, and they tell me that it’s my .htaccess file that’s causing the problem. So, in a nutshell, not only was my site down, but I PAID GoDaddy $75 to f*ck it up. Awesome, right?

Anyway, that’s just one of many stories. I was sooo pissed, I didn’t even flinch. I immediately called MediaTemple and bought a new hosting account, and started uploading. After I was about 50% done uploading, I switched the DNS and this morning I canceled my GoDaddy account. I’m looking forward to this fresh start, and again, I apologize to those of you who were inconvenienced by GoDaddy’s incompetence.

~Bitt

]]> http://www.bittbox.com/news/server-maintenance/feed 13 http://www.bittbox.com/news/new-server-2 http://www.bittbox.com/news/new-server-2#comments Thu, 17 Jan 2008 05:19:52 +0000 Jay Hilgert http://www.bittbox.com/news/new-server-2/ If any of you have noticed anything weird lately around the Box, or are having trouble loading the RSS feeds, please give it a day or two. I just migrated BittBox to a brand new dedicated server, and it can take up to 3 days before the transition is totally done. Sorry for the inconvenience.

~Bitt

If anyone has any info or would like to help (I’m not a WordPress Guru) you can email me at contact(at)bittbox.com.

~Bitt