[wp-trac] [WordPress Trac] #9166: Missing propper check transparently for needed config constants

WordPress Trac wp-trac at lists.automattic.com
Wed Feb 18 19:06:22 GMT 2009

#9166: Missing propper check transparently for needed config constants
 Reporter:  hakre            |       Owner:  anonymous    
     Type:  feature request  |      Status:  new          
 Priority:  normal           |   Milestone:  2.7.2        
Component:  Administration   |     Version:  2.7          
 Severity:  normal           |    Keywords:  configuration
 Beside the fact, that you can come more or less often to the point to
 start a flame-war because WordPress is designed to have the static
 configuration settings in a PHP File, some things can be done to improve
 the installation-easyness and provide better hints to this error-prone way
 of setting something up.

 For Example: WordPress does not verify that really needed config PHP-
 Constants _are_ defined. Let's assume a user does not understand the
 configuration and enters the following in wp-config.php

 define('90a83383_dbYZ', 'putyourdbnamehere'); // Der Name der Datenbank,
 die du benutzt.
 define('90a83383_unZUF1', 'usernamehere'); // Dein MySQL-Datenbank-
 define('xxx', 'yourpasswordhere'); // Dein MySQL-Passwort.

 then the wordpress error message that the connection to the db server
 failed does not reflect the fact, that the constants DB_NAME, DB_USER or
 DB_PASSWORD are not defined. Putting out this message clearly, that wp-
 config.php is not properly configured and the database configuration
 should be checked would help much instead.

Ticket URL: <https://core.trac.wordpress.org/ticket/9166>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list