[pridigital]

12 months ago #31144

Hi there,

I wondered if there is a way to use the “Views” extension without using the “Toolset Views” plugin. I couldn’t find any documentation about this matter.

I see the following message in the interface, though:

Create views, and use them anywhere with shortcodes or Elementor widgets.

Would you mind documenting the process or sharing some examples?
Thanks

[wpsolr]

12 months ago #31145

WPSOLR View are in their early release. For now they can be used to configure 2 search engines and use them on different sections of a site.

For instance, a view for all searches with Elasticsearch, and a view for Question Answering with Weaviate.

[pridigital]

12 months ago #31150

Hi there,
I see… but how do I use in my code a custom view instead of the default view? I thought it was via a shortcode, but where can I find it?
Thanks again

[wpsolr]

12 months ago #31151

Right now WPSOLR views are not for displaying search results. Showing results is still the responsibility of themes, and only on archives.

[pridigital]

12 months ago #31152

I understand what you’re saying, which is not what I meant. I guess I was asking, for instance, if it could be possible to use “View 1” on taxonomy-a.php and “View 2” on taxonomy-z.php.

[wpsolr]

11 months, 4 weeks ago #31153

For now, it is not possible.

[pridigital]

7 months, 3 weeks ago #32496

Hi,
following up on my client’s query-
We created 2 views. However when we configure any 2.x tab it seems to apply those config changes to all views.
Additionally, you mentioned views extension is in early release, any indication on when we can see a stable release?

[wpsolr]

7 months, 3 weeks ago #32497

However when we configure any 2.x tab it seems to apply those config changes to all views.

Indeed. But as soon as you edit and save a view’s configuration, it will stop following the default view’s settings.

any indication on when we can see a stable release?

Views are stable.
You can use them with several indexes to show several suggestions at the same time.
Or you can activate/deactivate them to test different settings for your front-end archive searches.
Or use a different index for admin post types search and front-end search (for instance Elasticsearch for WooCommerce admin orders, and Weaviate with GPT-3.5 AI search for your front-end).
Or use a view for media search with Weaviate/CLIP image search.