Join GitHub today
Permit defining abspath before WP-CLI is loaded #69
If ABSPATH is defined before wp-cli loads it will throw a notice.
Now if you run any wp-cli it will throw a notice that ABSPATH is already defined.
When would you want this?
WordPress tries to define the ABSPATH it uses
The file structure of this with my example to help visualize this.
referenced this issue
Nov 28, 2017
This kind of setup can be achieved through the web interface. If you check wp-load.php:20 This check is the first thing in the file.
So when for example I go to the wp-login the first thing it does is include wp-load.php. Which tries to define the
But where is this alternative
I have this setup running for a week in test mode and in the web interface I haven't encountered problems.
Are there specific things that come to mind that worry you with this setup?
Maybe add an extra debug message when
Maybe WordPress does support
More so: unintended consequences. If we permit this and it causes problems X, Y and Z down then line, then I'd rather not let this happen in the first place.
But, given WordPress supports it, I'm open to it. Want to submit a pull request with functional tests?