[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11962

A small workaround to detect the problem origin:

Line 313 of /public_html/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/models/post/class-wpsolr-model-post.php

Replace

array_push( $term_parents_names, $term_parent->name );

// Add the term to the non-flat hierarchy (for filter queries on all the hierarchy levels)
array_push( $taxonomy_non_flat_hierarchies, $term_parent->name );

with

if ( method_exists( $term_parent, 'name' ) ) {

	array_push( $term_parents_names, $term_parent->name );

	// Add the term to the non-flat hierarchy (for filter queries on all the hierarchy levels)
	array_push( $taxonomy_non_flat_hierarchies, $term_parent->name );

} else {

	throw new \Exception( sprintf( "WPSOLR: term %s for taxonomy %s has no name", $term_parent_id, $parent ) );
}

[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11960

I suspect your cleaning of taxonomies has yet to be continued.

[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11957

Restart indexing with debug mode “on” and batch size “1”, until it stops in error. Then restart it once more. Check the product id in the debug trace and exclude the product with its WPSOLR metabox.

[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11954

Can you repost the error here?

(we do not access clients environment during support)

[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11952

Same issue on another product.

[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11950

Then, it’s not that product that causes the problem.

Edit the product, save it. What message appears in the notice header?

[wpsolr]

7 years, 5 months ago in reply to: WPSOLR: error on term #11948

You can prevent indexing it with the product metabox “Do not search” checkbox.

[wpsolr]

7 years, 5 months ago in reply to: Unable to replace the default WordPress search with WPSOLR search #11946

I don’t think so. Why?

[wpsolr]

7 years, 5 months ago in reply to: Need help to creating AMP compatible Search on our website. #11928

It’s too big and probably impossible. The WPSOLR facets use several hundred lines of javascript, and several major javascript libraries (slider2, ionRange, ….). None will work with AMP.

[wpsolr]

7 years, 5 months ago in reply to: Need help to creating AMP compatible Search on our website. #11926

There are no plans at the moment for an AMP version.

[wpsolr]

7 years, 5 months ago in reply to: Need help to creating AMP compatible Search on our website. #11924

Hi,

Thanks for the request.

I wonder why you would need WPSOLR for you current search. You already have one installed with filters, and not enough products to be in trouble.

[wpsolr]

7 years, 5 months ago in reply to: Unable to replace the default WordPress search with WPSOLR search #11921

Thanks.

Which PHP version do you have?

Is your php curl installed? https://php.net/manual/en/book.curl.php

[wpsolr]

7 years, 5 months ago in reply to: Multiple sliders override each other #11918

Yes.

[wpsolr]

7 years, 5 months ago in reply to: Multiple sliders override each other #11916

The slider selection always show the min-max values for the current selection.

If you select a kilometerstand with results containing the current bouwjaar min-max values, nothing changes in bouwjaar. Else, bouwjaar is updated with min-max of results.

[wpsolr]

7 years, 5 months ago in reply to: Unable to replace the default WordPress search with WPSOLR search #11914

What I said earlier:
– Trace all queries in Elasticsearch logs
– Ask your hosting provider