[wp-hackers] Is WP_INSTALLING constant here to stay?
dyordan1 at ramapo.edu
Tue Jan 22 14:07:43 UTC 2013
I'm pretty sure that the solution you came up with (assuming it works now) will be pretty stable for the "foreseeable future". However, I'll be the first one to say, you're probably doing it wrong if you need to run just core. Or, for that matter, one of the other plugins installed is doing it wrong. Wordpress plugins (and themes) are meant to work together in unison, not shut down each other. I'd first try to disable (through /wp-admin/) some of the plugins that you suspect might be breaking your code and if it's just one - you've got your culprit, take it from there. If it's more than one, chances are your code is acting weird. Download some plugins that have functionality similar to the one you're aiming for and see how they coded it in, maybe you're missing something? No harsh feelings, just trying to go for the cleanest approach, right? Cheers!
On Tue, 22 Jan 2013, at 8:17 AM, Dino Termini wrote:
> Good morning, all,
> for a plugin I'm working on, I need to user some WordPress functions in an external file. I'm loading it with the usual wp-load.php include, but apparently some plugins don't like that, and throw a fatal error, breaking my code. Thanks to St. Google, I found out that there's a constant that can be used to tell Wordpress to not load any plugins:
> define('WP_INSTALLING', true);
> Now my question to core developers is if this approach is correct and if I can rely on it for the foreseeable future. Otherwise, my question becomes: what is the best way to load just the CORE without all the stuff added by plugins and themes?
> Thank you,
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers