Facets layouts: Range slider A Range Slider is an intuitive user interface to position a number within a range. A typical Range Slider usually can be used to filter results between two prices, or two dates. WPSOLR uses the ion.rangeSlider javascript library to render the Range Slider control user interface. This library is very popular, and very flexible. As we will see, WPSOLR is able to accept all the ion.rangeSlider parameters, to customize your slider filters with tens of features. The WPSOLR Range Slider can work both with numbers and dates. Both are described below in their own chapter. 1) Activate the Advanced Layout add-on Range sliders are part of the Advanced Layout add-on (also name "Theme" add-on). You need to activate it, to be able to select and configure the Range Slider facets. Theme add-on activation 2) Numbers Range Slider a) Select the custom field(s) (like WooCommerce "_price", or "rating", or "_stock", ...), which contain numbers and are configured with type "Integer" or "Float" in screen 2.2 b) Save c) Set a field label if necessary, and select the "Range Slider" layout. You can also translate your field label with WPML/Polylang string modules d) Save e) Select the Range Slider "Skin". The skins are predefined css applied to the slider. f) Set the ion.rangeSlider javascript options to customize how your slider will look like (money prefix, decimal separators, grid ....). You can also translate your javascript options with WPML/Polylang string modules. For instance, to show a "$" prefix for language "en-US", and "€" for language "fr-FR". For instance, to round decimals: wpsolr_ion_range_slider_options = { grid: true, prefix: "€", prettify: function my_prettify (n) { return Math.floor(n); }}; g) Save h) Add the "WPSOLR Facets" widget to your search Ion.rangeSlider: configure number custom field Here is how your search facets could look like, then: Ion.rangeSlider: number filters 3) Dates Range Slider Ion.rangeSlider: configure date filters with different locales Ion.rangeSlider: results with date filters and different locales displaydate_dt is the post type modification date. Let's format it as a US formatted date: wpsolr_ion_range_slider_options = { grid: true, prettify: function tsToDate (ts) { var lang = "en-US"; var d = new Date(ts); return d.toLocaleDateString(lang, { year: 'numeric', month: 'long', day: 'numeric' }); } }; Ion.rangeSlider: date formatted with "us-US" locale displaymodified_dt is the post type creation date. Let's format it as a Japanese formatted date: wpsolr_ion_range_slider_options = { grid: true, prettify: function tsToDate (ts) { var lang = "ja-JA"; var d = new Date(ts); return d.toLocaleDateString(lang, { year: 'numeric', month: 'long', day: 'numeric' }); } }; Ion.rangeSlider: date formatted with Japanese "ja-JA" locale wpsolr_date_custom_field is a custom field, configured in screen 2.2 with a date type. Let's format it as a French formatted date: Ion.rangeSlider: format a custom field as a date wpsolr_ion_range_slider_options = { grid: true, prettify: function tsToDate (ts) { var lang = "fr-FR"; var d = new Date(ts); return d.toLocaleDateString(lang, { year: 'numeric', month: 'long', day: 'numeric' }); } }; Ion.rangeSlider: date formatted with French "fr-FR" locale WPSOLR - User guide...

The Jobify add-on for WPSOLR is deceptively simple. Configure WPSOLR as usual, activate the add-on, and that's it. All your jobs search are now accelerated as if by magic. No extra-setup, no knowledge of Elasticsearch or Solr are even required. Below are explained the steps to activate the add-on. Notice that most steps are optional. If you prefer watching the full tutorial showing the setup of WPSOLR with Jobify: With Elasticsearch: 1) Create an index For Elasticsearch: Video: Create an Elasticsearch index automatically For Solr: Video: Create an Apache Solr index semi-automatically For SolrCloud: Video: Create an Apache SolrCloud index automatically You can also want to search for more informations on index creation, Elasticsearch, Apache Solr, or Elasticsearch/Solr hosting providers. Or just browse the Elasticsearch/Solr forums. 2) Activate the Jobify add-on The only action required for the add-on is to activate it. The add-on will then operate in the background to transform mySQL queries in Elasticsearch or Solr queries. Therefore, no other Jobify configuration is necessary. Jobify add-on activation 3) Select the archive types to speed up Pick the archive search page (which you want to accelerate with WPSOLR), among the 8 archive types. 4) Index the "Jobs" post type This step is mandatory. Select the "Jobs" post type, and its taxonomies and custom fields in screen 2.2: items will be indexed, and only then their custom fields can be used as a facet or a sort in Elasticsearch or Solr. Jobify add-on: index "Jobs" post type 5) Index your content You created your index, configured it. It's now time to fill it with your data (selected in screen 2.2): Index your Jobify jobs 8) Nothing else! Yes, that's it. From now on, WPSOLR will replace your Jobify MySQL queries with faster Elasticsearch/Solr queries. WPSOLR - User guide...

WPSOLR PRO + Jobify Theme + Elasticsearch This video suppose you already have installed a local Elasticsearch. You will see how to setup WPSOLR PRO to speedup the Listify search, including geolocation, with: Jobify Theme Your local Elasticsearch What is the "Jobify Theme" extension ? Jobify is made for huge jobs searches, including geolocation. As soon as the number of jobs grows, so is the time to display search results to visitors. WPSOLR PRO transparently replaces Jobify searches and sorting with Elasticsearch searches. The best way to speed up jobs searches, whatever the number of jobs, even millions. What is in the video ? The video shows how to: Import the Jobify data examples Create and configure automatically an Elasticsearch index Activate and set up the WPSOLR PRO Jobify Theme extension Browse live searches and filters, including location and categories WPSOLR - Video Tutorials...

WPSOLR PRO + Directory+ Theme + Elasticsearch This video suppose you already have installed a local Elasticsearch. You will see how to setup WPSOLR PRO to speedup the Directory+ search, including geolocation, with: Directory+ Theme Your local Elasticsearch What is the "Directory+ Theme" extension ? Directory+ is made for huge items searches, including geolocation. As soon as the number of items grows, so is the time to display search results to visitors. WPSOLR PRO transparently replaces Directory+ searches and sorting with Elasticsearch searches. The best way to speed up items searches, whatever the number of items, even millions. What is in the video ? The video shows how to: Import the Directory+ data examples Create and configure automatically an Elasticsearch index Activate and set up the WPSOLR PRO Directory+ Theme extension Browse live searches and filters, including geolocation and distance filters WPSOLR - Video Tutorials...

The Listify add-on for WPSOLR is deceptively simple. Configure WPSOLR as usual, activate the add-on, and that's it. All your listings search are now accelerated as if by magic. No extra-setup, no knowledge of Elasticsearch or Solr are even required. Below are explained the steps to activate the add-on. Notice that most steps are optional. If you prefer watching the full tutorial showing the setup of WPSOLR with Listify: With Elasticsearch: With Apache Solr: 1) Create an index For Elasticsearch: Video: Create an Elasticsearch index automatically For Solr: Video: Create an Apache Solr index semi-automatically For SolrCloud: Video: Create an Apache SolrCloud index automatically You can also want to search for more informations on index creation, Elasticsearch, Apache Solr, or Elasticsearch/Solr hosting providers. Or just browse the Elasticsearch/Solr forums. 2) Activate the Listify add-on The only action required for the add-on is to activate it. The add-on will then operate in the background to transform mySQL queries in Elasticsearch or Solr queries. Therefore, no other Listify configuration is necessary. Listify add-on activation 3) Select the archive types to speed up Pick the archive search page (which you want to accelerate with WPSOLR), among the 8 archive types. 4) Index the "Listings" post type This step is mandatory. Select the "Listings" post type, and its taxonomies and custom fields in screen 2.2: items will be indexed, and only then their custom fields can be used as a facet or a sort in Elasticsearch or Solr. Listify add-on: index "Listings" post type 5) Index your content You created your index, configured it. It's now time to fill it with your data (selected in screen 2.2): Index your Listify listings 8) Nothing else! Yes, that's it. From now on, WPSOLR will replace your Listify MySQL queries with faster Elasticsearch/Solr queries. WPSOLR - User guide...

