Welcome to the Elastic Search Ultimate Guide!

Here you will find everything you need to set up a better search experience.

First, please find your extension in your account in My Downloadable Products section. Then, start with Installation and Quick Start option. It is best to follow our step-by-step guide in order to configure the best search results.

Go ahead, dive in!

Learn about the initial setup:

Installation

In this article you will find two possible ways of our extension's installation.

Installation via composer (preferably)

We recommend this installation method because Composer doesn't allow to overwrite files.

  1. Backup your store's database and web directory.
  2. Login to the SSH console of your server and navigate to the root directory of the Magento 2 store.
  3. Copy the installation instructions from the page My Downloadable Products / View & Download to the SSH console.
  4. Run command php -f bin/magento module:enable Mirasvit_Core Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchElastic Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_Report Mirasvit_SearchReport to enable the extension.
  5. Run command php -f bin/magento setup:upgrade to install the extension.
  6. Run command php -f bin/magento cache:clean to clean the cache.
  7. Deploy static view files
    rm -rf pub/static/*
    rm -rf var/view_preprocessed/*
    php -f bin/magento setup:static-content:deploy

  8. Run search spell-correction reindex php -f bin/magento indexer:reindex mst_misspell
  9. Go to System / Search Indexes, configure Product index and run the reindex for it.

Installation via direct file upload

You can also install the extension via direct files uploading.

  1. Go to My Downloadable Products / View & Download
  2. Unpack .zip package and copy contents to magento root directory
  3. Run command composer require elasticsearch/elasticsearch:~5.1 to install required libraries.
  4. Run command php -f bin/magento module:enable Mirasvit_Core Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchElastic Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_Report Mirasvit_SearchReport to enable the extension.
  5. Run command php -f bin/magento setup:upgrade to install the extension.
  6. Run command php -f bin/magento cache:clean to clean the cache.
  7. Deploy static view files
    rm -rf pub/static/*
    rm -rf var/view_preprocessed/*
    php -f bin/magento setup:static-content:deploy

  8. Run search spell-correction reindex php -f bin/magento indexer:reindex mst_misspell
  9. Go to System / Search Indexes, configure Product index and run the reindex for it.

Learn about the initial setup:

Quick Start

As you've successfully completed installation of Elastic Search Ultimate, we will guide you through the main steps required to start efficiently using our extension.

  1. Make the content of your store searchable by configuring different Search Indexes.

    • Go to System / Search / Manage Indexes
    • Enable or add new indexes that you want to be searchable
    • After that please reindex search indexes by running the command php -f bin/magento indexer:reindex catalogsearch_fulltext
  2. Configure Global Search Options and Additional Search Options
  3. Display search results the way you want it with the Autocomplete option!

    • Open Search Autocomplete configuration in System / Search Management / Settings / Search Autocomplete.
    • Enable required indexes and set proper results limit.
  4. Enable Search Spell Correction

    Please reindex spell correction by running the command php -f bin/magento indexer:reindex mst_misspell

Please follow our guide step by step to get the best search result!

Core Search Settings

Here you can quickly navigate across all functionality settings we have. Please use the list below to navigate.

This section covers all topics, necessary for working with indices, and consists of the following subsections:

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Configure Search Indexes

Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.

This section covers all topics, necessary for working with indexes, and consists of the following subsections:

Managing Indexes

Our extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.

Each index, added to this grid, displayes the following properties:

  • Title - title of the search index.
  • Type - shows index type (searchable content type - read more at Adding New Index subsection).
  • Position - the position of the index in the search results. Search results will be organized in tabs according to this property.
  • Status - indicates, whether current index is ready for search. Disabled value means, that index will be excluded from search.

Additional Action column provides common actions, that can be performed directly from grid, such as:

  • Edit - edit index settings (default action).
  • Reindex - run manual reindexing for selected index.
  • Delete - remove index from Mirasvit Search extension. %

    Note

    This action will completely remove this index from your store, so if you wish index to be excluded from search - just change its status to Disable.

Back to top

Adding and Configuring New Index

  1. To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.

  2. Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:

    • Title - title of the search index. It will be used as tab header at search display page.
    • Type - shows index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
    • Position - the position of the index in the search results. Extension will sort tabs on search results page based on position.
    • Active - sets, whether index should be activated.
  3. Press Save and Continue Edit to proceed to index configuration stage.

  4. Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes, where extension should conduct search. Each row consist of the following fields:
    • Attribute - attribute name. It is picked from properties of selected index type. For example, if Product type is selected - then attributes would be Product Name, SKU, Price, Tax Class and so on.
    • Weight - sort order, which defines importance of each attribute for product relevancy. The maximum weight is 10 (highest priority), the minimum weight is 0(lowest priority). Each index type comes with a predefined set of searchable options, that will be displayed after completing the first stage. There should be at least one searchable attribute, otherwise search will not work properly.
  5. Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.

  6. Save index and activate it to include to search.

On installation three indexes will be automatically created and configured: Product, Category and CMS Page.

Back to top

Product Index

Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Specific options of this type will be shown on Properies section of Index edit page:

  • Search by Parent Category Name - include to search all parent categories (useful, when store has wide categories tree).
  • Search by child products - include to search associated products from Bundled and Grouped products.
  • Search by Product ID - enable search by product id (entity_id attribute, which is not listed as searchable by Magento).
  • Search by custom options - enable search by custom options (defined additionally to existing ones).
  • Push "out of stock" products to the end - force sorting of search results by stocks inventory, so 'out of stocks' products will be displayed last.
  • Search only by active categories - display only products, which are assigned to at least one active category
  • Force sort order by - overrides default sort order of search results by one of these options:
    • Relevance - sorting by maximum relevance with search request
    • Name - sorting by names in alphanumeric order.
    • Creation Time - sorting by date of adding products to store
    • Price 0-9 - sorting from cheapest to most expensive.
    • Price 9-0 - sorting from expensive to cheapest.

Back to top

Category Index

Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's no specific options for this type of index.

Back to top

CMS Index

CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

There's only one specific option for this type on Properies section of Index edit page:

  • Ignored CMS Pages - defines, on which CMS pages search should not be performed. You can select zero or more pages here via checkbox drop-down list.

Back to top

Attribute Index

Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.

This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.

Note

Attribute index can work only with attributes, that can be indexed, e. q. they belong to selectable type.

To see type of Product Attribute, visit Stores -> Attributes -> Product grid, pick up attribute record, and see Catalog Input Type for Store Owner field. Selectable types are Multiple Select and Dropdown. Only attributes of this type can be indexed.

If you wish to use attributes like Author, or similar, you have to make them selectable first, and then make them available for search as above.

After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

Back to top

Wordpress Blog Search Index

Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.

  • Database Connection Name - connection name of the wordpress database.

    • If WordPress is installed on the same database, the correct value is default.
    • If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.

      Example

      Typical database connection should look similar to this:

          'db' => array(
          'table_prefix' => '',
          'connection' => array(
              'default' => array(
                  'host' => 'localhost',
                  'dbname' => 'store',
                  'username' => 'root',
                  'password' => 'password',
                  'active' => '1',
              ),
          ),
         ),

  • Table Prefix - the prefix for the wordpress tables (wp_ by default).
  • Url Template - the full URL for your posts with dynamical variables.

    Typical base urls should look like example below below:

    http://example.com/blog/{post_name}.html
    http://example.com/blog/?p={ID}
    http://example.com/{category_slug}/{post_name}.html

Back to top

Implementing Custom Search Index

Sometimes it's need to have specific type of Index, which is either not included to our extension, or belongs to some third-party extension. In this case custom index can be implemented, using the following instructions:

  1. Clone the example module from repository http://github.com/mirasvit/module-search-extended
  2. Go to app/code/Mirasvit/SearchExtended/Index/ and rename subpath Magento/Review/Review/ to the required one ([provider]/[module]/[entity])
  3. Change class names in file app/code/Mirasvit/SearchExtended/Index/[provider]/[module]/[entity]/Index.php
    • Rename class
    • Set your values to getName(), getPrimaryKey() and getIdentifier() methods
  4. Configure the attributes you want to get in getAttributes() method
  5. Change methods buildSearchCollection() and getSearchableEntities()
  6. Change registration for new index in file app/code/Mirasvit/SearchExtended/etc/di.xml
  7. Adjust layout file app/code/Mirasvit/SearchExtended/view/frontend/layout/catalogsearch_result_index.xml

    Rename template name/path and adjust it /app/code/Mirasvit/SearchExtended/view/frontend/templates/index/magento/review/review.phtml

  8. Enable module and Clear magento cache

If everything was correct, you can add index of your custom type like any regular index.

  1. If you use SSU please go to: /vendor/mirasvit/module-search-autocomplete/src/SearchAutocomplete/Model/Index folder
  2. Create folder/file structure <Company>/<Extension>/<EntityType>.php i.e. /vendor/mirasvit/module-search-autocomplete/src/SearchAutocomplete/Model/Index/Ves/Blog/Post.php
  3. Open /vendor/mirasvit/module-search-autocomplete/src/SearchAutocomplete/etc/di.xml and add item to type name="Mirasvit\SearchAutocomplete\Model\Index\Pool" arguments

Configure Global Search Settings

This section describes, how you can customize and greatly improve the relevance of your search results by configuring Search Settings.

The most important part is Global Search Configuration. It is located at System -> Search Management -> Settings -> Mirasvit Extensions -> Search, and divided into the following sections:

search_engine.png

Search Engine Configuration

Our extension allows you to power up search either with default Magento search engine, or with Sphinx External Engine. Option Search Engine selects, which one should work now:

  • MySQL - the native magento engine.
  • Built-in search engine - will use an internal search algorithm of our extension.

    Note

    Built-in search engine mode does not require installation of Sphinx Engine on your server, but you will still receive the same features as with the Sphinx Engine. However, you can experience a slower search speed than with the Sphinx Engine (only for more then 20K products).
  • External Sphinx engine - allows to use Sphinx Engine on the dedicated server, or on the same server of your store.

    Note

    To start with, please, make sure that you have installed Sphinx Search Engine. To do this please follow our installation guide .
    external_common.png External Sphinx engine triggers additional options for configuring and managing Sphinx Daemon:

    • Sphinx Host - sphinx daemon host (localhost by default).
    • Sphinx Port - sphinx daemon port (any free port, like 9811, 9812).
    • Sphinx installed on same server - triggers appearance of additional features of Sphinx Daemon. Can have two different modes:

    For Sphinx installed on the same server with your Magento store : external_local_engine.png

    • Yes - defines, that Sphinx works on the same server, as store and database. Triggers the following additional options and additional buttons, which allows to manage daemon:
      • Sphinx Bin Path - defines name and location of sphinx daemon. By default it's searchd.
      • Allow auto-start Sphinx Daemon - sets auto-starting daemon with Magento's store. Useful, when you can have unexpected server power-off (for example, for maintenance purpose).
      • Check Status - button, that allows to view current daemon status
      • Restart Sphinx Daemon - button, that allows to restart daemon directly from Magento Configuration pane.
      • Reset - button, that allows reset daemon current search task.

    For Sphinx installed on the dedicated (remote) server : external_engine.png

    • No - defines, that Sphinx works on separate or dedicated server.
      • Generate configuration file - button, that allows to generate Sphinx config file to copy to your remote (dedicated) server.

    Note

    If you already installed Sphinx Search engine please learn more about connection with Sphinx Engine.

    Search Engine Configuration section contains Additional Configuration subsection, visible for External Sphinx engine only. It allows you to tune up Sphinx configuration file, and contains the following settings: external_additional.png

    • Custom Base Path - defines custom path to Sphinx, if it was installed not to the default [magento_root_directory]/var/sphinx/ location.
    • Additional searchd configuration - defines additional parameters to searchd Search Daemon. Read more about it here.
    • Additional index configuration - allows to add settings to the Sphinx index configuration. Read more about it here.
    • Custom Charset Table - allows to add character sets to the Sphinx configuration file. Read more about it here.

Back to Top

Search Settings

wildcard_options.png

  • Wildcard search - allows customer to search the product by part of the word, marking unknown part with asterisk (*). There's four different wildcard modes available:
    • Enabled (*word*) - fully enables wildcards.
    • Enabled at end (*word*) - partially enables wildcards, allowing to search by first part of keyword.
    • Enabled at start (*word*) - partially enables wildcards, allowing to search by last part of keyword.
    • Disabled - totally disables wildcards.

      Note

      Wildcards enabling slightly reduces the relevance of search and increases the number of search results.
  • Enable redirect from 404 to search results - if option is enabled, customer will be redirected to the store search results of the broken URL text instead of the "404 Not Found" page.
  • Redirect if there is a Single Result - if the search query results only have one match, the customer will be immediately taken to to corrresponding product page.
  • Enable Google Sitelinks Search - if option is enabled, the extension shows the Sitelink Search Box on the Google search results page. After enabling the option, the search box will be shown only after Google reindexing.
  • Enable search terms highlighting - if option is enabled, search query word(s) will be highlighted in the search results.
  • Display Related Search Terms - if option is enabled, related search terms will be displayed on the search result page.
  • Max number of items in the result - sets the maximum number of items in the search result. Set 0 to disable limitation.
  • Wildcard Exceptions - the list of keywords (characters) for which wildcard search can not apply.
  • Replace words in search query - two-column list of auto-replace. When evaluating search extension will seek keywords from Find word columns, and automatically replace with the one from Replace With column. Column Find word can contain more than one keyword, separated by comma.
  • Not' words - words from this list invert search. E. q. appearance of these words in search automatically treated as "exclude results with this word".
  • Long Tail Expressions - allows you to receive the correct search results for words that contain dashes or any other non-alphabetic symbols. Read more in Long Tail Configuration section.
  • Minimum number of characters - to search-specifies the minimum amount of characters, which triggers autocomplete drop-down list. It works only when Autocomplete is installed and enabled.
  • Match mode - overrides default Magento mode of search with one of the following options:
    • AND - this mode is default. Elements (e. q. products, pages) matched only when all requested keywords are found in respective attributes.
    • OR - defines, that elements matched only when at least one of requested keywords is found.

Back to Top

Multi-store Search Result

You need multi-store search, when you have store-dependant elements - for example, products, that are visible only at specific storeviews - but wish to allows customers to search simultaneously on all your stores.

  • Enable Multi-Store Search Results - enables multi-store search. Search results will be displayes in tabs, each of which corresponds with one of your storeviews. This option triggers one additional option:
    • Stores - allows you to select, which storeviews should be included to multi-store search.

Back to Top

Configure "Long-Tail" Search

This section describes the Long-Tail Search feature, that will allow you to have correct search results for words that contain dashes or other non-alphabetic symbols. You can also replace on-the fly the most typical errors customers can make in complex product names.

What is Long-Tail Search?

For example, we have a product Canon PowerShot SX500 IS. But customer can request Canon PowerShot SX-500IS, which default search will not find, because it differs from actual product label.

It's because Magento by default during reindex uses only correct product labels from database, and thus, index will contain only them - making products with complex names "ineligible" for search.

This is where "Long-tail" search come. During reindex and search this feature recognizes the keywords rather by pattern and replaces it either to the empty or some other characters, "correcting" customer's request on-the fly.

In example above the SX500 IS can be converted to the SX500IS and during the search, the SX-500IS also be converted to the SX500IS by replacing '-' symbol to empty char.

This way search will be able to find products by several combinations of spelling the product's name.

Back to Top

Configuring Long-Tail Search

Go to System / Search Management / Settings / Mirasvit Extensions / Search
In the section Search Settings go to the option Long tail.
There you can set up regular expressions to receive required search results.

  • Match Expression - the regular expression(s) that parses words for further replacing.

    Parsing goes for search index, during an indexing process, and goes for search phrases during search. E.g. /([a-zA-Z0-9]*[\-\/][a-zA-Z0-9]*[\-\/]*[a-zA-Z0-9]*)/

  • Replace Expression - the regular expression(s) to parse characters to be replaced. Parsing goes in the results of "Match Expression". E.g. /[\-\/]/
  • Replace Char - the character to replace values founded by "Replace Expression". E.g. empty value.

Back to Top

Configuring Long-Tail Search

Here is some of most useful cases of long-tail search, implemented as corresponding rules.

  • Automatically remove '-' symbol from product names

    Create a rule with the following parameters:

    • Match Expression - /[a-zA-Z0-9]*-[a-zA-Z0-9]*/
      Matched text: SX500-123, GLX-11A, GLZX-VXV, GLZ/123, GLZV 123, CNC-PWR1
    • Replace Expression -/-/
    • Replace Char - empty
      Result text: SX500123, GLX11A, GLZXVXV, GLZ/123, GLZV-123-123, CNCPWR1
  • Automatically remove '-' and '/' symbols from product names

    Create a rule with the following parameters:

    • Match Expression - /[a-zA-Z0-9]*[ \-\/][a-zA-Z0-9]*/
      Matched text: SX500-123, GLX-11A, GLZX-VXV, GLZ/123, GLZV 123, CNC-PWR1
    • Replace Expression - /[ \-\/]/
    • Replace Char - empty
      Result text: SX500123, GLX11A, GLZXVXV, GLZ123, GLZV123, CNCPWR1
  • Automatically make solid all products names with separators

    Create a rule with the following parameters:

    • Match Expression - /[a-zA-Z0-9]*[-\/][a-zA-Z0-9]*([-\/][a-zA-Z0-9]*)?/
      Matched text: SX500-123, GLX-11A, GLZX-VXV, GLZ/123, GLZV-123-123, CNC-PWR1
    • Replace Expression - /[-\/]/
    • Replace Char - empty
      Result text: SX500123, GLX11A, GLZXVXV, GLZ123, GLZV123123, CNCPWR1
  • Automatically fix misspelled product's name

    Create a rule with the following parameters:

    • Match Expression - /([a-zA-Z0-9]*[\- ][a-zA-Z0-9]*[\-][a-zA-Z0-9]*)/
      Matched text: VHC68B-80, VHC-68B-80, VHC68B80
    • Replace Expression - /[\- ]/
    • Replace Char - empty
      Result text: VHC68B80

