[wpsolr]

5 years, 10 months ago in reply to: Index Problem, error details failed to parse field #22889

Do you know what is:
{ “name”: “Cilt Durumu”, “value”: “Ciltli”, “position”: “5”, “is_visible”: “1”, “is_variation”: “0”, “is_taxonomy”: “0” }
It could be a custom field that contains object values instead of a string.

[wpsolr]

5 years, 10 months ago in reply to: Index Problem, error details failed to parse field #22887

Thanks.

This post contains a category with an object, rather than a string. Which causes the error.

"categories": [ ..., { "name": "pa_yazar", ... }]

[wpsolr]

5 years, 10 months ago in reply to: Index Problem, error details failed to parse field #22885

When indexing, activate the debug checkbox and set the batch size to 1. When it fails, click on index once more, to only get the debug infos of the failing ID. Check the debug details, especially the content of the ‘categories’ field.

[wpsolr]

5 years, 10 months ago in reply to: WP Solr not respecting Toolset views filters #22876

I created a fix on the roadmap: https://trello.com/c/jPGdXlP8/116-bug-toolset-views-not-respecting-some-parameters

[wpsolr]

5 years, 10 months ago in reply to: WP Solr not respecting Toolset views filters #22872

Thanks.
Did you find why your Toolset archives are not working with WPSOLR?

[wpsolr]

5 years, 10 months ago in reply to: WP Solr not respecting Toolset views filters #22868

I just did.

[wpsolr]

5 years, 10 months ago in reply to: WP Solr not respecting Toolset views filters #22866

I invited you on my 100K Toolset demo:
https://demo-toolset-cloudways-100k-products.wpsolr.com/?s=

Have a look, perhaps you can find out how your own site settings are different?

[wpsolr]

5 years, 10 months ago in reply to: How do you change the default loading gif? #22865

It is not a feature by design in WPSOLR.
Perhaps CSS?

.wpsolr_loading {
background-image: url(‘image here’)!important;
}

[wpsolr]

5 years, 10 months ago in reply to: Excluding Facets from Search Engines #22864

WPSOLR SEO add-ons do not work on category pages. Therefore the noindex/nofollow feature is not available on categories.

[wpsolr]

5 years, 10 months ago in reply to: Autocomplete Suggestions Performance #22863

The WPSolr autocomplete is not using the Algolia Instant Search?

No, WPSOLR is using a WP compatible autocomplete (wp-ajax) to be able to integrate deep with WP.

Can you give some advice on how one would best go about building an Autocomplete that would work with WPsolr (using the instant search offers)

It would require a full design and development, not a simple advice.

[wpsolr]

5 years, 10 months ago in reply to: Algolia searches are not being recorded #22858

And on your indice real-time logs in Algolia?

[wpsolr]

5 years, 10 months ago in reply to: Autocomplete Suggestions Performance #22857

– Algolia’s instant search is a javascript calling Algolia servers directly.

– WPSOLR’s Algolia search is a backend search, executed by a PHP code called by a standard WP Ajax call. The WP Ajax call can be slow sometimes (it executes the full WP core). You can check in WPSOLR ALgolia’s logs how fast the Algolia’s call is, and compare it to the Ajax call.

[wpsolr]

5 years, 10 months ago in reply to: indexing values within _product_attributes that are NOT archives #22856

Custom attributes are not specifically supported (by opposition to global attributes, which are taxonomies).
But if they are stored as custom fields, they should be indexable.

[wpsolr]

5 years, 10 months ago in reply to: Excluding Facets from Search Engines #22855

This option just adds nofolow/noindex on each facet link.

[wpsolr]

5 years, 10 months ago in reply to: Search sort options #22851

Something like ?

option[value="xxx"]{
display:none;
}