The Directory+ add-on for WPSOLR is deceptively simple. Configure WPSOLR as usual, activate the add-on, and that's it. All your items listings search are now accelerated as if by magic. No extra-setup, no knowledge of Elasticsearch or Solr are even required. Below are explained the steps to activate the add-on. Notice that most steps are optional. If you prefer watching the full tutorial showing the setup of WPSOLR with Directory+: 1) Create an index For Elasticsearch: Video: Create an Elasticsearch index automatically For Solr: Video: Create an Apache Solr index semi-automatically For SolrCloud: Video: Create an Apache SolrCloud index automatically You can also want to search for more informations on index creation, Elasticsearch, Apache Solr, or Elasticsearch/Solr hosting providers. Or just browse the Elasticsearch/Solr forums. 2) Activate the Directory+ add-on The only action required for the add-on is to activate it. The add-on will then operate in the background to transform mySQL queries in Elasticsearch or Solr queries. Therefore, no other Directory+ configuration is necessary. Directory+ add-on activation 3) Select the archive types to speed up Pick the archive search page (which you want to accelerate with WPSOLR), among the 8 archive types. 4) Index "Items" This step is mandatory. Select the "Items" post type, and its taxonomies and custom fields in screen 2.2: items will be indexed, and only then their custom fields can be used as a facet or a sort in Elasticsearch or Solr. 5) Configure facets (Optional) Facets are the dynamic filters you probably saw on WooCommerce sites like Amazon. You can select any of the custom fields and taxonomies you previously chose in screen 2.2. a) First add the facets: b) Save the facets 6) Add WPSOLR facets widget (Optional) Once you configured the facets in screen 2.4, you can add the WPSOLR Facets Widget to each archive type sidebar. Add facets widget Here is how the facets widget look like on the front-end, within the Directory+ search results page (after you indexed all your documents): 7) Index your content You created your index, configured it. It's now time to fill it with your data (selected in screen 2.2): 8) Nothing else! Yes, that's it. From now on, WPSOLR will replace your Directory+ MySQL queries with faster Elasticsearch/Solr queries. WPSOLR - User guide...

Video tutorial: Toolset Views archives configuration with Elasticsearch This video suppose you already have installed a local Elasticsearch. You will see how to setup WPSOLR PRO to search, index, and filter with: Toolset Views plugin TwentySixteen theme Your local Elasticsearch  You will watch how to replace Toolset Archive Views SQL queries with Elasticsearch queries. WPSOLR - Video Tutorials...

