You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I looked everywhere and didn't see any mention about the index command no longer supporting the global WP-CLI command --url so reaching out here to see what's up? This may not be a bug but it was unexpected for me.
I'm working on upgrading to v4 of ElasticPress on a couple of large multisite networks. Historically I could control the indexing to a single site when needed, but after upgrading to versions 4.0.0+ the CLI command wants to index the full network no matter what.
While normally I want a full network index, I have found in one particular network there is a large sum of content to index across 60+ sites. When running the full index it eventually errors out once it reaches the end of the index with Error: Network alias creation failed for posts ..., and I was trying to debug further by syncing a single site but found the index command doesn't seem to honor the --url parameter anymore after 4.0.0. This still works fine in 3.6.6 though?
Steps to Reproduce
In your command prompt, run the index CLI command for a single site in your subdirectory multisite install wp elasticpress index --setup --yes --url=https://test-multisite.test/some-sub-site
Observe that the indexing logs report starting from site ID 1 and continue through all the sites in the network.
Expected behavior
I expect the index command to ONLY focus on indexing the site provided in the --url parameter offered by WP-CLI which was supported in ElasticPress 3.6.6.
Screenshots NOTE: The doc in my command is an alias for 10updocker
Environment information
Device: All devices tested on (locally and on hosting)
OS:
Browser and version:
WordPress version: 5.9.3
ElasticPress version: 4.0.0+
Elasticsearch version: Unsure on version
Where do you host your Elasticsearch server? elasticpress.io
What ElasticPress features do you have currently active?
Plugins and version:
Theme and version:
Site Health Info:
Additional context
The text was updated successfully, but these errors were encountered:
I looked everywhere and didn't see any mention about the
index
command no longer supporting the global WP-CLI command--url
so reaching out here to see what's up? This may not be a bug but it was unexpected for me.I'm working on upgrading to v4 of ElasticPress on a couple of large multisite networks. Historically I could control the indexing to a single site when needed, but after upgrading to versions 4.0.0+ the CLI command wants to index the full network no matter what.
While normally I want a full network index, I have found in one particular network there is a large sum of content to index across 60+ sites. When running the full index it eventually errors out once it reaches the end of the index with
Error: Network alias creation failed for posts ...
, and I was trying to debug further by syncing a single site but found theindex
command doesn't seem to honor the--url
parameter anymore after 4.0.0. This still works fine in 3.6.6 though?Steps to Reproduce
wp elasticpress index --setup --yes --url=https://test-multisite.test/some-sub-site
Expected behavior
I expect the index command to ONLY focus on indexing the site provided in the
--url
parameter offered by WP-CLI which was supported in ElasticPress 3.6.6.Screenshots
NOTE: The
doc
in my command is an alias for 10updockerEnvironment information
Site Health Info:
Additional context
The text was updated successfully, but these errors were encountered: