Add inline documentation to clarify the reasoning behind the various conditions that control how WP is loaded.

Props mattheweppelsheimer for the initial patch.
Fixes #30935.


git-svn-id: https://develop.svn.wordpress.org/trunk@31463 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
Drew Jaynes 2015-02-14 11:38:41 +00:00
parent 9b463c5a45
commit c77e726eef
1 changed files with 8 additions and 0 deletions

View File

@ -23,6 +23,14 @@ define( 'ABSPATH', dirname(__FILE__) . '/' );
error_reporting( E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_ERROR | E_WARNING | E_PARSE | E_USER_ERROR | E_USER_WARNING | E_RECOVERABLE_ERROR );
/*
* If wp-config.php exists in the WordPress root, or if it exists in the root and wp-settings.php
* doesn't, load wp-config.php. The secondary check for wp-settings.php has the added benefit
* of avoiding cases where the current directory is a nested installation, e.g. / is WordPress(a)
* and /blog/ is WordPress(b).
*
* If neither set of conditions is true, initiate loading the setup process.
*/
if ( file_exists( ABSPATH . 'wp-config.php') ) {
/** The config file resides in ABSPATH */