WPSOLR will automatically speed up Toolset Archive Views You do not have to choose between flexibility and scalability anymore. Keep using Toolset Views plugin as your favourite Query Builder. But boost your site speed and relevancy with WPSOLR working in the background. Bring the speed of WPSOLR to Toolset Archive Views With Toolset Views alone, you can build sophisticated queries and filters. Without any knowledge of SQL. But the more complex your queries, the less quick your views become. In fact, SQL simply slows down with more where clause, table join, table scan, and aggregation. To see how SQL statements are built with the Toolset Views Query Builder, let's install the plugin Query monitor. This plugin displays all SQL queries executed while the admin or front-end pages are loaded. Why SQL full-text search queries are slow? A full-text search is a search with keywords. For instance, the SQL query below is a search for keyword 'red'. From the SQL, you can notice several facts. First, the keywords are searched in 3 fields only (title, excerpt, content). Custom fields and products attributes are not searched at all. Secondly, the keywords are partially searched. The special character '%' is added at the beginning and at the end of the keyword, to tell mySQL to look for posts beginning with, and ending by 'red'. This is a tentative to also retrieve related keywords, like plural forms ("red", "reds", ...). But this is hugely costly, because the full-text search is not using any index. The search is opening every title/excerpt/content and tries to match it to the keywords. And obviously, a search that opens every post for every search is not scalable. The more posts you add, and the more visitors you get, the more your server will need CPU/RAM/Disk. At some point, you will not be able to afford enough server resources and you search will crash. SELECT SQL_CALC_FOUND_ROWS posts.ID FROM posts WHERE 1=1 AND (((posts.post_title LIKE '%red%') OR (posts.post_excerpt LIKE '%red%') OR (posts.post_content LIKE '%red%'))) AND posts.post_type = 'post' AND ((posts.post_status = 'publish' OR posts.post_status = 'private')) Why complex SQL queries are slow? The nicest feature of Toolset Views can be your main downfall. It is so easy to add complex filters to your views. Dates, authors, categories, tags, custom fields, and so on. There are also many comparators to choose from. BETWEEN, IN, NOT IN, ANY, NONE, >, <, and so on. Just remember that each new filter will create more stress on your server. This is probably fine if you manage few posts/products, or get few visitors. But as soon your site becomes somehow popular, all those filters will contribute to slowing it down. Eventually to the point where it can barely serve any search under 3 seconds. And 3 seconds is considered today the maximum time a visitor will be willing to wait, before leaving to your competitors. But you also probably know that speed is a key SEO factor that Google will consider, with many others, to position your site before your competition too. a) This simple Toolset View filter on date and taxonomy: Toolset View complex filter b) will generate this complex and costly SQL: SELECT SQL_CALC_FOUND_ROWS posts.ID FROM posts LEFT JOIN term_relationships ON (posts.ID = term_relationships.object_id) WHERE 1=1 AND ( ( YEAR( posts.post_date ) = 2018 AND MONTH( posts.post_date ) = 12 AND HOUR( posts.post_date ) = 10 ) OR YEAR( posts.post_modified ) BETWEEN 2018 AND 2013 ) AND ( term_relationships.term_taxonomy_id IN (1,2,3,4,5,6,7) AND posts.ID NOT IN ( SELECT object_id FROM term_relationships WHERE term_taxonomy_id IN (9,19) ) ) AND (((posts.post_title LIKE '%red%') OR (posts.post_excerpt LIKE '%red%') OR (posts.post_content LIKE '%red%'))) AND posts.post_type = 'post' AND ((posts.post_status = 'publish' OR posts.post_status = 'private')) GROUP BY posts.ID Here, we get everything feared by SQL admins: - Table joins - Functions in where condition - Full-text search - Results aggregation In severe conditions, it can only lead to server resource exhaustion and search downtime. Bring the simplicity of Toolset Views to WPSOLR With WPSOLR alone, queries are incredibly fast and scalable. Including dynamic facets to help filtering results with custom fields or product attributes. And of course, with WPSOLR's hooks, you can develop more complicated queries to suit your needs. But the hooks require quite a heck of a knowledge about Elasticsearch and Solr. Therefore, until now, there was no easy way to build custom queries without an expertise search engine knowledge. Unlike the Toolset Views Query Builder. Below is an example of the complexity of Elasticsearch queries. This simplified one was generated automatically from the Toolset Views Query Builders b) example from the previous paragraph: And remember that this is a pretty simple query. But then, why is so different from the previous SQL query, in terms of performance? Well, the answer is "everything". Because Elasticsearch was built to handle such sophisticated queries, by using an inverted index. Inverted indexes are used like tables of contents in books. Instead of a page number as in books, they store, for each word, which document contains the word. This enables to retrieve instantaneously every post containing the word "red", without opening any post. And there are many ways, named analysers and filters, to customize the inverted index content to specific needs. Like for languages, stop words, synonyms, stemming, and so on. If you wish to see by yourself a full tutorial showing the setup of WPSOLR (since version 20.1), to speed up Toolset Archive Views: The step by step documentation is here. Plugins. 0. wpsolr. All Included Pack...

