Sometimes when a WordPress blog gets put up on digg.com or slashdot – the MySQL server that is storing the data gets overloaded and then WordPress can’t establish a database connection. Many servers don’t have this problem – but the few that do bring up the wordpress “Error establishing a database connection” message.
The problem with the screen as it exists now is that it has a WordPress logo very big on it – is called “WordPress > Error” – both things make it seem like it’s WordPress’s fault that there is an error. This is obviously not the case – since it’s MySQL’s fault.
I think the page title should be “MySQL Error” and the WordPress logo should be made much smaller on the error page… Perhaps a MySQL logo could be put on that page to make the visitor realize it’s not WordPress – but MySQL that’s at fault.
The reason I say this is because in the comments on articles once this happens many people will say stuff such as “Man, WordPress really sucks – it can’t handle traffic…” – so you can see that the error message is doing a lot to damage the reputation of WordPress…
Sounds like a reasonable change to me. Why don’t you work up those modifications and submit them to trac?
Of course, those of us who have lived through the ‘slashdot-effect’ use WP-Cache, and don’t generally suffer the MySQL overload issues.
And, even before I set up caching (I actually use my own tailored version of Staticize), I created my own MySQL error output…
But yeah, feel free to open up a trac ticket that there should be a theme file for when there’s a db access problem — that’d be the best way to handle it (like theme’d 404s…).
yes, this would be a nice thing to have for folks who don’t know how to do their own mysql error outputs. I get this error sometimes too when my server is using lots of CPU and it would be good to have a blank screen or something changeable.
- The topic ‘Suggestion: Change the database connect screen’ is closed to new replies.