wpstarter

Fix HTTPS when a load balancer is in use.

First commit – First version

First attempt for a README

Hotfix

Fixed

Nothing

Added

Nothing

Changed

• Changed bootstrap line in index.php template to be similar to what WP core uses. This avoid issues with scripts parsing index.php with regular expression. Props @schlessera, see #35

Fixed

Nothing

Added

Nothing

Changed

• wp-content-related constants are defined only when actually different from default, otherwise network installation screen will complain for no reason
• Documentation improvement and fixes, thanks to @schlessera

Added

• Make WPSTARTER_PATH available in wp-config.php (see #30)

Changed

Nothing

Fixed

Nothing

• Add Setup::runAsRoot script to post-update-cmd to ensure installation script on update when WP Starter is used as root package
• Update "Quick Start" example to include Setup::run script to post-update-cmd

Fixed

Require wpackagist with https. (Only relevant when used as root package.)

Removed WP_LANG and FORCE_SSL_LOGIN props @GaryJones

• Fix MuLoader throws notice (see #18) - Thanks @schlessera
• Remove duplicate settings form .env.example template - Thanks @GaryJones

Salt keys are not forced to be unique per environment by default.

This has proven to be an issue is some cases, even if issue was not consistently reproducible.

As always salts can be set via environment vars.

• Updated Dotenv version
• Add possibility to use custom name .env file
• General improvements to environment variables handling

Better folder handling: now all paths are internally managed as relative to root. Nothing change for API.

Fixed a bug in Config class

• Massive refactoring: code is now more modular and the entire workflow is organized into "steps".
• Content folder is not moved anymore, but an additional theme folder is registered. As per discussion in #2
• Configurations disscuded in #3 is now available.
• Documenation added in gh-pages branch, see http://wecodemore.github.io/wpstarter/

Fixed issue with MuLoader on installing.