[wpsolr]

6 years, 8 months ago in reply to: Filters are not applying #17650

I tried colours. Looks fine. For instance /winkel/zwart+heren-sport-hoodies

[wpsolr]

6 years, 8 months ago in reply to: Filters are not applying #17645

Try with “/%category%/%postname%/” instead.

[wpsolr]

6 years, 8 months ago in reply to: Filters are not applying #17643

It seems that the issue is due to permalinks set to “/%category%/%postname%”.

[wpsolr]

6 years, 8 months ago in reply to: Filters are not applying #17642

Indeed, “Redirect facets to permalinks home” unchecked removes the “/winkel/” permalinks, hence the 404. It is a bug.

But with “”Redirect facets to permalinks home”, there are issues with product categories.

Checking the problem…

[wpsolr]

6 years, 8 months ago in reply to: Draft products in backend #17640

You just need to check option “Index all status” on each post types selected for indexing in screen 2.2

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17636

1) I changed the score field error status to “stop at first error”.

Then I got this error during indexing:
“Value 188.0 of field “algoritme_score” of post->ID=294197 (“Happy Socks – Multipack sokken – Meerkleurig”) is not of type “Integer number, sortable”. Check out field’s definition in WPSOLR data settings (tab 2.2) .”

2) I changed score format to “Real number” (was “Integer”):
Indexing is going well now. And sort looks fine.

3) I also added the score as a slider filter. Just to see some scores.

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17634

Can you activate the Elasticsearch trace mode “Log the search engine queries?” in screen 2.1?

Then check your debug.log for the query in error.

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17630

Yes, I stopped indexing at 300, just for testing.

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17628

I created a new index, indexed a few products. And your filters are back!

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17626

There should be errors, as mentioned in the chrome js console:
“WPSOLR PRO : an error prevented the search engine query to be executed. To prevent empty results, the default WordPress query is used instead. Please check the error details in your debug.log file.”

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17623

You can also try to create a new index. We had had a similar issue when you started evaluating WPSOLR, if I remember.

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17622

What new errors do you see now in debug.log?

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17620

I still cannot see any WPSOLR filters on your site right now.

[wpsolr]

6 years, 8 months ago in reply to: Different options to sort #17618

You have strange errors from Wordfence plugin. As if WordPress had no rights to write in its own filesystem.

Can you check with your provider support?

[wpsolr]

6 years, 8 months ago in reply to: Toolset Views Results #17614

You insert your view shortcode as usual, and WPSOLR will replace the queries in the background. This is transparent.