[wpsolr]

5 years ago in reply to: integration issues – custom fields, speed, drop down list sort etc #27751

Let’s fix #1 first.

a) I never seen so many attributes and custom fields indexed. Are all of them necessary?
b) How many indexes were created in Algolia (one main index, and one replica per sort).

[wpsolr]

5 years ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27745

You can then install the files from the zip in WPSOLR’s folder, and reload the index (to apply the change of schema).

Or try:
– Opensolr
/guide/video-gallery-twentysixteen-theme-search-template/video-setup-demo-twentysixteen-theme-template-opensolr/
– Searchstax
/guide/configuration-step-by-step-schematic/configure-your-indexes/create-a-searchstax-solr-cloud-manager-index/

[wpsolr]

5 years ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27743

Can you delete your index from WPSOLR?

Was the index created by your hosting before you create it in WPSOLR?

[wpsolr]

5 years ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27739

Did you change also the /solr/xxxx path name in the new WPSOLR’s index screen?

You can find the file in the plugin’s folder:
/wpsolr/core/classes/engines/solarium/admin/conf/5.0

[wpsolr]

5 years ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27731

The simplest is to create a new index from WPSOLR’s admin. The new schema will be installed automatically.

[wpsolr]

5 years ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27730

<dynamicField name="*_i" type="plong" indexed="true" stored="true"/>

Did you mean “long” instead of “plong” : <dynamicField name="*_i" type="long" indexed="true" stored="true"/> ?

[wpsolr]

5 years ago in reply to: WPengine staging domain format doesn’t allow trial #27697

WPEngine’s staging domains will be added to the domains considered as staging by WPSOLR, in next release.
In the meantime, you can take the free trial on our pricing page.

• This reply was modified 5 years ago by wpsolr.

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27695

Please create another topic.

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27693

My tests show no problem with products filtered by category both on admin and on front.

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27691

Great.

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27687

I’d need the full query to tell you more. You sent me queries stopping at “comments”: {

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27686

I made my tests without the boosts.

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27683

I just tested orders search with success on Elasticsearch:
– first name + last name
– phone (even partial)
– order# (contrary to my previous answer, it works!)

Did you setup your search with screen 2.3 (boosts)?

• This reply was modified 5 years, 1 month ago by wpsolr.

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27681

so search by first and last name should work no?
it works with first or last, but not first+last

Can you create an order with only English characters (to check if the English analyser is the problem), and try to find it?

[wpsolr]

5 years, 1 month ago in reply to: Elasticpress shingle TokenFilter error #27678

Order number is the post_id. It is indexed, but used for filtering only, not for searching.
(It worked with Algolia though for any reason).

Some default post fields are searchable, like title and description, but in general searchable fields are custom fields (like the product sku).