[wp-hackers] wp-config.php, wp-load.php, and ABSPATH
wp-hackers at striderweb.com
Fri Sep 11 01:51:06 UTC 2009
On Sep 10, 2009, at 9:25 AM, Otto wrote:
> So, you're asking if we should instantly and intentionally break every
> plugin that includes wp-config.php?
> Yeah, I'm fine with it. ;)
Heh. Okay, to rephrase the question (via quoting myself):
> Here is my proposal: We should assert, in documentation and in code,
> that any time a plugin or process wants to access parts of WP
> (including the database), it should call wp-load.php.
> [W]e should put a "deprecated" call with the define() in wp-config
> (inside the "if it doesn't already exist" clause), so that if it
> does happen, there is a notice to the log that "You should not call
> wp-config.php directly. Call wp-load.php instead." Then somewhere
> down the road we can get rid of the troublesome define.
More information about the wp-hackers