Whippet Server launches a stand-alone web server for a specific WordPress installation. It makes WordPress easier to develop with, for example, by adding lots of debug information to the terminal without cluttering up or breaking your templates.
ISC License
80
stars
6
forks
source link
Don't mess up wp-config.php when running from wp-content #62
This is just a quick fix for when whippet-server is ran from within wp-content (when there is a wordpress core in parent directory), the wp-config.php gets injected with the code as if it's using the generated whippet-wp-config.php file.
I think it was my last pull request that introduced this, which looking back at it now has made the code a little unmanageable.
I'm going to try sort it out so that there are only 2 possible states:
We are in a wp-content directory with no wordpress core in parent directory
We are in a Wordpress root
Also, I'll make an attempt at being able to run whippet-server from anywhere within the wordpress directory (And changing the working directory to match the relevant state as above).
This is just a quick fix for when whippet-server is ran from within wp-content (when there is a wordpress core in parent directory), the wp-config.php gets injected with the code as if it's using the generated whippet-wp-config.php file.
I think it was my last pull request that introduced this, which looking back at it now has made the code a little unmanageable.
I'm going to try sort it out so that there are only 2 possible states:
Also, I'll make an attempt at being able to run whippet-server from anywhere within the wordpress directory (And changing the working directory to match the relevant state as above).