Custom error pages (with bonus server-eating monsters)

404 error page monsterAs part of all the tweaking I’ve been doing since my website donned its new outfit on Monday, I made myself a custom 404 error page.

Usually, that “File Not Found” page generated by a 404 error is pretty boring. I mean, nobody wants to spend time on a dead-end page that doesn’t have anything useful or interesting on it, right?

Now, my custom error page makes me giggle. It has monsters! Drawn by The Oatmeal!

(And no, I totally didn’t steal these images — he gave them away and said that anyone could use them without even crediting him. A lot of people have used and riffed on them, so actually, I’m terribly behind the times on this trend.)

Have you checked your 404 error page lately?

Do you even know what your visitors see if they come to your site via a broken or misspelled link, or try to visit a page that you’ve taken down or renamed?

Try this: Go to your home page, and then type something random after the slash, something like YourSite.com/blah …unless your site actually has a page with the title “Blah,” of course. Then you’d want to use something different.

What do you see?

The default WordPress 404 error page simply says “Error 404 – Not Found,” which is frustrating and unhelpful. Your theme may come with its own 404 template, which might or might not be an improvement.

The Genesis Theme Framework 404 template, for instance, is based on your site archives, and includes links to every page, author, and category on your site, plus the last 100 (!) posts. That’s super-complete, but I didn’t want my thank-you pages showing up in that list, so I’ve edited my archives template to show only categories and posts. (Yes, that’s an affiliate link — I’m using the Prose child theme myself and am happy to recommend it.)

You might need a new 404 error page

Ideally, your visitors would never need to see a 404 error page, but we all know that weird things happen to websites. Permalinks get changed, site structures get reorganized, pages get renamed. Even scrupulous site owners who set up their permalinks perfectly the first time can’t keep other people from misspelling or mistyping URLs.

So as long as there’s a need for an error page, you might as well make yours helpful, interesting, or both.

Some do’s and don’ts of custom 404 error pages

  • Do make it clear that it’s an error page. No tricks, please.
  • Don’t blame the error on your visitors. They didn’t do anything wrong. And even if they did misspell something, pointing fingers doesn’t help the immediate situation. Have the decency to say you’re sorry.
  • Do provide a search form so the visitor can take action instead of just leaving in frustration. If your search form is already in the sidebar, be super-clear and say something like “Use the handy search form in the sidebar.”
  • Don’t be cryptic or jargony. Even “404″ is machine language, not human. Just explain in regular words how your visitor can search or browse your site.
  • Do provide a link to your archives or sitemap as an alternative to searching. Or, as Genesis does by default, include the archives right on the 404 page.

Have you said hello to your error page lately? What did it say to you?

Want a WordPress site?

Want to declare your independence with a brand-new shiny WordPress site? You can launch it to the world by the fourth of July!

My wondertwin Amy Crook and I are all booked up for the rest of May, but we have two slots available in June and two in July for our Bonanza package (which includes custom header art and a cartoon by Amy, in addition to smooth tech sailing courtesy of yours truly).

Want to see the Bonanza package in action? Check out Amy’s original watercolor art for Maribeth Doerr of StorkNetFamily.com (those are some cute baby birds!). I installed WordPress and Maribeth’s choice of theme, added Amy’s art and custom color scheme, and Maribeth now has the freedom to add and edit content as she pleases.

I also have two slots in June and three in July for Bonus packages (which includes theme customization but not original art).

And if you want a no-frills install so you can get going quickly, you can get that for $99 with the Basic package (four slots available in June and four in July).

Complete details on all the packages are available on the WordPress Packages page.

But what if your WordPress upgrade fails?

Here’s a quick way to fix one of the most common errors when upgrading WordPress — plus reassurance that it’s not your fault.

Let’s say you follow my advice to upgrade to the latest version of WordPress.

You log into your WordPress dashboard and click “Please update now” in the little message at the top of your screen. Then, on the next screen, since you’re all backed up (you are, aren’t you?), you click “update automatically.”

And then the unthinkable happens: Your website disappears.