Back to Top

Moving Long-Tail Expressions from M1 to M2

Long-Tail expressions, which are used in Search Sphinx for M1 and M2 sliightly differ.

In M1 Search Sphinx you can enter one or more expressions to match, separated by '|' character. In M2 you can not.

Consider the following expression for Search Sphinx for M1:

Example

Match Expression: /[a-zA-Z0-9][ -/][a-zA-Z0-9]([ -/][a-zA-Z0-9]*)?/|/[a-zA-Z]{1,3}[0-9]{1,3}/
Replace Expression:/[ -/]/|/([a-zA-Z]{1,3})([0-9]{1,3})/
Replace Char:$1 $2

It actually contains two separate regexps to match: /[a-zA-Z0-9][ -/][a-zA-Z0-9]([ -/][a-zA-Z0-9]*)?/ and /[a-zA-Z]{1,3}[0-9]{1,3}/ with respective separate expressions for replace.

You need either to reformat that expression, so it will match in single expression, or rewrite this rule as a set of two:

  • First rule

    This rule will implement the first part of original M1 expression.

    • Match Expression: /[a-zA-Z0-9][ -/][a-zA-Z0-9]([ -/][a-zA-Z0-9]*)?/
    • Replace Expression:/[ -/]/
    • Replace Char:$1 $2
  • Second rule

    This rule will implement the second part of original M1 expression.

    • Match Expression: /[a-zA-Z]{1,3}[0-9]{1,3}/
    • Replace Expression:/([a-zA-Z]{1,3})([0-9]{1,3})/
    • Replace Char:$1 $2

