Forum Replies Created
-
wpsolrKeymaster6 years, 1 month ago in reply to: Can't Connect to SearchStax #21974
Recent versions of SolrCloud require that the user you use to create the index has also the rights to upload the configuration files.
Source: https://lucene.apache.org/solr/guide/8_4/configsets-api.html#configsets-upload
A configset is uploaded in a “trusted” mode if authentication is enabled and the upload operation is performed as an authenticated request
This can be done only in SearchStax.
wpsolrKeymaster6 years, 1 month ago in reply to: Can't Connect to SearchStax #21972Collection /solr/test exists. use another collection name /solr/test1
wpsolrKeymaster6 years, 1 month ago in reply to: Can't Connect to SearchStax #21969With engine “SolrCloud” or “Solr”?
wpsolrKeymaster6 years, 1 month ago in reply to: Can't Connect to SearchStax #21967You can try:
Serach engine: SolrCloud
WPSOLR index name: Test
Server Protocol: https
Server Host: xxxxxxxxx-xxxxxxxx-us-east-2-aws.searchstax.com
Server Port: 443
Solr index path: /solr/testwpsolrKeymaster6 years, 1 month ago in reply to: WP-CLI support #21944There is a “Cron” extension already available to call for index operations remotely: /guide/configuration-step-by-step-schematic/activate-extensions/cron-scheduling/
Roadmap: /forums/topic/wp-cli-support/
wpsolrKeymaster6 years, 1 month ago in reply to: Gets "stuck" indexing orders #21904With WooCommerce 4.4.1, I do not see “_order_items” in tab 2.2. Do you know where this custom field comes from?
wpsolrKeymaster6 years, 1 month ago in reply to: Gets "stuck" indexing orders #21900Had one more error, due to a long field, the order items field where they had a VERY LARGE order, over 32766 chars in that field. So I changed that type to the text that is too large to fit in other types and it seems to be indexing past that point now as well.
Your new error could be related to your previous change. Can you try with the order items field disabled in tab 2.2?
wpsolrKeymaster6 years, 1 month ago in reply to: Gets "stuck" indexing orders #21886Well done.
I agree on the not “plug & play”. It’s on purpose, as we want to keep as many options from the search engine as possible. This is the difference with a pure hosted solution, where most of the settings are hidden.
Just for my sake, how much long was your admin order search without WPSOLR?
wpsolrKeymaster6 years, 1 month ago in reply to: Error when indexing articles #21884This flag is raised by Elasticsearch when disk space is getting close to 100%: https://www.elastic.co/guide/en/elasticsearch/reference/7.9/modules-cluster.html#cluster-routing-flood-stage
But I noticed the index can be in read-only mode even if the disk has plenty of free space. Resetting the index.blocks.read_only_allow_delete flag is then a workaround.wpsolrKeymaster6 years, 1 month ago in reply to: Gets "stuck" indexing orders #21882Well done.
I’m impressed, never heard of 30O thousand orders until now. The orders search being able to look in customer’s details, like address fields, it should fly and be much more relevant now.
wpsolrKeymaster6 years, 1 month ago in reply to: Error when indexing products #21874Often, errors come from a forbidden unicode characters from imports.
wpsolrKeymaster6 years, 1 month ago in reply to: License activation stuck #21873I remove the older activation.
wpsolrKeymaster6 years, 1 month ago in reply to: Gets "stuck" indexing orders #21871Please check if you can find some clues in /forums/topic/error-when-indexing-products/
wpsolrKeymaster6 years, 1 month ago in reply to: Error when indexing products #21870To find the products with the error, you need to index with:
– Batch size “1”
– Debug mode “on”The indexing will fail once. Stop and restart with the same settings, and you will see the ID of the product.
From there, you can edit the product, and try to fix the problem, or simply check its metabox “Do no search” to prevent its indexing.
wpsolrKeymaster6 years, 1 month ago in reply to: Indexing similar category paths moves products to other categories #21636