[wpsolr]

7 years, 7 months ago in reply to: Error 500 on 2.2 page #10793

This query returned 399249 rows?

This would mean your posts have 399249 custom field definitions (not content, definition).
This is not possible.

[wpsolr]

7 years, 7 months ago in reply to: Error 500 on 2.2 page #10785

I suspect a lot of data is in your metas table.

Please try to execute the SQL on your WP:

SELECT distinct meta_key
FROM wp_posts as POSTS
INNER JOIN wp_postmeta AS POSTMETAS ON POSTS.ID = POSTMETAS.post_id
WHERE POSTS.post_type = 'post'

You can also install https://wordpress.org/plugins/query-monitor/ and check the longest queries.

• This reply was modified 7 years, 7 months ago by wpsolr.

[wpsolr]

7 years, 7 months ago in reply to: Error 500 on 2.2 page #10782

What are your versions of WP, and PHP?

[wpsolr]

7 years, 7 months ago in reply to: Error 500 on 2.2 page #10781

Hello,

It should not be the number of posts. We have clients with millions of posts/products/topics.

Do you get errors in WP debug.log?

[wpsolr]

7 years, 7 months ago in reply to: Quicksearch results by Taxonomies as well as Products #10771

– I’ve rebuilt UI elements, including suggestions, with Twig templates.

– The suggestions can now also show taxonomies, with a redirection to their taxonomy page.

– I’m now building a new suggestion template that can group suggestions, not by relevancy, but by “type” or “meta type”.

The “type” is the post type (post, page, product …), or the taxonomy name (tag, category, “title” in your case, …).

The “meta type”, on the other hand, is grouping results in only 3 groups: “Post type”, “Taxonomy”, “Term”.

The groups are not sorted with a predefined order. Instead, they are sorted based on their most relevant content. So, if for a keyword, suggestions returns terms and products, and terms contain the most relevant content, then terms group will be displayed in first position. Another keyword can therefore display products group first.

Let me know if this fits in your requirements.

[wpsolr]

7 years, 7 months ago in reply to: Support for all WP query’s #10762

I have no immediate plan to add this feature in WPSOLR.

If you have an urgent need, testing ElasticPress seems the reasonable option.

[wpsolr]

7 years, 7 months ago in reply to: Support for all WP query’s #10760

Yes, you should, if ElasticPress is able to fix your main issue (managing 20M posts in the backend).

If it does not work well, then let me know. I’ll consider adding the posts management in the backend too.

[wpsolr]

7 years, 7 months ago in reply to: Support for all WP query’s #10757

Pretty good reason indeed.

Did you try Elasticpress?

[wpsolr]

7 years, 7 months ago in reply to: Quicksearch results by Taxonomies as well as Products #10755

I am rewriting all UI elements with Twig templates.

It will allow more flexibility:
– Multiple templates for the same UI (admin can choose among several suggestion layouts for instance)
– Ability to customize UIs (by copying and editing the twig templates in the child theme folder)

[wpsolr]

7 years, 7 months ago in reply to: Support for all WP query’s #10753

Right now, the only backend post types search WPSOLR can replace are WooCommerce orders.

Do you have a special reason for replacing backend posts search?

[wpsolr]

7 years, 7 months ago in reply to: Support for all WP query’s #10724

Can you detail your question?

[wpsolr]

7 years, 7 months ago in reply to: Quicksearch results by Taxonomies as well as Products #10719

I’ve completed the first step: indexing and retrieving taxonomies.

I am working on suggestions layouts.

[wpsolr]

7 years, 7 months ago in reply to: Support for all WP query’s #10717

Hi,

WPSOLR works on all archives: Search, Home/Blog, Author, Year, Month, Day, Categories, Tags.

[wpsolr]

7 years, 7 months ago in reply to: Quicksearch results by Taxonomies as well as Products #10712

I had a good thought about it, and found that your needs could be very useful as a new feature I postponed until now: the “Triggers”.

Your requirement, in a nutshell, are to suggest products if a SKU is typed, else suggest taxonomies (categories and terms). The suggestion links should open their respective product or taxonomy archive.

The new “Triggers” are a generalisation of that:
1) Extend current post types search to also embrace categories and terms
2) Define one to several “conditions” for which to apply additional “filters”

Triggers must match some conditions:
– Url patterns
– Search type (Suggestion or search)
– Keywords pattern
– jQuery selectors

Trigger’s filters can be:
– Filter by post types
– Filter by taxonomy values
– Filter by custom field value
– Filter by date
– …

So, in your situation, you would define 2 Triggers named “Terms suggestions” and “Product SKU suggestions”:

Trigger “Terms suggestions”:
– Conditions: apply on suggestions only, on any url, for any search box, for any keywords NOT matching a SKU format
– Filters: search in any term, in any category

Trigger “Product SKU suggestion”:
– Conditions: apply on suggestions only, on any url, for any search box, for any keywords matching a SKU format
– Filters: search in any products

Depending on what the visitor would enter in the search box, the suggestions would then show products or taxonomies.

If your SKUs do not have a well-defined pattern, then you could just create 2 distinct search boxes, associated to their own filter, but without the matching SKU format condition.

Let me know if it would fit.

[wpsolr]

7 years, 7 months ago in reply to: Quicksearch results by Taxonomies as well as Products #10685

The only time I need individual product is if it is searched by SKU

How do you imagine that feature? Adding a checkbox “Search in SKU” close to the search box?