New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide an easier way to specify target site (--url
)
#5256
Comments
If a scheme isn't specified, then I think WP would just default to the value of |
@iandunn Im' not necessarily a fan of letting WP-CLI guess something and then immediately act on that. |
Ah, that's even better! |
Hi! Any progress on this? Or at least having a hook there to extend/customise behaviour here would be extremely helpful. |
Related: wp-cli/extension-command#21 (comment)
For this use case, we could maybe write a cache file w/ a list of URLs in the network. That way we wouldn't have to load WP each time. |
I think this should live in an installable package. This could make for a good contributor day project. |
My use case / problem
I frequently run commands on a Multisite instance with a large number of sites, most of which have long domains. Typing in the full URL to specify the target site feels unnecessarily tedious and slow.
e.g.,
wp shell --url=https://2019.saintpetersburg.wordcamp.org
The solution I'd like
It'd be much faster and more convenient if
--url
accepted a substring, and performed a search if the string isn't an exact match for a domain.e.g.,
wp shell --url=2019.saintp
To avoid any confusion, the command could output the full URL of the selected site when a substring is used:
That could be disabled when
--quiet
is set, though.If multiple results are found for the given substring, then the safest thing to do might be to throw an error, and ask the user to provide a unique substring.
In mutli-network installs, it should probably just search all networks, since everything is stored in
wp_blogs
anyway.wp_blogs
has adomain
index comprised ofwp_blogs.domain
andwp_blogs.path
, so searching should be performant even in very large sites. If that doesn't turn out to be true, though, then the search could simply be disabled whenwp_is_large_network()
, and the user would have to specify an exact URL. That would only impact a relatively small number of WP-CLI users, though.The text was updated successfully, but these errors were encountered: