Comments on: Custom WordPress database error pages

By: DanGayle (Daniel Gayle)

DanGayle (Daniel Gayle) — Mon, 21 Dec 2009 20:55:02 +0000

@yoast The code in http://yoast.com/custom-wordpress-database-error-pages/ is unescaping your escaped characters. Can you fix it?

By: Adding a custom error page when the database has issues. - Frumph’s Random Blog

Sat, 20 Jun 2009 21:39:05 +0000

[...] One is: http://yoast.com/custom-wordpress-database-error-pages/ [...]

By: phillprice (Phill Price)

phillprice (Phill Price) — Mon, 06 Apr 2009 13:03:08 +0000

@Cranialstrain I have found a lovely article by @jdevalk which shows how to make a prettier error page ... http://tinyurl.com/7rwh5o

By: Akshay

Akshay — Thu, 21 Aug 2008 12:00:27 +0000

sir, i have made a blog recently http://charismatic-verma.blogspot.com/. What should i do to make it adsense frindly and to increase it's pr, suggestions needed.

By: CantStopTheSignal

CantStopTheSignal — Tue, 03 Jun 2008 14:41:41 +0000

Why can't cached pages be shown in lieu of error pages, if they exist? There's a perfectly good copy of the page in cache, why show an error page?

The wp-cache engine would just need to include a comment tag in the html source that a database error occured and the page is from cache. If the cache is expired, then show it anyway, but also output the 500 header. Otherwise 200 header if the page isn't otherwise expired.

Only if there is no cached page for the request would I want to have an error page to appear when the database is not accessible.

This feature would wildly make WP capable of high-availability in high traffic situations.

By: Pashalex

Pashalex — Thu, 10 Apr 2008 00:34:14 +0000

I am trying to install a new theme in word press 2.o but any theme i chose it comes up with an error "Broken Theme" and "style.css is unreadable".
Any comments much appreciated.

By: [BLT]FQX

[BLT]FQX — Sun, 06 Apr 2008 08:32:34 +0000

So what is the test result, Joost?
Since your time stamp says it's Mar 12, but I received the pingback on Apr 6.

By: WLTC » Custom WordPress database error pages

WLTC » Custom WordPress database error pages — Thu, 27 Mar 2008 22:37:09 +0000

[...] Custom WordPress database error pages: This is an interesting article on how to setup WordPress to display custom database error pages and even send out an email to the owner of the blog in case of database failure. This means that should your database fail, and someone would open your front page at example.com, he would be served that error page with a 200 OK header. If that someone were a search engine, that’s what it would index… If the search engine encounters a 500 error, it will not index that page and just wait for your server to be fixed again. That means not making sure it sends a 500 header is a huge risk. « I am really loving Safari for Windows [...]

By: Joost de Valk

Joost de Valk — Wed, 12 Mar 2008 18:09:56 +0000

will test that tonight Marcus, thx!

By: Markus

Markus — Tue, 11 Mar 2008 12:08:06 +0000

Hello Joost

I just tried out this tip, and it is good when calling the error page directly. The web developer in Firefox showed me the 500 header.

Now I changed the wp-config.php for a few seconds to raise a real db error, but then the error page comes with 200 OK.

By: Create a Custom Database Connection Error Page |

Create a Custom Database Connection Error Page | — Tue, 11 Mar 2008 03:31:17 +0000

[...] Karma must be at work, because tonight I was checking my email and received the latest post from Joost de Valk’s SEO BLOG and the subject was exactly [...]

By: WPModder

WPModder — Tue, 11 Mar 2008 03:14:47 +0000

Great tip Joost, thank you so much for sharing!

By: Datenbank-Fehler und die Header » Beitrags-Archiv » Cowboy of Bottrop

Datenbank-Fehler und die Header » Beitrags-Archiv » Cowboy of Bottrop — Mon, 10 Mar 2008 22:23:12 +0000

[...] dem ich heute ein Pingback aus den Niederlanden erhielt. Joost de Valk greift das Thema in seinem SEO-Blog auf und meint, da stimmt was [...]

By: Joost de Valk

Joost de Valk — Mon, 10 Mar 2008 19:44:58 +0000

hmm depends on your apache config then I guess, I run 30odd websites on that server and it works correctly with this code on all of them...

By: Mark van Eijk

Mark van Eijk — Mon, 10 Mar 2008 17:31:19 +0000

HTTP_HOST takes the name of the host you request. So in this case this would be joostdevalk.nl. When you use SERVER_NAME it takes the name of the server your webhost uses as their hostname for the webserver.

By: Joost de Valk

Joost de Valk — Mon, 10 Mar 2008 16:32:27 +0000

Hmm Mark, I tested that, and for me it contained my server name just right this way...

By: link dump, march 10th â€˜08 : maxyRO’s blog

link dump, march 10th â€˜08 : maxyRO’s blog — Mon, 10 Mar 2008 15:52:50 +0000

[...] WordPress 2.3.2 (we’re on 2.3.3 at the moment) introduced a nice new feature many of us will find useful: : the possibility to create a custom database error page. Here’s an easy tutorial on how to create yours - link [...]

By: Mark van Eijk

Mark van Eijk — Mon, 10 Mar 2008 13:38:15 +0000

I would like to comment that you should use $_SERVER['HTTP_HOST'] instead of $_SERVER['SERVER_NAME']. Because your version takes the actual servername (this could be s001.yourhost.nl) and you're domainname is actually inside HTTP_HOST. So this will make your e-mail much more clearer when you've got more than one website.

By: Markus

Markus — Mon, 10 Mar 2008 09:34:29 +0000

Hello Joost

I think, the db_error.php is for the user who visit my blog. They don't see the header status code except with special tools.

But you're right to send a 500. I didn't notice that until now, but the robots will read the header, and I don't want to find my db_error in the google search results.

So thanks for the tip, I will use it.

The idea sending a mail has grown up in me too, but I leave it. On my shared hosting web space I'm not able to do anything, when an db error occurs.

Best regeards from Germany,
Markus