What is the toolset views add-on The toolset add-on makes it possible for the toolset plugin to work in tandem with WPSOLR. With the toolset plugin you can tailor WordPress to your individual needs. You can create custom post types, fields and taxonomies. You can create templates, archives, grids, tables and lists. Install the Toolset plugin Click on "Plugins" then on "Add New". Click on "Add plugins" then on "Upload Plugin". Add the toolset plugins. You will have to upload the toolset views and the toolset types plugins. Install the Query monitor plugin Click on "Add New". Install the Query monitor plugin. Create a WPSOLR index Click on the WPSOLR plugin. Click on "Connect to your search server or search service". Choose the Search engine and the hosting service. Then pick the WPSOLR index name. Lastly, fill in the endpoint url, user and password you got from the hosting service. Add the Toolset add-ons Click on "Activate extensions" to install the toolset add-ons. Click on "Toolset Types" in the sidebar. Click on the first checkbox to activate the add-on. If you select the second checkbox, you will replace WPSOLR facets label with Toolset Types label. Click on Toolset Views next. Click on the first checkbox to activate the plugin and replace the Toolset archives and views queries with WPSOLR queries. The second checkbox allows you to use Toolset Views caching but you don't need it since WPSOLR already speeds up your search. If you want to have more options when customizing search filters, you will need to activate the Theme add-on. For example you will not be able to use a slider without the Theme add-on. Click on the first checkbox to activate the extension then save. Click on "Query Monitor" in the sidebar. Then click on the checkbox to activate the add-on. Configure WPSOLR Click on "Define your search with 'No index selected'". Click on "Search" then click on "Search with this search engine index" and select the index. Then save. Don't forget to log the search engine queries in Query monitor. Click on "Data" in the sidebar. Then on the content you would like to use. Here i chose products. Choose the taxonomies you would like to use. Then choose fields you would like to use. if you want to use a slider for example, you will have to change the type of the field. For the price field i chose to use floating point numbers and integer numbers for the stock field. When you've saved the changes, click on "Filter" in the sidebar. Then click on the facets you would like to use as filters. Then save You can then customize the filters. Choose a name for the filter. It will be shown on the front end. Then pick a layout. I decided to use the range slider. You can pick a skin to use with the slider as well. Do the same thing for the stock filter. For the stock status i used check boxes but I changed the title of the item label. To change it, click on "Override each item label" then choose the title you want. Index the content Click on "Send your data". Then click on "Index selected post types". Install the WPSOLR facet widget Click on "Customize" in the frontend part of your website. Click on "Widgets". Then click on "Sidebar". And click on "Add a widget". Type in "WPSOLR Facets" then publish. Create Toolset archive Hover your mouse over "Toolset" in WordPress admin, then click on "WordPress Archives". Click on "Add New". You will then see this page. Choose the loop the archive will be used for then choose what kind of archive you want. I chose one with custom search. Then name the WordPress Archive. You should see this page. You can further customize the archive if you want but i chose to leave the defaults. Then if you scroll down you should see these to images. In the first image we can see that the layout is started and the items are fetched. The number of items counted are displayed next to the phrase "Item count:" and the number of items found are displayed next to the phrase "Items found:". The page number is displayed next to the word "Page:" and the total number of pages is displayed next to "Total pages". The loop starts and a table is created. In the table is stored the wpsolt title (in this case the product title) and the wpsolr excerpt (product excerpt and featured image). We then define for how many products this process will be repeated and the loop ends. the wpv-items from before are displayed. if none are found, then the message "No items found" is displayed. You can also write some CSS. Here the nav links are displayed inline and the pagination is not displayed. Here the products link are displayed, as well as the excerpt and the product category. Test website search Here is how the websites search looks like without the toolset plugins. Here is how it looks like with the toolset plugins activated. Of course further customization is possible if you want fine tune the appearance of the results. If you want to see the differences, here is some information about the query when Toolset is deactivated. This is the information we see when WPSOLR is deactivated. If you need additional explanations you can watch this video: https://www.youtube.com/watch?v=j8NUf6vAxvo&t=246s WPSOLR - User guide...