[wpsolr]

3 years, 10 months ago in reply to: Wpsolr requests needs Sometimes 5 or 6 sec. #31619

The search itself is usually fast (100 ms), the remaining time being spent on theme’s UI rendering.

Configure WPSOLR’s Query monitor add-on to see the search timing.

[wpsolr]

3 years, 10 months ago in reply to: Seo Permalinks not worked for us #31616

Permalinks are present on your search, not on your other archives (categories or tags).

[wpsolr]

3 years, 10 months ago in reply to: Seo Permalinks not worked for us #31613

Permalinks are activated on https://1000-brands.com/shop/

As mentioned in the permalinks documentation, permalinks do not apply on taxonomy archives like https://1000-brands.com/bekleidung/blusen-tuniken/

[wpsolr]

3 years, 10 months ago in reply to: 2.2 Data cannot be opened #31612

Sure.

In file wpsolr-pro/wpsolr/core/classes/extensions/premium/includes/indexing-custom-fields.inc.php, remove the code from line 138 to line 175 (included) displayed below:

<div class="wdm_row">
  <div class="col_left">Carried by relation to:</div>
  ....
  <div class="clear"></div>
</div>

[wpsolr]

3 years, 10 months ago in reply to: 2.2 Data cannot be opened #31610

This will be fixed in Release 22.6

I can give you a workaround trick if you are in a hurry (a modification of a WPSOLR source file)

[wpsolr]

3 years, 10 months ago in reply to: Yoast Breadcrumbs removed with WP Solr activated #31604

Despite a thorough investigation, I could not locate nor fix the conflict with Yoast breadcrumbs.

[wpsolr]

3 years, 10 months ago in reply to: Seo Permalinks not worked for us #31601

Please post here a capture of your settings:
– The SEO add-on settings
– The facet “pa_color” settings

[wpsolr]

3 years, 10 months ago in reply to: 2.2 Data cannot be opened #31600

This topic could be related: /forums/topic/memory-size-exhausted-error-in-includes-indexing-custom-fields-inc-php167/

[wpsolr]

3 years, 10 months ago in reply to: Yoast Breadcrumbs removed with WP Solr activated #31590

I could reproduce your issue on my local environments.

Investigating…

[wpsolr]

3 years, 10 months ago in reply to: Taxonomy not returning results despite being indexed #31587

Fixed in release 22.6

[wpsolr]

3 years, 10 months ago in reply to: Incorrect results for search term #31568

Each search engine has its own way of dealing with stop words.

– Apache Solr: https://solr.apache.org/guide/solr/latest/indexing-guide/filters.html#stop-filter
– Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-stop-analyzer.html

For engines with full or hybrid AI capabilities (Weaviate, Google Retail, Algolia), this should not be so important, as results should be based on the meaning of keywords rather than on keywords themselves.

[wpsolr]

3 years, 10 months ago in reply to: Incorrect results for search term #31566

You have the exact same results for https://www.broinc.com/media?s=butting and https://www.broinc.com/media?s=but

I think “butting” is stemmed to “but”, which should be a stop word.

[wpsolr]

3 years, 10 months ago in reply to: Search in title based on condition #31564

There is no hook for updating the query fields.

[wpsolr]

3 years, 10 months ago in reply to: Search in title based on condition #31562

Duplicate of Limit Search results to a certain custom taxonomy

[wpsolr]

3 years, 10 months ago in reply to: 2.2 Data cannot be opened #31558

What error?