Forum Replies Created
-
wpsolrKeymaster1 year, 2 months ago in reply to: Filtering Issue with Child Terms and ‘OR’ Setting #54900
There is no plan to enable “OR” condition with select2.js facets.
wpsolrKeymaster1 year, 3 months ago in reply to: WPSOLR active and working but WordPress standard search results are shown #54478When an error is detected, WPSOLR reverts back to the standard WP search.
You should be able to read the error in your debug.log file if you activate WP_DEBUG_LOG.
Or you can get it live from our Query Monitor add-on.
wpsolrKeymaster1 year, 3 months ago in reply to: WPSOLR active and working but WordPress standard search results are shown #54464Which release of WPSOLR is it?
wpsolrKeymaster1 year, 3 months ago in reply to: Phrase based search without using fuzzy logic #54435There are no other options in the plugin. You can modify your index settings and mappings if you find a better way for your use case.
wpsolrKeymaster1 year, 3 months ago in reply to: Critical Error on SERP after upgrade to 24.0.1 #54404A plugin is probably installing the same library, but in an older version, creating this conflict.
wpsolrKeymaster1 year, 3 months ago in reply to: Critical Error on SERP after upgrade to 24.0.1 #54401After investigation, it will not be possible to remove the dependency.
=> react/promise is required by ezimuel/ringphp, itself required by opensearch-project/opensearch-php
wpsolrKeymaster1 year, 3 months ago in reply to: Critical Error on SERP after upgrade to 24.0.1 #54380Thanks for the feedback. We will investigate to remove the React dependency from WPSOLR’s composer on next release.
wpsolrKeymaster1 year, 4 months ago in reply to: Indexing Error When URL Field Returns 404 or Forbidden #54221I guess you are using the WPSOLR ACF add-on. The piece of code that extract file contents from ACF file fields has not changed, and was always expected to fail on 404 or 403.
The only thing you can do is to fix each post with urls, or prevent them from being indexed:
– Deactivate the ACF add-on “Index all files option”, and activate the same option on each post meta-field without error
– Or activate the ACF add-on “Index all files option”, and deactivate the same option on each post meta-field with errorswpsolrKeymaster1 year, 4 months ago in reply to: When using fuzzy search it ignore single word more than 9 characters #54184It is not possible to tweak queries or fuzziness. It would not work anyway, as the apparent 9 character limits is inside Lucene.
You can fall back to my initial suggestion:
You could perhaps avoid fuzziness with a little trick (and better search speed and scalability):
when you index your SKU, add the SKU without the first letter. For instance, index SKU array with [‘K1239807’, ‘1239807’].wpsolrKeymaster1 year, 4 months ago in reply to: When using fuzzy search it ignore single word more than 9 characters #54182WPSOLR does not skip fuzzy logic on long words, as you can see with
panasonic~1in your query.wpsolrKeymaster1 year, 4 months ago in reply to: When using fuzzy search it ignore single word more than 9 characters #54179You can copy the query and modify the fuzzy part (panasonic~1) in Opensearch dashboards to verify if Opensearch is limited to 9 characters with fuzziness.
wpsolrKeymaster1 year, 4 months ago in reply to: When using fuzzy search it ignore single word more than 9 characters #54175You can activate the query monitor add-on that will show you the exact Opensearch query syntax used.
You can then execute/tweak the query in your Opensearch dashboard.If we omit 2,3,4 starting characters we might have to do something like this [‘K1239807’, ‘1239807’,’239807′,39807′,’9807′]. Will there be any issue with that?
Fuzzy is limited to 2 characters. Using the “contains” operator instead in 2.1 with this fix should give you results on longer missing prefixes.
On the other hand, fuzzy currently works on all fieldswpsolrKeymaster1 year, 4 months ago in reply to: When using fuzzy search it ignore single word more than 9 characters #54173It is difficult to understand why each world should be less than 9 characters for the fuzzy operator. I checked in the Lucene documentation, but it is no mentioned.
You could perhaps avoid fuzziness with a little trick (and better search speed and scalability):
when you index your SKU, add the SKU without the first letter. For instance, index SKU array with ['K1239807', '1239807'].wpsolrKeymaster1 year, 5 months ago in reply to: Bug Fix Recommendation for Older Browser Compatibility #54159This javascript code is very sensitive and extremely difficult to modify and test.
This is why we cannot update it.
wpsolrKeymaster1 year, 5 months ago in reply to: PHP Fatal error: Declaration of Monolog\Logger::emergency #54064Fix released with WPSOLR 24.0.1.