[wp-hackers] wp-config.php defining value of ABSPATH

[Nikola Nikolov]

It's actually defined in wp-load.php and the correct way of including just
WordPress(without parsing the request and displaying the correct template)
is actually by including wp-load.php and not wp-config.php.

Basically wp-load.php looks in two locations for wp-config.php:

ABSPATH . 'wp-config.php'

and

dirname( ABSPATH ) . '/wp-config.php'

In the second case, wp-load.php also makes sure that in the directory where
the wp-config.php resides there is no wp-settings.php, because if there is,
that means that this wp-config file is actually part of a different
install.


On Sun, Feb 9, 2014 at 3:58 PM, Utkarsh Dixit <utkarsh.dixit11 at gmail.com>wrote:

> Hi,
>
> I'm just a beginner to wordpress so it might sound a little naive, in
> wp-config.php file we have following lines of code just before including
> 'wp-settings.php'
>
> if ( !defined('ABSPATH') )
> define('ABSPATH', dirname(__FILE__) . '/');
>
>
> Seems useless to me as we already define ABSPATH in wp-blog-header.php and
> suppose if we directly open our wp-config.php file then also if it is a
> level above the wordpress root directory the ABSPATH is set to the
> directory a level above the wordpress root directory which gives a fatal
> error when we include the wp-settings.php file in the next step.Can't we do
> it like this?
>
> if ( !defined('ABSPATH') )
> define('ABSPATH', dirname(__FILE__) . '/');
>
> if(file_exists(ABSPATH . 'wp-settings.php'))
>          require_once(ABSPATH . 'wp-settings.php');
>
>
> It helps in removing the Fatal error which might occur.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>