Extended customized errors

[coolmann]

One feature I appreciated in 2.3.2 is the chance to have customized db errors, using the wp-content/db-error.php page. I'd like to point your attention on two issues:

• Why don't you move the db-error.php page inside the theme folder? So that theme developers can also distribute it inside one single folder
• What about customizing the wp_die function declared in functions.php? Currently I'm using an hacked version, in which I added this row

Included a custom error page, much better than the standard one!
And of course commented the one below
include($_SERVERDOCUMENT_ROOT.'wp-content/themes/duechiacchiere/wp-die.php');

at row 1260, and removed the static HTML code included below that line. I know this is not the "best" way to do it, but maybe it's a beginning!

Have a happy new Year!
camu.

[filosofo]

Replying to coolmann:

Why don't you move the db-error.php page inside the theme folder? So that theme developers can also distribute it inside one single folder

The problem is that when the database is down, there's no way to know which is the live theme, because that's something that's stored in the db.

[coolmann]

I see, even if this information could be written in the wp-config.php

[DD32]

I guess it could be possible to allow a page within wp-content that can be loaded for errors.

ie.

if( error == db-down && file_exists( ABSPATH . WPCON . '/db-down.php') ){
   include(ABSPATH . WPCON . '/db-down.php');
} else if ( error == fatal && file_exists( ABSPATH . WPCON . '/wp-die.php') ){
   include( ABSPATH . WPCON . '/wp-die.php' );
} else {
   //normal wp-die stuff
}

[ffemtcj]

No Patch. Moved to 2.7

[Denis-de-Bernardy]

db errors are no longer shown.