Back to Top

Manage Landing Pages

Landing search page is special search result page, with a static URL, where customers are redirected on using some search expression.

Let us have a large number of frequently asked (or just a promotional set) models of Samsung phones with black coat. So we create a separate promotional page, say, http://store.com/black-samsung-phone.html, and bind it to the search phrase "black samsung phone". Then, when customer will request a black Samsung phone, it will be immediately sent to your special page.

Also it supports the following logic .We create a separate promotional page, say, http://store.com/black-samsung-phone.html, and bind it to the search phrase "black samsung phone". When customer will go to this (specific) URL search results for "black samsung phone" will be immediately built on it.

All such a pages can be managed from System -> Search Management -> Manage Landing Pages grid.

Adding New Landing Page

  • Go to System / Search Management / Manage Landing Pages and press Add New button.
  • On creation page fill the following fieds:
    • Query Text - the key phrase, which should bring customer to landing page (ex. black samsung phone)
    • URL Key - relative path to landing page. For example, if URL key is shoes/all, then full URL would be https://example/shoes/all/.
    • Active - activates or deactivated redirect to landing page.
    • Page Title - overrides title of that page with yours.
    • Meta Keywords - meta keywords, that can be used by search crawlers.
    • Meta Description - meta description, that can be used by search crawlers.
    • Layout Update XML - overrides XML layout of landing page.
  • Save and activate landing page.

Manage Synonyms

Synonyms are keywords with the same or similar meaning. All of them are located at System -> Search Management -> Manage Synonyms section.

You can either manually add synonyms, or import them from YAML-formatted file.

Adding New Synonym

  • Go to System -> Search Management -> Manage Synonyms grid and press Add New Synonym button.
  • On creation page, fill the following fields:

    • Term - is the base keyword, to which synonyms will be replaced.
    • Synonyms - comma-separated list of synonyms. It should contain at least one keyword. Each of them should match the following requirements:

      1. It should consist of one word, and only of alphanumeric characters (e. q. without spaces, dashes, slashes and so on).
      2. It should have length, greater than 1 character.

      3. Max length of synonyms list equals 255 symbols.
    • Store View - allows to select, where defined synonyms will be applied.
  • Save record.

Importing Synonyms

Our extension uses YAML file format for synonyms importing. It should resemble the following format:

    -
      term: [TERM_1]
      synonyms: [SYN_1]
    -
      term: [TERM_2]
      synonyms: [SYN_2]

Name of this file should be equal to your language code in capital case. Codes can be found here, use column 639-1 for that.

Example

