[wpsolr]

5 years, 2 months ago in reply to: How to replace default wordpress serach #27330

If you selected your theme’s search template in screen 2.1, it is now up to your theme to show whatever it can within the query loop. WPSOLR only takes care of the query.

[wpsolr]

5 years, 2 months ago in reply to: Override default template of search results #27329

As WPSOLR only replaces archives, you must use the Elementor “Archive posts” widget, not the “Posts” widget.

[wpsolr]

5 years, 2 months ago in reply to: Override default template of search results #27327

Can you check your console javascript errors, and eventually your wp-content/debug.log errors?

[wpsolr]

5 years, 2 months ago in reply to: Override default template of search results #27325

If not, please check your WP debug logs for errors.

[wpsolr]

5 years, 2 months ago in reply to: How to replace default wordpress serach #27324

In theory, you have to follow WPSOLR screens in sequence: /guide/configuration-step-by-step-schematic/

In screen 2.1, did you select the search archive check box, so WPSOLR can replace the default search queries?

You can check for errors in WP debug logs: when some problems occur, WPSOLR reverts to the standard WP search, and log errors.

[wpsolr]

5 years, 2 months ago in reply to: Override default template of search results #27323

Can you see the WPSOLR facets widget on your search template (inserted in an Elementor sidebar widget for instance)?

[wpsolr]

5 years, 2 months ago in reply to: Override default template of search results #27320

With Elementor template it displays CPT that I haven’t added to WPSOLR index

It works with Elementor archive templates, not with single page Elementor templates.
More generally, WPSOLR can replace archive queries.

You can find a 100K products WooCommerce demo with Elementor “Hello” theme: /wpsolr-demos/

[wpsolr]

5 years, 2 months ago in reply to: Override default template of search results #27318

Indeed, the shortcode [solr_search_shortcode] is using WPSOLR’s search twig templates, and is deprecated.

The idea instead is to use WPSOLR’s search backend while enjoying 100% of your theme’s search features.

WPSOLR provided the shortcode a long time ago, for a simple blog post search.
But now, there is simply no need of replacing advanced search templates like Flatsome/WooCommerce.

If you choose “Use my theme’s search template” in screen 2.1, you will need no more the shortcode: all your theme’s archive templates will be used as usual to display results coming from WPSOLR’s backend (Elasticsearch, Solr, or Algolia, and soon Weaviate AI semantic search).

[wpsolr]

5 years, 2 months ago in reply to: Could not activate license key after database upgrade #27315

I removed the previous site activation from your license. You can activate your site now.

[wpsolr]

5 years, 3 months ago in reply to: Could not activate license key after database upgrade #27311

Sorry, but I could not find a subscription to your email or to your company’s name.

[wpsolr]

5 years, 3 months ago in reply to: Override default template of search results #27309

I’d like to emphasis that the WPSOLR search template is deprecated and not supported. Instead, your theme’s search template is recommended (you can select it in screen 2.1).

On the other hand, the suggestions’ twig templates are supported. You can find a full example in /wpsolr-examples.

[wpsolr]

5 years, 3 months ago in reply to: missing required field: appKey #27307

Did you solve your problem?

[wpsolr]

5 years, 3 months ago in reply to: Invalid Number: n for field is_excluded_s #27305

Strange indeed.

[wpsolr]

5 years, 3 months ago in reply to: Invalid Number: n for field is_excluded_s #27303

(both with type “long”, instead of “integer”)

[wpsolr]

5 years, 3 months ago in reply to: Invalid Number: n for field is_excluded_s #27302

Can you check the content of some files in your WPSOLR plugin?

– File /wp-content/plugins/wpsolr-pro/wpsolr/core/classes/engines/solarium/admin/conf/wpsolr_schema_5.0.json
Should contain:

"add-dynamic-field": {
    "name": "*_i",
    "type": "long",
    "indexed": true,
    "stored": true
  }

– File /wp-content/plugins/wpsolr-pro/wpsolr/core/classes/engines/solarium/admin/conf/opensolr/5.0/schema.xml
Should contain:
<dynamicField name="*_i" type="long" indexed="true" stored="true" multiValued="true" docValues="true"/>