Conversation
The URL replace task runs wp option update, which comes from wp-cli/entity-command. On a composer install of the plugin the option command isn't registered, so both option updates error mid-sync (the search-replace calls are fine, as search-replace-command is already required). A global WP-CLI bundle install never hits this, which is probably why it went unnoticed.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The URL replace task runs
wp option update, butoptioncomes fromwp-cli/entity-command, which isn't in the composer requires so on a composer-managed install both option updates error with'option' is not a registered wp commandmid-sync. The search-replace part is fine since search-replace-command is already required. Doesn't show up when WP-CLI is installed globally, as the bundle includes everything.