Adapting local WordPress setup outside the project directory #513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'll get on this one soon. I swear! 😃 |
alessandro-fazzi
approved these changes
Nov 16, 2019
This was referenced Apr 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm going to use Wordmove to manage multiple sites, and have noticed that currently it rasies the error below if the local WordPress setup is outside the project directory:
This PR is intended to solve this by always setting
--pathoption towp search-replace.The path given to the options is retrieved by
local_options[:wordpress_path]. Since it is where the local WordPress setup is located, I think setting it through--pathdoes not harm any usage. Please correct me if not.Related issue: #407