Ugly bland error message upon missing wp-config file ... and a fix!

[chuyskywalker]

I was going through the 2.0 beta1 to give it a run and after SNV CO'ing the files I just hit the website and got this ugly, no frills, plain, and scary error message about some missing files and some such.

So, doing my part, here's a patch that snatches the same layout as the database error screen and uses it to pretty up this error. Additionally, I added some basic write checks to see if a user can even use the setup-config.php before offering them the false hope that it'd work.

Finally, I've updated the "more help" link to point to the much more complete and helpful codex wp-config reference.

[chuyskywalker]

patch to make the ugly error not so ugly, and much more helpful

[Nazgul]

Updated the patch to make use of wp_die.

[Nazgul]

2.0.5. Candidate

[markjaquith]

wp_die() is 2.1 only.

[markjaquith]

(In [4307]) missing wp-config.php error uses wp_die() now. props Nazgul. fixes #1936

[Viper007Bond]

Needs some more work.

[Viper007Bond]

Bah, forgot to check the "overwrite" box.

[Viper007Bond]

Why is changing the help link to the Codex something that should wait for 2.2?

[foolswisdom]

Replying to Viper007Bond:

Why is changing the help link to the Codex something that should wait for 2.2?

Because this ticket has become epic? ;-) But lets try again. Setting milestone to 2.1 . Please apply missing_wp-config.2.patch

epic: started out with a detailed problem and creative and complete solution by chuyskywalker, later Nazgul lay down a tight fix... time passed... Viper reopened for the missing important pieces, but the tale was probably forgotten. I often do the same thing, but I do try to remember that we have lots of ticket numbers available.

[ryan]

(In [4737]) Change editing wp-config codex link. fixes #1936