Let's create a synonyms file for English locale. Name of such a file would be EN.yaml, and it's content should be:

    -
      term: abiogenesis
      synonyms: autogenesis,autogeny,spontaneous generation
    -
      term: abject
      synonyms: low,miserable,scummy,scurvy,resigned,unhopeful
    -
      term: abjection
      synonyms: abasement,degradation
    -
      term: abjectly
      synonyms: resignedly

To import synonyms, perform the following steps:

  • Place your custom YAML file to the special folder [magento_root]/var/sphinx/synonyms/
  • Go to System -> Search Management -> Manage Synonyms and press Import Synonyms button.
  • Dictionary field defines locale (language), to which synonyms are imported. All dictionaries should exist, and have at least one record, since imported data are appended to existing.
  • Store View defines storeviews, where imported synonyms will be applied.
  • Press Import to import and apply synonyms.

Manage Stopwords

Stopwords are words that have little lexical meaning or ambiguous meaning and are not useful during the search (ex. and, or, the, a, with, etc). Therefore, these words should be removed from search phrases to make them relevant.

You can either manually add stopwords, or import them from YAML-formatted file.

Adding New Stopword

  • Go to System -> Search Management -> Manage Stopwords grid and press Add New Stopword button.
  • On creation page, fill the following fields:
    • Stopword - is the keyword, which should be removed from search requests.
    • Store View - allows to select, where defined synonyms will be applied.
  • Save record.

Importing Stopwords

Our extension uses YAML file format for stopwords importing. It should resemble the following format:

    {[ID_1]:[Stopword_1],[ID_2]:[Stopword_2],[ID_3]:[Stopword_3]}

Name of this file should be equal to your language code in capital case. Codes can be found here, use column 639-1 for that.

Example

Let's create a stopwords file for English locale. Name of such a file would be EN.yaml, and it's content should be:

    {1:"but",2:"now",3:"what",4:"except"}

To import stopwords from such a file, perform the following steps:

  • Place your custom YAML file to the special folder [magento_root]/var/sphinx/stopwords/
  • Go to System -> Search Management -> Manage Stopwords and press Import Stopwords button.
  • Dictionary field defines locale (language), for which stopwords are imported. It is picked from the name of your YAML import files.
  • Store View defines storeview, where imported stopwords should be applied.
  • Press Import to import and apply stopwords.

Customize Search Weight

Our extension arranges relevance of found products using Global Settings. But sometimes (for example, for promotional purposes) you need to forcibly move one or more specific products to the top, or vice versa, to the bottom of search results.

It can be done via special option Search Weight, added by our extension to the general settings of the Product Edit Pages.

create_product.png

This weight is the relative position, where product will be placed on search result page. It ranges from 100 (product or category will always appear at the top of search results list) to -100 (product or category will always appear at the bottom of search results list).

Installing Elastic Search Engine

If you would like to use our extension with Elasticsearch Engine, you should install it first.