All you see is a white screen, blank except for this bland, non-reassuring message:

Say what?!?

At this point you might follow the instructions and wait a minute, but probably not. A more likely scenario is that, in an adrenaline surge of anxiety, you hit the refresh button on your browser, even though you’re worried about messing up an upgrade in progress. You might even refresh a couple of times in a row. And at some point you get this even more frightening message in the middle of your still-ominously-blank screen:

And what’s worse, there is no “OK” button to click, nor is there a “cancel” button, nor is there a Panic Button.

So, naturally, you panic.

You try to load your website — any page on your website. And you get nowhere. Then you try to reload the login page, and your anxiety levels ramp up to DefCon 1 Red Alert Battle Stations when you realize that you can’t even login to the back end of your site.

At least that’s what happened to me the first time I saw this message after a “routine” WordPress upgrade.

How to fix the “Scheduled Maintenance” error

First of all, it’s not your fault. You didn’t break anything. It’s a weird little WordPress glitch that happens to me about one in every eight upgrades (and I do quite a bit of upgrading for my various sites plus my Peace of Mind Program clients).

Second of all, there is a way you can fix it. Yourself.

You’ll need to access your website files via FTP. If you are not familiar with this process, I suggest you log into your web hosting account and look in their help section for information about FTP. Your web host may have even emailed you FTP instructions when you first signed up for web hosting.

You’ll need a piece of software called an FTP client, which is different from a web browser. You can get a free FTP client called FileZilla here if you don’t have one installed on your computer.

To login to your website, you’ll need three pieces of information:

  1. A hostname. Sometimes this is ftp.your-domain.com, but sometimes it’s a server address at your web host. This is why you need to read your web host’s specific instructions.
  2. A username. Sometimes your web host assigns you one, sometimes you have to set this up yourself.
  3. A password. Even if your web host assigns your password, you can usually change it in your web hosting account. Please take care to use a solid, secure password here, because this is a direct doorway to all of your website files.

When you login to the FTP server for your website, you’ll be looking at a list of files. Look for a file named .maintenance, a file that was created today. Whether your files are sorted alphabetically or by creation date, it should appear near the top. You may have to change your FTP client’s preferences so that you can see files whose names begin with a dot (period).

On my FTP client (Fetch, which is Mac-only and not free — but when it’s transferring a file, the cursor changes into an animated running puppy, which feature all by itself is well worth the price of the software), it looks like this:

Found that file? Good. Now delete it.

Yep, just delete it.

Now go back to your web browser and try your site URL.

Don’t reload the page with the error message, the one that has a URL that looks like this:

http://your-domain.com/wp-admin/update-core.php?action=do-core-upgrade.

You’ll just get that ominous “are you sure you want to do this?” error message again.

Instead, just reload the front page of your site.

If your site reappears, you are good! You have solved the problem! Go ahead and login to your dashboard and breathe a sigh of relief.

And that’s how to fix the “scheduled maintenance” error that sometimes happens when upgrading WordPress. If you get a different error message, or a totally blank screen with no error message at all, this fix will most likely not work. But those situations are much more rare.

It’s World Backup Day! Are YOU backed up?

I just found out (via a tweet from @Ipstenu) that it’s World Backup Day!

(That page has some coupon codes for backup services, plus apparently there are some Twitter contests to win free backup packages. Smart marketing!)

If your computer isn’t backed up, consider this a friendly public service announcement reminding you that you might want to take care of that soon-ish.

And don’t forget to back up your website(s) as well — in the case of WordPress, you need to back up both your database and your actual website files in order to have a complete copy. There are several plugins that will do the job (I use a combo of WB-DB Backup for my database and WordPress Backup for my files, and there are plugins that will do both parts, but I haven’t tested them yet).

I’ll also remind you that there are a limited number of slots still available in my WordPress Peace of Mind Program, which is open for new signups until April 4. If you join this program, I will do a complete backup of your site (and schedule regular ongoing backups) as well as upgrade WordPress, your plugins and themes.

And I had no idea World Backup Day was going to happen during the enrollment period!