[wpsolr]

4 years, 4 months ago in reply to: AWS OpenSearch error – Authorization header requires ‘Credential’ parameter #29744

We tested WPSOLR with a local OpenSearch until now. Never tested with AWS. Sorry for that.
I’ll add the compatibility with AWS OpenSearch in next release.

[wpsolr]

4 years, 4 months ago in reply to: Can this plugin replace the default query? #29741

WPSOLR will replace the default query for archives, like search, taxonomy, author, ….

In your case, it will replace the 1 million products WooCommerce shop page, product search page, and product category page queries.

After a query is called on Solr, Elasticsearch, Algolia, or OpensSearch, WPSOLR sends results back to your theme’s standard WP loop to let it display the results as usual.

Other queries, like all queries called to build the product detail page, are not replaced.

[wpsolr]

4 years, 4 months ago in reply to: keywords in text followd by a colon not found with SOLR #29739

As a fix, you could remove “:” at indexing time, by adding a charfilter on type “text_lws” in your Solr schema.xml file as described at https://solr.apache.org/guide/solr/latest/indexing-guide/charfilterfactories.html

<field name="title" type="text_lws" indexed="true" stored="true"/>

<fieldType name="text_lws" class="solr.TextField" positionIncrementGap="100">
    <analyzer>
       <tokenizer class="solr.WhitespaceTokenizerFactory"/>
       <filter class="solr.LowerCaseFilterFactory"/>
       YOUR FILTER HERE
       </analyzer>
</fieldType>

[wpsolr]

4 years, 4 months ago in reply to: keywords in text followd by a colon not found with SOLR #29738

Can you activate the Query Monitor extension, so you can check the WPSOLR’s Solr query?

[wpsolr]

4 years, 4 months ago in reply to: Search keyword not working properly #29737

This is an error triggered by the previous code commented, as $res_final is no more defined.

Please add the following initialisation, after your commented line 878:

// throw $e; <== THIS LINE COMMENTED !!!!
$res_final = 0;

[wpsolr]

4 years, 4 months ago in reply to: Search keyword not working properly #29734

As you checked “Debug infos during indexing”, you can see the errors, but this should not prevent the indexing to continue till the end (after the small code customisation described above).

Can you try again without the “Debug infos during indexing” ?

[wpsolr]

4 years, 4 months ago in reply to: Can’t Deactivate/Reactivate License #29733

Done.

[wpsolr]

4 years, 4 months ago in reply to: Search keyword not working properly #29728

By commenting the code above, you should be able to continue indexing while getting errors.

What happens exactly?

[wpsolr]

4 years, 4 months ago in reply to: Search keyword not working properly #29725

You can try commenting out line 878 of file wpsolr-pro/wpsolr/core/classes/engines/class-wpsolr-abstractindexclient.php:

try {

	$res_final = $this->send_posts_or_attachments_to_solr_index( $documents );

} catch ( \Exception $e ) {

	if ( $is_debug_indexing ) {
		// Echo debug text now, else it will be hidden by the exception
		echo $debug_text;
	}

	// Continue
	// throw $e; <== THIS LINE COMMENTED !!!!
}

• This reply was modified 4 years, 4 months ago by wpsolr.

[wpsolr]

4 years, 4 months ago in reply to: Search keyword not working properly #29723

You can try with Elasticsearch, or Algolia. they could be less prone to this error than Solr.
Or try to fix your posts. For instance, if you import your posts from a file, the file could be corrupted with bad characters during the export.

[wpsolr]

4 years, 4 months ago in reply to: How to go back to “This is a test environment only.” on test system #29717

I cannot reproduce your issue unfortunately. You should see a link ‘Click here to manage your license’ with WPSOLR 22.2
You can keep going with 22.1 on your current test environment

[wpsolr]

4 years, 4 months ago in reply to: Allow to exclude certain facet value from taxonomy/attributes/categories filters #29714

On WPSOLR 22.2, click on you filter’s button “Override each item label” to open the section containing the “Hide” option.
The “hide” is available on checkbox or listbox layouts.

[wpsolr]

4 years, 4 months ago in reply to: An error prevented the search engine query to be executed. #29710

This is a failsafe mechanism: when the WSPOLR query fails for any reason, it reverts to the WordPress search.

Please check your debug.log for the error description, or use our Query monitor extension

[wpsolr]

4 years, 5 months ago in reply to: empty category pages #29707

Please check in Kibana that you have product_cat values.

Can you execute in Kibana the Elasticsearch query, and try to find the problem by eliminating bits of subqueries, one at a time.
I suggest starting with product_cat term queries:

{
  "bool": {
    "must": {
      "term": {
        "product_cat_str": "Ανταλλακτικά"
      }
    }
  }
}

[wpsolr]

4 years, 5 months ago in reply to: How to go back to “This is a test environment only.” on test system #29705

It is possible that test*.domain was accepted in the past, indeed.
By copying your production site, you also installed a new, more restrictive, version of the plugin.

I understand your current situation, so I added a free license seat to your license, to register your test2.domain site.