Closed castilma closed 2 years ago
I'm a newbie. If I had to guess, it looks to me like wp search-replace is called with a wrong --path argument. The value should maybe not be literally "WP_CLI_CONFIG_PATH", but the actual path on the local machine?
I don't know - as it stands - how WP_CLI_CONFIG_PATH
could have been appeared there, but my guess is that the cause should be your local path:
wordpress_path: "/Users/me/Local Sites/***/app/public/"
since it contains spaces you should escape them
wordpress_path: "/Users/me/Local\ Sites/***/app/public/"
or, even better, rename your folder with a more geek-friendly name like LocalSites
:)
Found the problem. I work with someone else on this wp installation and my partner added a wp-cli.yml file with the following content: path: WP_CLI_CONFIG_PATH
He was trying something out, but forgot to remove it afterwards.
since it contains spaces you should escape them
wordpress_path: "/Users/me/Local\ Sites/***/app/public/"
I think wordmove is doing something wrong here:
I believe wordpress_path: "/Users/me/Local Sites/***/app/public/"
is valid .yml syntax.
So I passed the path /Users/me/Local Sites/***/app/public/
correctly to wordmove. It is now up to wordmove to correctly pass that path to other programs/components itself might use!
From a theoretical point of view, I'm totally with you.
Always hoped various things:
I've updated wiki's doc warning about this misbehaviour. I'm sure this is better than nothing 👍
Thanks for your comprehension.
Describe the bug
I want to pull a remote db to a local wp installation.
Wordmove command
Expected behavior
I expect the command to exit with no error.
movefile.yml
Exception/trace
Environment (please complete the following information):
Doctor
wordmove doctor
command returns all green(I believe those errors are unrelated.)