Elastic Search should be installed differently in different platforms. If you use UNIX or Linux-based system, you can use one of the following commands:

  • cat /etc/*-release
  • cat /proc/version
  • hostnamectl

Note

Important Note: Elastic Search requires Java, so make sure openJDK or Oracle JDK is installed before proceed.

Depending on your platform, displayed by command above, you need to pick up one of the following procedures:

If you have unusual configuration, or use non-Linux setup, please, refer to official user manual how to install the elastic engine in such case.

After installation is complete, refer to How to check and manage Elastic Search Service subsection.

Ubuntu and other Debian-enabled OS

If you have installed Ubuntu, or other system with Debian package manager, execute the following commands:

  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.deb
  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.deb.sha512
  • shasum -a 512 -c elasticsearch-6.2.2.deb.sha512
  • sudo dpkg -i elasticsearch-6.2.2.deb
  • sudo update-rc.d elasticsearch defaults 95 10
  • sudo -i service elasticsearch start

CentOS and other RPM-enabled OS

If you have installed CentOS, or other system with RPM package manager, execute the following commands:

  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.1.1.rpm
  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.1.1.rpm.sha512
  • shasum -a 512 -c elasticsearch-6.1.1.rpm.sha512
  • sudo rpm --install elasticsearch-6.1.1.rpm
  • sudo chkconfig --add elasticsearch
  • sudo -i service elasticsearch start

Install from gzip package

If you have Linux-based system, but not from above distributions, or you just wish to make it run on-demand, use the following commands:

  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.tar.gz
  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.tar.gz.sha512
  • shasum -a 512 -c elasticsearch-6.2.2.tar.gz.sha512
  • tar -xzf elasticsearch-6.2.2.tar.gz
  • cd elasticsearch-6.2.2/
  • ./bin/elasticsearch

How to check and manage Elastic Search Service

Once you had installed Elastic Search using one of above procedures, you need to check, whether it actually installed and running. Use this command to get current status:

  • sudo -i service elasticsearch status

Output should return: elasticsearch is running

You can also visit Stores -> Configuration -> Mirasvit Extensions -> Search -> Search Engine Configuration, then select Elasticsearch Engine at Search Engine option.

You will see a Check status button on displayed subpanel. If Elastic Search is properly installed, you will receive output like below:

Example

Elasticsearch is running.

name: nyYUXv5
cluster_name: elasticsearch
cluster_uuid: EFGeuFOBSP64M9q0N8ST2Q
version:
     number: 6.2.2
     build_hash: 10b1edd
     build_date: 2018-02-16T19:01:30.685723Z
     build_snapshot:
     lucene_version: 7.2.1
     minimum_wire_compatibility_version: 5.6.0
     minimum_index_compatibility_version: 5.0.0
tagline: You Know, for Search
_shards:
     total: 0
     successful: 0
     failed: 0
_all:
     primaries:
     total:
indices:
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","index":"*"}],"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","index":"*"},"status":404}

You can also send a request to your store's Elastic Search Port (see Connecting Elastic Search Engine). By default it is 9200. If Elastic Search is properly installed, you will receive the following output:

Example

URL: http://store.com:9200/

{
  "name" : "nyYUXv5",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "EFGeuFOBSP64M9q0N8ST2Q",
  "version" : {
    "number" : "6.2.2",
    "build_hash" : "10b1edd",
    "build_date" : "2018-02-16T19:01:30.685723Z",
    "build_snapshot" : false,
    "lucene_version" : "7.2.1",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

If at least one of the tests above passed with correct output, you had successfully installed Elastic Search Engine on your store.

If you need to manually restart Elastic Search, use command sudo -i service elasticsearch restart.

If you need to manually stop Elastic Search, use command sudo -i service elasticsearch stop.

Connecting Elasticsearch Engine

Make sure, that you had installed Elastic Search prior to configuring it.

Note

Supported Elastic Search Engine versions are 5.2.+, 5.5.+ or 6.0.+.

If you had installed it, and checked, whether it is running, visit System -> Search Management -> Settings subsection.

  1. Set Elastic Search Engine in option Search Engine, and subpanel with connection settings will appear:

    • Elasticsearch Host - Elastic Search host (localhost, or 127.0.0.1 by default).
    • Elasticsearch Port - Elastic Search Query port (9200 by default).
    • Elasticsearch Index Prefix - prefix for store index. Should be changed if you have multiple magento installations on server, each with respective prefix.
  2. Check correctness of configuration by pressing Check Status button. It should return output, as described in How to check and manage Elastic Search Service subsection.

  3. If parameters are incorrect, use Reset button to return to defaults.

  4. Save configuration, if you sure, that configuration is fine.

Note

After configuration saving, you need to run reindex:

  • At System -> Search Management -> Search Indices or
  • Using CLI interface with a command php bin/magento indexer:reindex catalogsearch_fulltext from your store's root directory.

Installing Elastic Search Engine

If you would like to use our extension with Elasticsearch Engine, you should install it first.

Elastic Search should be installed differently in different platforms. If you use UNIX or Linux-based system, you can use one of the following commands:

  • cat /etc/*-release
  • cat /proc/version
  • hostnamectl

Note

Important Note: Elastic Search requires Java, so make sure openJDK or Oracle JDK is installed before proceed.

Depending on your platform, displayed by command above, you need to pick up one of the following procedures:

If you have unusual configuration, or use non-Linux setup, please, refer to official user manual how to install the elastic engine in such case.

After installation is complete, refer to How to check and manage Elastic Search Service subsection.

Ubuntu and other Debian-enabled OS

If you have installed Ubuntu, or other system with Debian package manager, execute the following commands:

  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.deb
  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.deb.sha512
  • shasum -a 512 -c elasticsearch-6.2.2.deb.sha512
  • sudo dpkg -i elasticsearch-6.2.2.deb
  • sudo update-rc.d elasticsearch defaults 95 10
  • sudo -i service elasticsearch start

CentOS and other RPM-enabled OS

If you have installed CentOS, or other system with RPM package manager, execute the following commands:

  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.1.1.rpm
  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.1.1.rpm.sha512
  • shasum -a 512 -c elasticsearch-6.1.1.rpm.sha512
  • sudo rpm --install elasticsearch-6.1.1.rpm
  • sudo chkconfig --add elasticsearch
  • sudo -i service elasticsearch start

Install from gzip package

If you have Linux-based system, but not from above distributions, or you just wish to make it run on-demand, use the following commands:

  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.tar.gz
  • wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.2.tar.gz.sha512
  • shasum -a 512 -c elasticsearch-6.2.2.tar.gz.sha512
  • tar -xzf elasticsearch-6.2.2.tar.gz
  • cd elasticsearch-6.2.2/
  • ./bin/elasticsearch

How to check and manage Elastic Search Service

Once you had installed Elastic Search using one of above procedures, you need to check, whether it actually installed and running. Use this command to get current status:

  • sudo -i service elasticsearch status

Output should return: elasticsearch is running

You can also visit Stores -> Configuration -> Mirasvit Extensions -> Search -> Search Engine Configuration, then select Elasticsearch Engine at Search Engine option.

You will see a Check status button on displayed subpanel. If Elastic Search is properly installed, you will receive output like below:

Example

Elasticsearch is running.

name: nyYUXv5
cluster_name: elasticsearch
cluster_uuid: EFGeuFOBSP64M9q0N8ST2Q
version:
     number: 6.2.2
     build_hash: 10b1edd
     build_date: 2018-02-16T19:01:30.685723Z
     build_snapshot:
     lucene_version: 7.2.1
     minimum_wire_compatibility_version: 5.6.0
     minimum_index_compatibility_version: 5.0.0
tagline: You Know, for Search
_shards:
     total: 0
     successful: 0
     failed: 0
_all:
     primaries:
     total:
indices:
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","index":"*"}],"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","index":"*"},"status":404}

You can also send a request to your store's Elastic Search Port (see Connecting Elastic Search Engine). By default it is 9200. If Elastic Search is properly installed, you will receive the following output:

Example

URL: http://store.com:9200/

{
  "name" : "nyYUXv5",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "EFGeuFOBSP64M9q0N8ST2Q",
  "version" : {
    "number" : "6.2.2",
    "build_hash" : "10b1edd",
    "build_date" : "2018-02-16T19:01:30.685723Z",
    "build_snapshot" : false,
    "lucene_version" : "7.2.1",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

If at least one of the tests above passed with correct output, you had successfully installed Elastic Search Engine on your store.

If you need to manually restart Elastic Search, use command sudo -i service elasticsearch restart.

If you need to manually stop Elastic Search, use command sudo -i service elasticsearch stop.

Configuring Autocomplete & Suggest

All Autocomplete settings are located at System / Settings / Mirasvit Extensions / Search Autocomplete section.

It consists of the following sections:

General Configuration

This section also breaks into lesser subsections, and contains the following options:

  • General Configuration - defines basic application settings
    • Minimum number of characters to search - specifies the minimum amount of characters, which customer should enter to trigger autocomplete.
    • The delay to start finding - specifies delay between triggering autocomplete. (by option above) and beginning of actual search.

      Note

      Our extension actually begins to search for possible autocompletions and suggestions only when both conditions match:
      • customer had entered minimal required number of characters;
      • there were no actions during specified delay period.
  • Searchable content - list of search indexes, where search is performed, and results displayed as autocomplete options. Indices are either taken from standard Magento, or if extension is installed as part of Advanced Search Sphinx Pro or Sphinx Search Ultimate - from corresponding Indexes grid.
    • Index - name of index, which can be included to autocomplete.
    • Is Enabled - includes current index to autocomplete
    • Max Number of results - the maximum number of results, which should be displayed in autocomplete drop-down widget.

      Note

      You can drag and drop rows in this list to define order, in which results from different indices will be displayed in autocomplete drop-down.
  • Product Settings - defines content and appearance of autocomplete individual product information cells.
    • Show Price - displays price of product.
    • Show Thumbnail - displays small thumbnail of product image.
    • Show Rating - displays number of reviews and approval rating (so-called star rating).
    • Show Description - displays short excerpt from product's description.
    • Show SKU - displays SKU of the product.
    • Show "Add to cart" - displays shortcut button for quick purchasing products.
    • Optimize autocomplete view for small screen size - allows optimization of autocomplete layout to small screen sizes. Note: may require additional style fixing at Appearance section.
  • Appearance - contains only one field, which defines custom appearance of autocomplete widget.
    • Additional CSS Styles - custom CSS styles, that should be applied either to entire drop-down, or to individual product cells. It is extremely powerful tool, which allows you to fit our Autocomplete extension to almost any theme.

      Example

      To customize individual product cell in autocomplete drop-down, use the following expression:
      .searchautocomplete__item-magento_catalog_product
      {
          // Your extended styles
      }

      It will be added to our stylesheet.

  • Hot Searches

    Hot searches are the most popular queries, which were requested by customers. If current customer request includes such a query, autocomplete can highlight them and put to the top of drop-down.

    • Search queries - allows to override Hot Searches by adding here special keywords (comma-separated), that should be counted as hot. It is very useful during promotional campaigns.
    • Ignored words - allows to exclude from Hot Searches certain keywords. It is also a list of comma-separated words.
    • Max Number of queries - the maximum allowed number of Hot Searches, which should be displayed on autocomplete drop-down.

    FAQ

    This section describes the most common problems, that customers report, and how they can be resolved:

    How to make the autocomplete dropdown scrollable and smaller for mobile devices

    For this navigate to the Stores > Settings > Configuration > Mirasvit Extensions > Developer > CSS Settings and add the css styles below to the Additional CSS Styles field:

    @media screen and (max-width: 767px) {
        .searchautocomplete__autocomplete {
            max-height: 200px;
            overflow-y: scroll;
        }
    }

    max-width: 767px - is the maximum width of the device for which these styles are applied.

    How to make the autocomplete show a product price including or excluding tax

    For this navigate to the Stores > Settings > Configuration > Sales > Tax > Price Display Settings and switch the option Display Product Prices In Catalog to Excluding Tax - to display price without taxes or any other option to display price including tax.

    Configure Search Spell Correction

    All configuration options are located at Store -> Configuration -> Mirasvit Extensions -> Search Spell Correction section.

    There's only two options for now. In both our extension analyzes customer's request and tries to find product, whose names are most close to the original request.

    • Enable spell correction - enables automatic spelling correction.

      Example

      Let us assume, that your store have 'Samsung' products in catalog.

      When customer accidentally misspells Samsang phone, default Magento search will return nothing, since you have no such a product.

      But with this option enabled, customer will be notified about potential misspell and will see results for the corrected search phrase Samsung phone.

    • Enable fallback search - enables searching for partial request satisfaction, when there's no results for original request.

      Example

      Let us assume, that customer puts a phrase red samsung phone to the search, but you have only samsung phone product.

      If store has no such a product, default Magento search also will return nothing.

      But with this option enabled, customer will be notified about error, and and receive results by the correct search phrase samsung phone.

    Reports

    With detailed search reports, you are able to check how relative the search is to your customers.

    From this information you will be able to fine-tune your search configuration so that your customers will be led to the products they need.

    You can find reports in System / Search Management / Reports

    You can check the Search Report by:

    Search Volume

    • Total Searches / Popularity
    • Unique Searches - number of unique searches (search phrases)
    • Users - number of unique sessions with searches
    • Engagement % - the percent of users that opened product from search page

    You can group or filter it

    • By exact date
    • By hour
    • By day
    • By week
    • By month
    • By year

    Search Terms

    • Total Searches
    • Popularity
    • Engagement %

    Tip

    You can export Reports to CSV, Excel or XML formats

    Extension Upgrading

    To upgrade the extension follow these steps:

    1. Backup your store's database and web directory.
    2. Login to the SSH console of your server and navigate to the root directory of the Magento 2 store.
      If extension was installed via:
      • Composer: run command `composer update mirasvit/module-search-elastic-ultimate --update-with-dependencies to update current extension with all dependencies.

        Note

        In some cases the command above is not applicable, it's not possible to update just current module, or you just need to upgrade all Mirasvit modules in a bundle. In this case command above will have no effect.

        Run instead composer update mirasvit/* command. It will update all Mirasvit modules, installed on your store.

      • Direct file upload: download new extension package from our store and copy contents to root Magento directory
    3. Run command php -f bin/magento setup:upgrade to install updates.
    4. Deploy static view files rm -rf pub/static/*; rm -rf var/view_preprocessed/*; php -f bin/magento setup:static-content:deploy
    5. Run command php -f bin/magento cache:clean to clean the cache.

    Extension Disabling

    Temporarily Disable

    To temporarily disable the extension please follow these steps:

    1. Login to the SSH console of your server and navigate the to root directory of the Magento 2 store.
    2. Run the command php -f bin/magento module:disable Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchElastic Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_SearchReport to disabled the extension.

    Remove the Extension

    To uninstall the extension please follow these steps:

    1. Login to the SSH console of your server and navigate to the root directory of the Magento 2 store.
    2. Disable extension.
    3. Run command composer remove mirasvit/module-search-elastic-ultimate to remove the extension.

    Change Log

    Search Spell Correction [mirasvit/module-misspell]

    1.0.24

    (2018-05-31)

    Fixed

    • Issue with indexation cyrilic terms

    1.0.23

    (2018-04-11)

    Fixed

    • Issue with error 22003

    1.0.22

    (2017-12-25)

    Improvements

    • Integrated with Search Autocomplete
    • Added Reindex validator

    1.0.21

    (2017-12-13)

    Improvements

    • Fallback search logic

    1.0.20

    (2017-11-17)

    Fixed

    • Issue with _cl table

    1.0.19

    (2017-10-26)

    Fixed

    • Possible issue with null values during indexation

    1.0.18

    (2017-09-28)

    Fixed

    • Issue with calculation number of results for suggested search phrase

    1.0.17

    (2017-09-26)

    Fixed

    • M2.2
    • Issue with highlighting

    1.0.16

    (2017-08-09)

    Fixed

    • Issue with check zero result

    1.0.15

    (2017-07-12)

    Fixed

    • Issue with Changelog changes

    1.0.14

    (2017-07-10)

    Improvements

    • Fallback search logic

    1.0.13

    (2017-06-20)

    Fixed

    • Compatibility issue with Amasty Shopby

    1.0.12

    (2017-05-10)

    Improvements

    • Remove spell correction index if it disabled

    1.0.11

    (2017-04-11)

    Improvements

    • Switched to API interfaces

    1.0.10

    (2017-02-20)

    Improvements

    • Changed all string fuctions to mb_*

    1.0.9

    (2017-02-03)

    Improvements

    • Added Recurring setup script for check fulltext indices

    1.0.8

    (2016-11-21)

    Improvements

    • Compatibility with M 2.2.0

    1.0.7

    (2016-06-24)

    Fixed

    • Compatibility with Magento 2.1

    1.0.6

    (2016-06-16)

    Fixed

    • Fixed an issue with changing index mode for misspell index

    1.0.5

    (2016-04-27)

    Improvements

    • Improved extension performance
    • i18n

    Documentation

    • Updated installation steps

    1.0.4

    (2016-02-23)

    Fixed

    • Fixed an issue with segmentation fault during reindex (PHP7)

    1.0.3

    (2016-02-07)

    Documentation

    • Added user manual

    Search Autocomplete & Suggest [mirasvit/module-search-autocomplete]

    1.1.47

    (2018-07-06)

    Fixed

    • Conflict with Catalog Permission module on Magento EE edition

    1.1.46

    (2018-07-05)

    Improvements

    • MageFan Blog for Autocomplete

    1.1.45

    (2018-06-26)

    Fixed

    • Recent search span is not clickable
    • Product image is not clickable

    1.1.44

    (2018-06-21)

    Improvements

    • Changed visibility for mapProduct method

    1.1.43

    (2018-06-14)

    Fixed

    • Issue with reviews block

    1.1.42

    (2018-06-14)

    Improvements

    • Performance optimization of mapping (Fast Mode)

    1.1.41

    (2018-06-07)

    Improvements

    • ESU compatiblity + VES Blog

    Fixed

    • Issue with sorting results
    • issue with cached block initialization mirasvit/module-search-ultimate#62 (#19)
    • Product Settings in Autocomplete synced

    1.1.40

    (2018-03-09)

    Fixed

    • Issue with click on product

    1.1.39

    (2018-02-16)

    Features

    • add gift registry search index for autocomplete mirasvit/module-search#25

    1.1.38

    (2018-02-06)

    Improvements

    • Disabled native search/ajax/suggest

    1.1.37

    (2018-02-01)

    Fixed

    • Issue with special chars in CategoryProduct index

    1.1.36

    (2018-01-29)

    Improvements

    • Add to cart button

    1.1.35

    (2018-01-15)

    Fixed

    • Mageplaza blog

    1.1.34

    (2018-01-09)

    Fixed

    • Issue with attributes index

    1.1.33

    (2017-12-25)

    Improvements

    • Refactoring

    1.1.32

    (2017-12-18)

    Fixed

    • Fixed an issue with price formatter

    1.1.31

    (2017-12-13)

    Fixed

    • Fix in autocomplete price for configurable/group products

    Feature

    • Search results optimizer for mobile devices (small screen)
    • Added "search in categories" option to show categories sorted by most qty of matched products

    1.1.30

    (2017-12-11)

    Fixed

    • Issue with wrong link for hot searches terms

    1.1.29

    (2017-12-06)

    Fixed

    • Issue with bundled product price

    1.1.28

    (2017-11-29)

    Fixed

    • Issue with sort order

    1.1.27

    (2017-11-28)

    Fixed

    • Cache control
    • Code Formatting
    • Issue with size
    • Added currency to cache key
    • Issue with sorting

    1.1.26

    (2017-10-30)

    Fixed

    • Issue with right click

    1.1.25

    (2017-10-17)

    Fixed

    • Issue with cache key

    1.1.24

    (2017-09-28)

    Fixed

    • Updated default indexes configuration

    1.1.23

    (2017-09-27)

    Fixed

    • M2.2

    1.1.22

    (2017-09-13)

    Fixed

    • Issue with order by "score"

    1.1.21

    (2017-08-29)

    Improvements

    • Ability to filter by category

    1.1.20

    (2017-08-25)

    Fixed

    • Issue with cache

    1.1.19

    (2017-08-22)

    Fixed

    • Issue with Hot Searches

    1.1.18

    (2017-08-21)

    Fixed

    • Issue with wordpress

    1.1.17

    (2017-07-25)

    Fixed

    • Issue with "Attribute" index

    1.1.16

    (2017-06-23)

    Fixed

    • Issue with echo

    1.1.15

    (2017-06-22)

    Fixed

    • Issue with cache (after editing/removing products)

    1.1.14

    (2017-05-25)

    Improvements

    • Performance

    Fixed

    • Issue with image placeholder
    • Issue with calculation final price

    1.1.13

    (2017-05-12)

    Fixed

    • Issue with sorting queries

    1.1.12

    (2017-05-11)

    Improvements

    • Ability to set queries limit for "Hot Searches"

    Fixed

    • Possible issue with results sorting

    1.1.11

    (2017-05-03)

    Fixed

    • Issue with sku

    1.1.9

    (2017-05-02)

    Fixed

    • For landing pages

    1.1.8

    (2017-04-27)

    Fixed

    • Issue with mageplaza blog

    1.1.7

    (2017-04-26)

    Improvements

    • Mageplaza blog post

    1.1.6

    (2017-04-26)

    Improvements

    • Added sku

    Fixed

    • Issue with Mirasvit indices

    1.1.5

    (2017-04-26)

    Improvements

    • Mouse paste event

    1.1.4

    (2017-04-24)

    Fixed

    • Issue with DI
    • Product name is empty in search results

    1.1.3

    (2017-04-06)

    Fixed

    • Fixed an issue with disabled submit button after use hot / popular queries

    1.1.2

    (2017-04-05)

    Fixed

    • Fixed an issue with provider

    1.1.1

    (2017-04-04)

    Fixed

    • Fixed an issue with results

    1.0.48

    (2017-01-20)

    Improvements

    • Added new index for catalog attributes

    1.0.47

    (2017-01-15)

    Fixed

    • Fixed an issue with submit

    1.0.46

    (2017-01-12)

    Fixed

    • Fixed an issue with default search bar behaviour

    1.0.45

    (2016-12-23)

    Fixed

    • Fixed an issue witk key navigation
    • Fixed possible issue with product price (tax)
    • Fixed an issue with recent queries

    1.0.44

    (2016-12-08)

    Fixed

    • Fixed few possible JS issue with search results behaviour
    • Fixed an issue with selecting most popular search terms

    1.0.43

    (2016-11-21)

    Improvements

    • Compatibility with M 2.2.0

    1.0.42

    (2016-10-28)

    Fixed

    • Fixed an issue with "Hot searches"

    1.0.41

    (2016-10-25)

    Improvements

    • Added user agent to warmer

    1.0.40

    (2016-10-12)

    Fixed

    • Fixed an issue with hide search results

    1.0.39

    (2016-10-06)

    Fixed

    • Fixed an issue with autocomplete position

    1.0.38

    (2016-09-30)

    Fixed

    • Fixed an issue with minimum query length
    • Ability to translate index names

    1.0.36

    (2016-09-20)

    Fixed

    • Fixed an issue with translations

    1.0.34

    (2016-09-16)

    Fixed

    • Fixed an issue with reset cursor position after change query

    1.0.33

    (2016-08-30)

    Fixed

    • Fixed an issue with html markup (style tag)
    • Fixed an issue with popular suggestions

    1.0.32

    (2016-07-29)

    Fixed

    • Fixed an issue with cache special chars

    1.0.31

    (2016-07-28)

    Fixed

    • Fixed a possible issue with number of search results

    1.0.30

    (2016-07-07)

    Fixed

    • Fixed an issue with translations (M2.1)

    1.0.29

    (2016-06-29)

    Fixed

    • Fixed an issue with "Show all results" link

    1.0.28

    (2016-06-24)

    Fixed

    • Compatibility with Magento 2.1

    1.0.27

    (2016-06-22)

    Fixed

    • Fixed an issue with ajax loader

    1.0.26

    (2016-05-30)

    Fixed

    • Fixed an issue with catalog layer

    1.0.25

    (2016-05-26)

    Fixed

    • Fixed an issue with duplicating Popular suggestions (letter register)

    1.0.24

    (2016-05-20)

    Improvements

    • Image selection for products autocomplete
    • Ability to define ignored words for "Hot Searches"

    1.0.23

    (2016-05-17)

    Fixed

    • Fixed an issue with possible search layer exception

    1.0.21, 1.0.22

    (2016-05-11)

    Fixed

    • Fixed an issue with translations .html templates

    1.0.20

    (2016-05-08)

    Fixed

    • Fixed an issue with wrong autocomplete position on mobile devices

    1.0.19

    (2016-05-06)

    Fixed

    • Fixed an issue with wrong currency convert rate
    • Fixed an issue with multi-store configuration

    1.0.17

    (2016-04-29)

    Fixed

    • Fixed an issue with tax

    1.0.16

    (2016-04-27)

    Fixed

    • Fixed an issue with html entity chars

    1.0.15

    (2016-04-11)

    Fixed

    • Fixed possible issue with http/https ajax urls
    • Fixed an issue with cache warmer
    • Fixed an issue with behaviour for popular search queries

    1.0.14

    (2016-04-06)

    Improvements

    • Hot Searches

    1.0.13

    (2016-04-1)

    Improvements

    • Performance and Styles

    1.0.12

    (2016-03-25)

    Improvements

    • Integrated Mirasvit Knowledge Base

    1.0.11

    (2016-03-23)

    Improvements

    • Display full category path for categories
    • Default configuration for indexes

    Fixed

    • Fixed an issue with hiding placeholder before redirect to "View all results"
    • Fixed an issue with selection not active indexes

    1.0.10

    (2016-03-11)

    Improvements

    • Improved loader logic

    Fixed

    • Fixed issue with FrontController headers

    1.0.9

    (2016-03-09)

    Fixed

    • Fixed an issue with price formatting
    • Fixed issue with FrontController headers

    Documentation

    • Updated installation steps

    1.0.8

    (2016-03-06)

    Improvements

    • Search by Mirasvit Blog MX
    • Added ability to set-up custom css styles in magento backend
    • Improved Translations

    Fixed

    • Fixed compatibility issue with Amasty_Shopby
    • Fixed an issue with cache
    • Fixed an issue related with autocomplete position on some devices

    1.0.7

    (2016-02-22)

    Fixed

    • Fixed an issue related with case sensitive search results (should be same for both registers)
    • Fixed an bug with undefined configuration for search index
    • Cache id for results

    1.0.6

    (2016-02-15)

    Improvements

    • Added caching for results (tag FULL Page Cache)
    • Added link/url for Popular Suggestions
    • Changed autocomplete block (added injection). Removed form.
    • Added form loaded state

    Fixed

    • Fixed issue with broken product image url, if image not assigned to image
    • Fixed issues related with autocomlete injection
    • Fixed an issue with page cache (increased TTFB)
    • Fixed an performance issue related with locale/currency (temporary fix)

    Documentation

    • Added user manual

    1.0.5

    (2016-02-02)

    Fixed

    • Fixed an performance issue related with locale/currency (temporary fix)

    Improvements

    • Added form loaded state

    Search Elastic [mirasvit/module-search-elastic]

    1.2.13

    (2018-07-24)

    Fixed

    • Manadev compatibility

    1.2.12

    (2018-07-19)

    Fixed

    • B2B issue

    1.2.11

    (2018-07-18)

    Fixed

    • Solved an issue with price mapping

    1.2.10

    (2018-07-04)

    Fixed

    • Issue with fast mode

    1.2.9

    (2018-07-02)

    Fixed

    • CategoryProduct issue on M2.2.5

    1.2.8

    (2018-07-02)

    Fixed

    • Issue with UnitTests

    1.2.7

    (2018-06-18)

    Fixed

    • Issue with di:compile

    1.2.6

    (2018-06-15)

    Fixed

    • EE reindex error

    1.2.5

    (2018-06-15)

    Improvements

    • Fast Mode
    • Indexation

    1.2.4

    (2018-06-07)

    Fixed

    • Issue with REQUEST_URI
    • Issue with price interval

    1.2.3

    (2018-05-30)

    Improvements

    • Added option "ignore_malformed" to mapping

    1.2.2

    (2018-05-24)

    Improvements

    • ES status output

    Fixed

    • Memory leak issue during products indexation

    1.2.1

    (2018-05-23)

    Features

    • Direct autocomplete (beta)

    Improvements

    • Changed indexation workflow (full reindex is required)

    1.2.0

    (2018-04-05)

    Improvements

    • Changed full reindex logic: Added temporary indexes and aliases

    1.1.21

    (2018-03-22)

    Fixed

    • Stock Status

    1.1.20

    (2018-03-12)

    Fixed

    • Issue with mapping
    • Multiword relevance

    1.1.19

    (2018-03-09)

    Fixed

    • Issue with stock status

    1.1.17

    (2018-03-05)

    Fixed

    • Category

    1.1.16

    (2018-02-27)

    Improvements

    • Category IDs for product index
    • Mapping

    Fixed

    • Correct visibility attribute for mutlstore configuration

    1.1.15

    (2018-02-20)

    Improvements

    • ES status

    1.1.14

    (2018-02-16)

    Fixed

    • Fielddata

    1.1.13

    (2018-02-16)

    Improvements

    • Enabled fielddata for predefined _raw fields (sku, description, name etc)

    1.1.12

    (2018-02-15)

    Fixed

    • Issue with mapping (short_description_raw as long)

    1.1.10

    (2018-02-15)

    Fixed

    • Restored previous version (High memory usage issue)

    1.1.9

    (2018-02-13)

    Improvements

    • reindex performance

    1.1.8

    (2018-01-30)

    Fixed

    • Issue with price data mapper

    1.1.7

    (2018-01-26)

    Fixed

    • Issue with filter by _raw

    1.1.6

    (2018-01-24)

    Fixed

    • Search by options

    1.1.5

    (2018-01-19)

    Fixed

    • Filter wildcardFilter not implemented

    1.1.4

    (2018-01-15)

    Improvements

    • Matching (wildcard matching + stemming)
    • Detailed status information (mapping and index settings)

    1.1.3

    (2018-01-04)

    Improvements

    • Added stemmer to elastic index settings (stemmer based on store locale)

    1.1.2

    (2017-12-22)

    Fixed

    • Removed compatibility with old elasticsearch php library for solving error Elasticsearch\Common\Exceptions\BadRequest400Exception: {"error":"Content-Type header [] is not supported","status":406}

    1.1.1

    (2017-12-18)

    Fixed

    • Search Spell Correction

    1.1.0

    (2017-11-30)

    Improvements

    • Code Refactoring
    • Compatibility with Elasticsearch 6.0.x

    1.0.23

    (2017-11-09)

    Fixed

    • Issue with intervals

    1.0.22

    (2017-11-07)

    Fixed

    • Issue with spell correction adapter

    1.0.21

    (2017-10-27)

    Fixed

    • Issue with intervals

    1.0.20

    (2017-09-27)

    Fixed

    • M2.2

    1.0.19

    (2017-09-25)

    Fixed

    • Installation

    1.0.18

    (2017-09-19)

    Fixed

    • Update methods visibility

    1.0.17

    (2017-08-29)

    Fixed

    • Updated elastic configuration (analyzer)

    1.0.16

    (2017-08-18)

    Fixed

    • Issue with price indexation
    • Improved relevance

    1.0.15

    (2017-07-26)

    Fixed

    • Issue with Mapping generation

    1.0.14

    (2017-07-13)

    Fixed

    • Issue with "Not Words"

    1.0.13

    (2017-06-21)

    Fixed

    • Boots conversion

    1.0.12

    (2017-05-31)

    Improvements

    • Validate elastic version

    Fixed

    • Composer requirements

    1.0.11

    (2017-05-25)

    Improvements

    • Indexation process

    Fixed

    • Autocomplete
    • Issue with stock status
    • Out of stock products
    • Compatibility with Amasty layered navigation

    1.0.10

    (2017-05-22)

    Improvements

    • Significant changes in indexation process
    • Relevance
    • Search with dashes

    1.0.9

    (2017-05-05)

    Improvements

    • Full reindex time

    1.0.8

    (2017-05-05)

    Fixed

    • Indexation issues
    • Spell correction provider
    • Number of terms buckets for aggregation

    1.0.7

    (2017-05-01)

    Fixed

    • Issues with indexation

    1.0.6

    (2017-04-14)

    Fixed

    • Suggestions provider

    1.0.5

    (2017-04-13)

    Fixed

    • Issues with indexation

    1.0.4

    (2017-04-11)

    Improvements

    • Spell correction provider

    1.0.3

    (2017-04-06)

    Improvements

    • Added prefix for indices

    1.0.2

    (2017-03-06)

    Improvements

    • Improved performance

    Fixed

    • Fixed an issue in query builder

    1.0.1

    (2017-03-03)

    Improvements

    • Added logger
    • Stability improvements

    1.0.0

    (2017-02-16)

    • initial release

    Search Landing Page [mirasvit/module-search-landing]

    1.0.4

    (2018-04-12)

    Features

    • Allow redirect by search term to url key

    1.0.3

    (2017-09-26)

    Fixed

    • M2.2

    1.0.2

    (2017-07-25)

    Fixed

    • Issue with static tests

    1.0.1

    (2017-05-03)

    Fixed

    • Issue with UI

    1.0.0

    (2017-05-03)

    • Initial release

    Search Report [mirasvit/module-search-report]

    1.0.4

    (2018-04-20)

    Fixed

    • Issue with report by search terms

    1.0.3

    (2018-02-14)

    Improvements

    • Switched to new module-report version

    Fixed

    • Added details for secure cookies added details for secure cookies

    1.0.2

    (2017-09-26)

    Fixed

    • M2.2

    1.0.1

    (2017-07-21)

    Fixed

    • Possible issue with "Circular dependency"