Make WP_SITEURL smart by detecting if $WORDPRESS_DIR is set #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Happy to see that the buildpack supports subdirectory (mchung/heroku-buildpack-wordpress/issues/23).
This patch instructs Wordpress to detect WORDPRESS_DIR and then dynamically sets WP_SITEURL. Currently, this isn't done, so when a developer sets WORDPRESS_DIR via
heroku config:set
, the site breaks since WP is still serving content out of the previously configured directory. And since the site breaks, the user can't login to update that variable.The buildpack README also specifies that WP_CONTENT_DIR and WP_CONTENT_URL must be set, however I didn't observe any problems without them set. Is that doc out of date? Or was I just lucky?
cc: @okko