Search Ultimate Documentation
Here you will find everything you need to set up a better search experience.
This guide is for
Magento 2.4 only
The Search Ultimate extension gives you a powerful way to search through your store. Search Ultimate's set of modules includes:
- Elastic Search
- Sphinx Search
- MySQL Search
- Search Spell-Correction
- Search Autocomplete
- Search Reports
- Landing Pages
First, please find your extension in your account in the My Downloadable Products section.
Start with the Installation and Quick Start options. It is best to follow our step-by-step guide to configure the best search results.
Go ahead, dive in!
Learn about the initial setup:
Search Ultimate Documentation
Here you will find everything you need to set up a better search experience.
This guide is for
Magento 2.4 only
The Search Ultimate extension gives you a powerful way to search through your store. Search Ultimate's set of modules includes:
- Elastic Search
- Sphinx Search
- MySQL Search
- Search Spell-Correction
- Search Autocomplete
- Search Reports
- Landing Pages
First, please find your extension in your account in the My Downloadable Products section.
Start with the Installation and Quick Start options. It is best to follow our step-by-step guide to configure the best search results.
Go ahead, dive in!
Learn about the initial setup:
Installation
On this page, you will find two possible ways to proceed with our extension's installation.
Please note these instructions are valid for
Magento 2.4 only. To install the extension on a previous Magento
version, please follow:
Installation via composer (preferably)
We recommend this installation method because the composer automatically checks and installs the necessary dependencies,
and it is also much easier to keep the extension up-to-date.
- Back up your store's database and web directory.
- Log in to the SSH console of your server and navigate to the root directory of the Magento 2 store.
- Copy the installation instructions from the My Downloadable Products / View & Download page to the SSH console.
If you bought the extension in the Magento Marketplace, run the command in your store's root folder.
composer require mirasvit/module-search-ultimate
- To enable the extension, run the commands:
php -f bin/magento module:enable Mirasvit_Core Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchElastic Mirasvit_SearchSphinx Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_Report Mirasvit_SearchReport
php -f bin/magento setup:upgrade
-
Clean the cache
php -f bin/magento cache:clean
-
Deploy static view files
rm -rf pub/static/*
rm -rf var/view_preprocessed/*
php -f bin/magento setup:static-content:deploy
- Reindex the search index and the spell-correction index
php -f bin/magento indexer:reindex catalogsearch_fulltext mst_misspell
Installation via direct file upload
You can also install the extension via direct files uploading.
- Go to My Downloadable Products / View & Download. Download the extension package.
If you bought the extension in the Magento Marketplace, you are not able to install the extension via a direct file upload. You need to do the installation via the composer, or contact the Mirasvit support team.
- Unpack .zip package and copy the contents to the Magento root directory
- Log in to the SSH console of your server and navigate to the Magento root directory.
-
To enable the extension, run the commands:
php -f bin/magento module:enable Mirasvit_Core Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchElastic Mirasvit_SearchSphinx Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_Report Mirasvit_SearchReport Mirasvit_SearchGraphQl Mirasvit_SearchUltimate
php -f bin/magento setup:upgrade
-
Clean the cache
php -f bin/magento cache:clean
-
Deploy static view files
rm -rf pub/static/*
rm -rf var/view_preprocessed/*
php -f bin/magento setup:static-content:deploy
-
Reindex search index and spell-correction index
php -f bin/magento indexer:reindex catalogsearch_fulltext mst_misspell
Learn about the initial setup:
Install the extension for Hyva
-
Run the command
composer require mirasvit/module-search-ultimate-hyva
-
Enable the installed Hyva modules:
php -f bin/magento module:enable Hyva_MirasvitSearch Hyva_MirasvitSearchAutocomplete Hyva_SearchMisspell
-
Update the Magento database schema and data with the command:
php -f bin/magento setup:upgrade
-
Compile the code of the installed extension:
php -f bin/magento setup:di:compile
-
Check the file app/etc/hyva-themes.json. If there are no entries for the mirasvit/module-search-ultimate-hyva package - run the following command:
php -f bin/magento hyva:config:generate
-
Generate the styles for the installed extension:
cd /path/to/theme/web/tailwind/;
npm run build-prod
-
Deploy the static view files
cd /path/to/project/;
rm -rf pub/static/*; rm -rf var/view_preprocessed/*;
php -f bin/magento setup:static-content:deploy
- Run the command below to clean the cache:
php -f bin/magento cache:flush
Quick Start
Search Ultimate is our most powerful extension which combines all of our best features to enhance the search capabilities of Standard Magento.
It combines several powerful modules, each of which offers you a large set of options:
- Core Search Module - contains everything necessary to enhance search and display of its results.
- Search Engines
- Elasticsearch - extends native Magento Elasticsearch engines.
- Sphinx Search - contains an easy and rich interface for the Search Sphinx engine.
- MySQL Search - implements search functionality using MySQL database.
- Search Autocomplete - allows you to enhance your search by adding suggestions at the customer's fingertips.
- Search Spell Correction - allows you to correct on-the-fly customer misspellings, and ensure that virtually any request will be satisfied.
Here is how you can tune up our extension for maximum effectiveness.
-
Tune-up Core Search Settings. Start by creating Indexes and configuring Search Results.
After you have created Indexes, it's better to quickly reindex all data. The best way to do it is via console/SSH:
php -f bin/magento indexer:reindex catalogsearch_fulltext
-
Consider which search engine you're about to use.
-
Add to your store Stopwords and Synonyms to enhance search. You can even import them using command-line interface.
-
Create a set of Landing Pages to create convenient hubs for your most important products.
-
Enhance your search by creating rules for 'long-tail search' and ordering products at search results.
-
Configure Autocomplete to provide your customers with useful suggestions and searching tips.
-
Enable misspell correction to provide customers with results even when they make mistakes.
- Analyze your searches with our Reports and build flexible search policies to boost your store capabilities to the top.
Please follow our guide step by step to get the best search result!
General Settings
Here you can quickly navigate across all the functionality settings we have available. Please use the list below to navigate.
This section covers all topics necessary for working with indexes, and consists of the following subsections:
-
Global Search Settings
- Search Engine Configuration
- Sphinx Search Engine
- Installation
- Connection with Sphinx Engine
- Elastic Search Engine
- Search Settings
- Multi-store Search Result
- "Long-Tail" Search
- Landing Pages
- Synonyms
- Stopwords
- Customize Search Weight
-
Search Indexes Settings
- Managing Indexes
- Adding New Index
- Product Index
- Category Index
- CMS Index
- Attribute Index
- Wordpress Blog Index
- Add Custom Index
Configure Key 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 the Search Logic Configuration. It is located at System -> Search Management -> Configuration.
Search Engine Configuration
Our extension allows you to power up your search either with default Magento Elasticsearch engines or additional engines.

Option Search Engine selects which engine should be in charge, and has three possible values:
- Elasticsearch 7, Elasticsearch 6.x, Elasticsearch 5.0.x - native Magento search engines.
- MySQL - search engine, based on MySQL fulltext search.
- Sphinx Search engine - search engine, based on Sphinx Search.
You can manage your store engine status and indexes:
- Check Status - describes whether the search engine is running on the server or not.
- Reset Indexes - deletes all available indexes. Products will disappear from the frontend if you click it. Run reindex to restore indexes.
- Reset Store Indexes - deletes store indexes by Elasticsearch Index Prefix. Products will disappear from the frontend if you click it. Run reindex to restore indexes.
Note
MySQL search engine mode does not require the installation of Elasticsearch or Sphinx Search on your server, but you will still receive the same features as with the other engines.
However, you may experience a slower search speed than with the Elastic/Sphinx engines. This engine is applicable for small catalogs, or if your server doesn't allow the installation of Elasticsearch or Sphinx Search.
-
Sphinx Search Engine
Sphinx is an open-source full-text search server which features high performance, relevance (aka search quality), and integration simplicity. It's written in C++ and runs on Linux (RedHat, Ubuntu, etc), Windows, macOS, Solaris, FreeBSD, and a few other systems. It is best used for stores with product quantities below 50k who do not require layered navigation or aggregated search requests. Read more about this engine key features.
Sphinx Search Ultimate adds to the option Search Engine Configuration -> Search Engine possible value Sphinx Search.

Note
To start, please make sure that you have installed Sphinx Search Engine.
To do this, please follow our installation guide
External Sphinx Engine also 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 the same server - triggers the appearance of additional features of Sphinx Daemon. Can have two different modes:
For Sphinx installed on the same server with your Magento store :

- Yes - defines that Sphinx works on the same server as store and database. Triggers the following additional options and buttons, which allows the managing daemon:
- Sphinx Bin Path - defines the 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 have an unexpected server power-off (for example, for maintenance purposes).
- Check Status - button that allows viewing current daemon status
- Restart Sphinx Daemon - button which allows restarting daemon directly from the Magento Configuration pane.
- Reset - button that allows resetting the daemon current search task.
For Sphinx installed on the dedicated (remote) server :

- No - defines that Sphinx works on separate or dedicated server.
- Generate configuration file - button that allows you to generate Sphinx config file to copy to your remote (dedicated) server.
Note
If you already installed Sphinx Search engine, please learn more about the connection with Sphinx Engine.
The Search Engine Configuration section contains an Additional Configuration subsection, visible for External Sphinx engine only. It allows you to tune up the Sphinx configuration file, and contains the following settings:

- Custom Base Path - defines a custom path to Sphinx, if it was not installed 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 you to add settings to the Sphinx index configuration. Read more about it here.
- Custom Charset Table - allows for adding character sets to the Sphinx configuration file. Read more about it here.
-
Elastic Search Engine
Elasticsearch is a distributed RESTful search and analytics engine capable of solving a growing number of use cases, written on Java so it can be run virtually anywhere. It is best used for stores with more than 50k of products and/or support of Layered Navigation. Read more about its key features.
You can configure a connection using native magento interface at Stores -> Configuration -> Catalog -> Catalog Search
The extension also features two buttons that allows you to check the actual Elastic Search status and reset indexes:
- Check Status - button that allows for viewing current Elastic status
- Reset Indexes - button that removes Elastic search indexes. To restore indexes, just run a full search reindex.
Search Logic Configuration

- Wildcard search - allows the customer to search the product by part of a word, marking unknown parts with asterisk (*). There are four different wildcard modes available:
- 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, the search extension will seek keywords from Find word columns, and automatically replace them with one from the Replace With column. Column Find word can contain more than one keyword, separated by a comma.
- 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 the Long Tail Configuration section.
- Match mode - overrides the default Magento mode of search with one of the following options:
- AND - this mode is default. Elements (e.g. products, pages) matched only when all requested keywords are found in respective attributes.
- OR - defines that elements matched only when at least one of the requested keywords is found.
Search Features
- Enable "Search In" - if the option is enabled, additional "Search in" block with aggregated by categories search links will be showed on the search results page
- Enable Search On Category Page - this option allows to show additional search bar on category pages
- Minimum number of products allows to set minimum number of products in the category to display search bar
- Enable redirect from 404 to search results - if this option is enabled, the customer will be redirected to the store search results of the broken URL text instead of the "404 Not Found" page.
- Redirect if Single Result - if the search query results only have one match, the customer will be immediately taken to the corrresponding product page.
- Enable Google Sitelinks Search - if the option is enabled, the extension shows the Sitelink Search Box on the Google search results page. After enabling this option, the search box will be shown only after Google reindexing.
- Enable search terms highlighting - if this option is enabled, search query word(s) will be highlighted in the search results.
- Omit tabs when the number of results fewer than - indicates when an extension should display search indexes as tabs.
- Ignored IPs - Doesn't track search queries for listed IPs, comma separated
- Enable ASCII Folding - enable ASCII Folding for Elasticsearch Engine. Fixes search issues related to accented characters.
- Enable Content Widget Indexation - if this option is enabled, indexation of widgets in the content will be performed
Multi-store Search Result
This option is useful when you have store-dependent elements in your store. For example, you have products which are visible only in specific storeviews and you wish to allow customers to search simultaneously in all your stores.
Sphinx Engine Installation
If you want to use our extension with Sphinx Engine, you first need to install it.
Note
Warning: The minimum allowed sphinx engine version is 2.2.x, 3.x
Installation includes a set of actions that should be performed under root privileges. Actions can differ depending on the selected platform.
After installation, run full reindex of Sphinx Engine indexes to fully enable your new search engine.
Installation on Ubuntu
Execute the following command from console/SSH under root privileges:
sudo apt-get install sphinxsearch
Proceed to Connection with Sphinx Engine
Installation on CentOS
Execute the following command from console/SSH under root privileges:
sudo yum install sphinxsearch
Proceed to Connection with Sphinx Engine
Installation with Stemmer (with language specific morphology)
In order to install Sphinx with Stemmer, run the following commands from console/SSH under root privileges:
wget http://sphinxsearch.com/files/sphinx-2.2.11-release.tar.gz
tar xvf sphinx-2.2.11-release.tar.gz
cd sphinx-2.2.11-release
wget http://snowball.tartarus.org/dist/libstemmer_c.tgz
tar xvf libstemmer_c.tgz
./configure --with-libstemmer
make
make install
-
Learn more about Libstemmer morphology
Libstemmer controls which characters are accepted as valid and which are not, and how the accepted characters should be transformed (eg. should the case be removed or not).
If charset table is configured for special language chars, then search phrases "kottkvarn" and "köttkvarn" will return the same result.
Libstemmer supports morphology of the following languages:
- Danish
- Dutch
- English
- Finnish
- French
- German
- Hungarian
- Italian
- Norwegian
- Polish
- Portuguese
- Romanian
- Russian
- Spanish
- Swedish
- Turkish
To configure morphology and charset tables for additional languages, perform the following actions:
- Open the file
/vendor/mirasvit/module-search-sphinx/src/SearchSphinx/etc/conf/index.conf.
-
Configure morphology variable. Standard language codes you can find here. Use two-letter codes from 639-1 column.
Tip
For example, to add German to the list of supported languages, you need to set in
index.conf:
morphology = stem_enru, libstemmer_de
Read more about morphology here.
-
Add charsets to the charset_table variable. List of codes for different charset tables can be found here
Tip
For example, to add English and Russian characters, variable should look as shown below:
charset_table = 0..9, A..Z->a..z, _, a..z, \
U+410..U+42F->U+430..U+44F, U+430..U+44F, U+401->U+451, U+451
Read more about character tables here.
Proceed to Connection with Sphinx Engine
Manual installation
In some cases, automatic installation either does not start, or even is not possible. In those cases, you can manually install Sphinx:
wget http://sphinxsearch.com/files/sphinx-2.2.11-release.tar.gz
tar xvf sphinx-2.2.11-release.tar.gz
cd sphinx-2.2.11-release
./configure
make
make install
Configuration file will be generated automatically.
Proceed to Connection with Sphinx Engine
Connection with Sphinx Engine
After the Sphinx Engine is installed, you need to connect it to our Search Extension.
Settings are diffenent depending on where you had installed Sphinx - on the same server as a store, or on a dedicated separate server.
Connect with Sphinx Engine on the same server
- Go to System -> Search Management -> Settings and proceed to Search Engine Configuration.
- In the field Search Engine select External Sphinx Engine option, and fill in the following fields.
- Sphinx Host - sphinx daemon host. Should be set to localhost in this case.
- Sphinx Port - sphinx daemon port (any free port).
- Sphinx Bin Path - if "searchd" is not configured in shell paths on your server, here you need to enter the full path to "searchd" (ex.
/usr/local/bin/).
- Tune up your Search Daemon, using extended options in Additional Configuration subsection if needed.
- Save and click Reset,then Restart Sphinx Daemon. More about this buttons find the Shell Commands.
- Run the following command
php -f bin/magento indexer:reindex catalogsearch_fulltext to reindex search indexes.
Connect with Sphinx Engine on another server
To establish a connection with sphinx engine on another server, you need to run sphinx engine with an auto-generated configuration file.
Go to System / Search Management / Settings / Mirasvit Extensions / Sphinx Search.
- Select another server option and press the button "Generate configuration file".
- Copy the configuration file to the sphinx server (same path to file is required)
- Start sphinx daemon using command
searchd --config <path to config/sphinx.conf>
- Run the search reindex in System / Search Management / Search Indexes
Configure "Long-Tail" Search
This section describes the Long-Tail Search feature which will allow you to have the correct search results for words that contain dashes or other non-alphabetic symbols. You can also replace the most typical errors customers make in complex product names on the fly .
What is Long-Tail Search?
For example, we have a product Canon PowerShot SX500 IS. The customer can request Canon PowerShot SX-500IS, which a default search will not find, because it differs from the actual product label.
This is because Magento by default during reindex uses only correct product labels from the database, thus, ensuring the index will contain only them - making products with complex names "ineligible" for search.
This is where "Long-tail" search comes in. During the reindex and search, this feature recognizes keywords by pattern and replaces them either with empty space or some other characters, "correcting" customer's request in real time.
In the example above, the SX500 IS can be converted to the SX500IS and during the search, the SX-500IS is also be converted to the SX500IS by replacing the '-' symbol with empty char.
This way, the search will be able to find products by several combinations of spelling the product's name.
Also, please learn more about configuring Long-Tail Search for your store in our Blog article.
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 is used for search index, during an indexing process, and goes for search phrases during a search.
E.g. /([a-zA-Z0-9]*[\-\/][a-zA-Z0-9]*[\-\/]*[a-zA-Z0-9]*)/
- Replace Expression - the regular expression(s) for parsing 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.
Configuring Long-Tail Search
Here are some of the 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
Moving Long-Tail Expressions from M1 to M2
Long-Tail expressions, which are used in Search Sphinx for M1 and M2 slightly 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 regex 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:
Customize Search Weight
Our extension arranges the relevance of products found using Global Settings. However, 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.

This weight allows to set a positive or negative value to increase/decrease original product score and change the product position in search results list.
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
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 in 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
- Adding New Index
- Product Index
- Category Index
- CMS Page Index
- Attribute Index
- Wordpress Blog Index
Managing Indexes
Our search can combine all indexes existing in your configuration to boost the 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 which you can configure them.
Each index, added to this grid, displays the following properties:
- Title - title of the search index.
- Type - shows the 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 the current index is ready for searching. The Disabled value means that particular index will be excluded from the search.
Additional Action column provides common actions that can be performed directly from the grid, such as:
Adding and Configuring New Index
-
To add a new index to the Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
-
Index record creation is divided into two stages: setting common settings and specific, which depend on their type. Common settings are shown in the General Settings subsection:
- Title - title of the search index. It will be used as a tab header at the search display page.
- Type - shows the index type (searchable content type). Some values of this field will trigger specific options. Pick a link from type list below to know more:
- Magento Indexes
- Product
- Category
- CMS Page
- Attribute
- Custom Search Indexes
- Mirasvit Extensions
- Blog MX
- Knowledge Base
- Gift Registry
- Magefun Blog Extension
- Mageplaza Blog Extension
- Ves Extensions
- Amasty
- Blackbird Content Manager
- Position - the position of the index in the search results. The extension will sort tabs on the search results page based on the position.
- Active - sets whether the index should be activated.
-
Press Save and Continue Edit to proceed to the index configuration stage.
- Add Searchable Attributes to the type-dependent option list, with rows corresponding to attributes where the extension should conduct a 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 the 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 the search will not work properly.
-
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
- Save the index and activate it to be included in the search.
During installation, three indexes will be automatically created and configured: Product, Category and CMS Page.
Product Index
The Product Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Specific options of this type will be shown on the Properies section of the Index edit page:
- Search by Parent Categories Name - include in the search all parent categories (useful when a store has a wide categories tree).
- Search by child products - include associated products from Bundled, Grouped and Configurable products in the search.
- 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 in addition to existing options).
- Exclude out of stock products - exclude out of stock products from the search (useful when out of stock products are visible in the catalog but undesirable to show in search results).
Category Index
Category Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's no specific options for this type of index.
CMS Index
CMS Page Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
There's only one specific option for this type on the Properies section of the Index edit page:
- Ignored CMS Pages - defines, on whose CMS pages search should not be performed. You can select zero or more pages here via the checkbox drop-down list.
Attribute Index
Unlike other indexes, this one can be created only for a specific attribute which should be displayed as a separate section in the Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at the Stores -> Attributes -> Product grid. Pick up the desired attribute, then jump to the Storefront Properties subsection and make it 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.g. they belong to a selectable type.
To see type of Product Attribute, visit the Stores -> Attributes -> Product grid, pick up the attribute record, and see the 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 something similar, you have to make them selectable first, and then make them available for searching as above.
After saving the product, you can configure Attribute Index for this attribute at the System -> Search Management -> Search Indexes grid. Read more about it here: adding new index.
Wordpress Blog Search Index
Wordpress Blog Index can be created at the System -> Search Management -> Search Indexes grid. Read more about it here: 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.
Example
A 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',
),
),
),
-
If WordPress is installed on a separate database, you need to create a new connection in the file app/etc/env.php.
Example
A typical separate database connection should look similar to this:
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],
- Table Prefix - the prefix for the wordpress tables (wp_ by default) or login to MySQL: use your_wp_dbname; show tables;
-
Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like the example below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.html
Implementing Custom Search Index
Sometimes it's necessary to have a specific type of Index which is either not included to our search extension, or belongs to some third-party extension. In this case, custom index can be implemented using the following instructions:
-
Clone the example module from the repository https://github.com/mirasvit/module-search-extended.git
Note
There must be taken into account your Magento version. Correct steps should be:
git clone <repo_url> - Clone the example module from the repository;
cd module-search-extended/ - Change directory;
git checkout magento23 - Navigate to specific tagname for Magento 2.1-2.3 please use tag magento23.
git checkout magento24 - For Magento 2.4+ please use tag magento24.
To make sure you switched to the correct tagname, run git branch.
- Go to
app/code/Mirasvit/SearchExtended/Index/ and rename the subpath Magento/Review/ to the required one. We suggest to use the following structure - ([provider]/[module]/[entity])
- Change class names in file
app/code/Mirasvit/SearchExtended/Index/[provider]/[module]/[entity]/Index.php
- Set your values to
getName(), getPrimaryKey() and getIdentifier() methods
- Configure the attributes you want to get in
getAttributes() method
- Change
buildSearchCollection() and getIndexableDocuments() methods
- Change class names in file
app/code/Mirasvit/SearchExtended/Index/[provider]/[module]/[entity]/InstantProvider.php
- Set your values to
map() and mapItem() methods
- Change registration for new index in file
app/code/Mirasvit/SearchExtended/etc/di.xml
- Adjust layout file
app/code/Mirasvit/SearchExtended/view/frontend/layout/catalogsearch_result_index.xml
- Rename the template name/path and adjust it
/app/code/Mirasvit/SearchExtended/view/frontend/templates/index/magento/review/review.phtml
- Adjust layout file
app/code/Mirasvit/SearchExtended/view/frontend/layout/default.xml
- Rename the template name/path and adjust it
/app/code/Mirasvit/SearchExtended/view/frontend/templates/magento_review.phtml
- Enable the module and Clear magento cache
If everything was performed correctly, you should be able to add index of your custom type like any regular index.
Configuring Autocomplete & Suggest
All Autocomplete settings are located in the System / Settings / Mirasvit Extensions / Search Autocomplete section.
It consists of the following sections:
- General Configuration
- Popular suggestions
General Configuration
This section is broken down into smaller subsections, and contains the following options:
- Minimum number of characters to search - specifies the minimum number of characters which customers need to enter to trigger autocomplete.
- The delay to start finding - specifies the delay between triggering autocomplete (by option above) and the beginning of the actual search.
Note
Our extension begins searching for possible autocompletion and offers suggestions only when both of the following conditions have been met:
- the customer has entered the minimal required number of characters;
- no actions took place during the specified delay period.
Fast Mode - This option allows you to greatly improve search speed by excluding Magento 2 from the autocomplete search at the initialization stage.
Note
- This option is available for Elasticsearch engine only;
- This option increase indexing time of the search index.
Searchable content - list of search indexes where the search is performed, and results are displayed as autocomplete options. Indices are either taken from standard Magento or if the extension is installed as part of Advanced Search Sphinx Pro or Sphinx Search Ultimate - from corresponding Indexes grid.
Note
The grid contains the following settings:
- Index - the name of the 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 the autocomplete drop-down widget.
You can drag and drop rows in this list to define the order in which results from different indices will be displayed in autocomplete drop-down.
Enable TypeAhead - enables the auto-suggestion feature. Our extension collects information about the most popular search queries and their results, groups them, and stores them separately. When autocomplete is triggered and the TypeAhead option enabled, our application automatically searches for the typed term and displays the suggestion of the most relevant query found.
Tip
Use the Right Arrow button to quickly turn auto-suggestion to full autocomplete query and save autocomplete time.
Product Settings - defines the content and appearance of autocomplete individual product information cells.
Popular Suggestions
Popular suggestions are the most popular queries which have been requested by customers. If a current customer request includes such a query, autocomplete can highlight them and bring them to the top of the drop-down.
Configure Search Spell Correction
All configuration options are located in the Store -> Configuration -> Mirasvit Extensions -> Search Spell Correction section.
There are only two options for now. In both, our extension analyzes the customer's request and tries to find products whose names most closely resemble the original request.
-
Enable spell correction - enables automatic spelling correction.
Example
Let's assume that your store has 'Samsung' products in the catalog.
When a customer accidentally misspells Samsang phone, the default Magento search will return nothing, since you have no such product.
But with this option enabled, the customer will be notified about potential misspelling and will see the results for the corrected search phrase Samsung phone.
-
Enable fallback search - enables searching for partial request satisfaction, when there are no results for the original request.
Example
Let's assume that customer puts the phrase red samsung phone into the search, but you have only samsung phone product.
If the store has no such product, the default Magento search also will return nothing.
But with this option enabled, the customer will be notified about the error, and will receive results by the correct search phrase samsung phone.
Search Results Validator
Validator - debugging tool. It is compatible only with the Elasticsearch engine.
It is located in the **System -> Search Management -> Validator** section.
To start validation, enter in the field Search term - wanted search term, and Entity ID which can be found in the Catalog - Products.
This tool helps you find out whether a particular product has been indexed or not. As a result, if the product has been indexed, you will get the output directly from the Elasticsearch index where it finds the matches and highlights all occurrences in the result.
Reports
With detailed search reports, you are able to check how relevant 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 the product from the 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
Manage Landing Pages
A landing search page is a special search result page with a static URL where customers are redirected by using some search expression.
Let's consider a large number of frequently requested (or just a promotional set) models of Samsung phones with a black coat. We can 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 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, for example, http://store.com/black-samsung-phone.html, and bind it to the search phrase "black samsung phone". When a customer goes to this (specific) URL, the search results for "black samsung phone" will be immediately built on it.
All such pages can be managed from the 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 the creation page, fill in the following fieds:
- Query Text - the key phrase, which should bring customer to the landing page (ex. black samsung phone)
- URL Key - relative path to the landing page. For example, if the URL key is
shoes/all, then the full URL would be https://example/shoes/all/.
- Active - activates or deactivated redirect to the landing page.
- Page Title - overrides the 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 the landing page.
- Save and activate the landing page.
Manage Synonyms
The extension enhances the functionality of native Magento synonyms and provides an additional capability for importing synonyms.
To import synonyms, follow these steps:
-
Create your custom CSV file using the following file structure.
able,capable
ananas,pineapple
bodyguard,guard
The name of this file should be equal to your language code in capital letters. Codes can be found here, use column 639-1 for that. For example use the "EN.csv" file name.
- Place your custom CSV file into the
[magento_root]/var/synonyms/ folder.
- Go to System -> Search Management -> Manage Synonyms and press the Import Synonyms button.
- The 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 the store views 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 a 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 a CSV-formatted file.
Adding New Stopword
- Go to the System -> Search Management -> Manage Stopwords grid and press the Add New Stopword button.
- On the creation page, fill in the following fields:
- Stopword - is the keyword which should be removed from search requests.
- Store View - allows you to select where defined synonyms will be applied.
- Save record.
Importing Stopwords
Our extension uses the CSV file format for stopwords importing. It should resemble the following format:
[Stopword_1]
[Stopword_2]
[Stopword_3]
The name of this file should be equal to your language code in capital letters. Codes can be found here, use column 639-1 for that.
Example
Let's create a stopwords file for English locale. The name of such a file would be
EN.csv, and its content should be:
but
now
what
except
To import stopwords from such a file, perform the following steps:
- Place your custom CSV file to the special
[magento_root]/var/stopwords/ folder.
- Go to System -> Search Management -> Manage Stopwords and press the Import Stopwords button.
- Dictionary field defines locale (language), for which stopwords are imported. It is picked from the name of your CSV import files.
- Store View defines the storeview, where imported stopwords should be applied.
- Press Import to import and apply stopwords.
Score Boost Rules
Score Boost Rules are a powerful tool, which allows you to influence the relevancy of search results, depending on certain conditions.
When the Mirasvit Search extension builds search results, it groups them by indexes' position and their position in System -> Search Management -> Settings -> Search Autocomplete -> Searchable Content. Groups can include Products, Pages, Categories and so on - they can be defined in System -> Search Management -> Search Indexes.
However, inside these groups items are listed strictly by their relevance to search query, which is calculated for each item separately as item rank. The position in a search results list is dependent on this rank value.
Score Boost Rules allows you to increase or decrease this rank depending on item properties, which allow you to move certain products to the top or botton of a list, which can be extremely useful for promotion and marketing purposes.
Creating a new Rule
To create a new Score Boost Rule, navigate to System -> Search Management -> Score Boost Rules section and press Add New Rule button.
You need to define the following properties to create a Rule:
- Title - internal title of the Rule
- Active - whether the Rule is active and should be applied to Search Results
- Active (date) - a time period, when the Rule should apply to Search Results. Leave this field empty to have the Rule always be applicable.
- Store - storeviews, where the current Rule should be applicable.
- Score Factor - score adjustment, which should be added or subtracted from the rating, generated by a search engine.
- Action - the action that should be performed. It can have only two possible values.
- Rank Adjustment - the numerical value, which should be added or subtracted from rating.
- Metric - defines, how Rank Adjustment shall be used for adjustment. It can have two possible values:
- Points - in this case, Rank Adjustment is just added to the actual rating.
- Times - in this case, the actual rating is multiplied by Rank Adjustment. It is used to rocket-jump products to the top (for example, promotional products).
- Parameter - defines which rating shall be adjusted by the Rule.
- Initial Score - the rating which was generated by search engine.
- Product Popularity - the popularity rating, which is defined as the quantity of orders of products that meet conditions below.
- Product Rating - product rating, that is defined as quantity of reviews for products, that meet conditions below
Conditions:
-
Apply the rule only for the following products - allows you to define which combination of products makes the Rule apply.
Note
To add additional conditions please go to Stores - Attributes - Product, select a necessary attribute, for example, SKU, open edition in the tab Storefront Properties, and set Yes for the Use for Promo Rule Conditions, clean Magento cache after saving.
These conditions use the same pattern, as with other rules in Magento 2, and are enclosed into logical blocks If ALL of these conditions are TRUE/FALSE (the products meet conditions, when all of them apply) or If ANY of these conditions are TRUE/FALSE (product shall meet only one of defined conditions).
Here are few useful examples that demonstrate how the Score Boost Rules work.
Examples
-
Erin Recommends Promo
This example allows you to move products that were recommended by your editorial board (defined here by the custom attribute Erin Recommends), to the top of the search results.
Title: Erin Recommends Promo
Score Factor: Increase by 10 points Initial Score
Apply the rule only for the following products:
-
Analog Watches to the End
This rule drops all analog watches to the very bottom when a customer search includes the "watch" keyword.
Title: Analog Watches to End
Score Factor: Decrease by 2 times Initial Score
Apply the rule only for the following products:
Product Name contains analog
-
New Products Promo
This example allows you to lift promotional products higher on the list than others, but not necessarily at the top.
Title: New Products Promo
Score Factor: increase by 5 points Initial Score
Apply the rule only for the following products:
Translation
Our extension supports multilanguage stores. To translate it, we have used the same logic as default Magento.
All our translation files are in the "/i18n" folder of each sub-module.
i18n files should be located at:
- vendor/mirasvit/module-name/src/ModuleName/i18n - if installed via composer;
- app/code/Mirasvit/ModuleName/i18n - if installed manually.
Create a separate .csv file of your language for our extension. The names of all languages can be found with this command:
php -f bin/magento info:language:list
Override the strings in your dictionary file:
"Original line" , "Translated line"
To avoid rewriting the file with the updating of the module, replace the translation file to your theme directory at app/design/frontend/THEME_VENDOR/theme_name/i18n/lg_LG.csv.
Where lg_LG.csv is a translation file in another locale.
To apply changes run static content deploy :
rm -rf pub/static/*
rm -rf var/view_preprocessed/*
php -f bin/magento setup:static-content:deploy
php -f bin/magento cache:flush
Example: translate "Sorry, nothing found for" and "Show all results" in Autocomplete:
- Open src/SearchAutocomplete/i18n/ directory to find the translation files;
- Make a copy of original en_EN.csv file, for example, nl_NL.csv file;
- Open nl_NL.csv file for editing;
-
If Fast Mode enabled at the Autocomplete settings
Change lines as below:
"Sorry, nothing found for ""%1."" change %1 to %s
"Show all %1 results →" change %1 to %d
"Sorry, nothing found for ""%s."", "Sorry niets gevonden voor ""%s.""
"Show all %d results →", "Toon alle %d resultaten →"
4) Temporarily disable a Fast mode in the autocomplete settings;
5) Run static content deploy;
6) Enable Fast Mode and run Magento reindex.
-
If Fast Mode disabled at the Autocomplete settings
Change lines as below:
"Sorry, nothing found for ""%1."", "Sorry niets gevonden voor ""%1.""
"Show all %1 results →", "Toon alle %1 resultaten →"
4) Run static content deploy;
Please do not add both kinds of translations in your locale file for a Fast mode enabled and disabled option. It will not work.
FAQ
This section describes the most common problems that customers report, and how they can be resolved.
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) {
.mst-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 the price without taxes or any other option for displaying the price including tax.
Keep getting error onto each search page: The page you requested was not found, but we have searched for relevant content.
This issue is possible if a certain page contains resources (js, css, images) with a 404 error.
To prevent this issue, you can disable a 404 search at System -> Search Management -> Settings -> Mirasvit Extensions -> Search.
After enabling Mirasvit_SearchAutocomplete my CSS styles are missed on frontend
Please follow System -> Search Management -> Settings -> Mirasvit Extensions -> Developer -> CSS Settings tab, set YES at Enable preprocessed CSS, then flush cache and run static content deploy.
Does Mirasvit Search support REST API?
Since Native Magento provides search API, our search extension uses it as well. Please follow the official documentation here
Singular/Plural search: how it works?
Our search extension supports singular and plural search out of the box for the EN, NL, RU locales. If you need to add support for other languages, use lang analyzer technology to customize your Elastic Search for the appropriate language.\
For the Sphinx, please use Sphinx engine version with Stemmer (with language specific morphology).
Display Search Recommendations
Enable Search Recommendations is now a part of Magento's core functionality, and this option was removed from the module configurations.
You can find related Magento configurations via Stores -> Settings -> Configuration -> Catalog -> Catalog -> Catalog Search -> Enable Search Recommendations.
Troubleshooting
This section contains the most common problems that customer can encounter, and how they can be resolved.
Note
Please, make sure that you're using the latest version of the extension. Otherwise, please update it to the latest version.
Search is not possible by SKU
Take a moment to verify the following conditions are in order:
- SKU attribute is searchable. You can check it in Stores -> Attributes -> Product grid -> SKU -> Storefront Properties -> Use in Search and Visible in Advanced Search should be Yes.
- SKU is in the list of Searchable attributes in Product Index. You can check it in System -> Search Management -> Search Indexes -> Product Index.
- If SKU includes dashes or other non-alphabetic symbols, set up Long Tail Search expressions as described in our manual.
- Validate the search result. Go to System -> Validator -> Validate Search Results. In the Search term field, enter your SKU, in Product ID - ID of the product without a searchable SKU and press Validate Search Results.
After enabling fallback search and entering too many words, search fails
Possible cause: too small a max_execution_time PHP parameter, which is not enough to complete requests with the large number of words.
Solution: there are two possible solutions.
-
Increase max_execution_time parameter either in .htaccess, or directly in PHP.ini.
- Use default Magento settings to adjust search parameters. They are located at Stores -> Configuration -> Catalog -> Catalog Search and consist of two options:
- Minimal Query Length - defines minimal quantity of words in search request (1 for default).
- Maximum Query Length - defines maximal quantity of words in search request (128 by default).
Typically, it is enough to decrease the latter parameter until the search works correctly.
Autocomplete (and/or Search Results) is too slow
Possible Causes and
Solutions
Aheadworks blog search doesn`t return results
- How to Resolve:
- Find and open the following file : Aheadworks/Blog/Block/Post.php
- Find
public function getSocialIconsHtml()
- After condition you will see this row
$block = $this->getLayout()->createBlock, place this code before
$socialIconsBlock = !empty($this->getSocialIconsBlock())?$this->getSocialIconsBlock():'Aheadworks\Blog\Block\Sharethis';
- Replace
$this->getSocialIconsBlock() after createBlock with $socialIconsBlock
- You should get your code to look like
$socialIconsBlock = !empty($this->getSocialIconsBlock())?$this->getSocialIconsBlock():'Aheadworks\Blog\Block\Sharethis'; $block = $this->getLayout()->createBlock( $socialIconsBlock,...
"unknown column" error during Sphinx reindex
Command line commands
Our Search extension also has a command-line interface which can be used from a console or SSH.
Here is the list of available commands. (for bin/magento):
Managing Search Sphinx from console
Console management of Search Sphinx includes the following commands:
start - starts Search Daemon
stop - stops Search Daemon
restart - kills Search Daemon process and starts it with clean data
reset - cleans search temporary data
status - displays current status of Search Sphinx engine.
ensure - special command, which automatically checks status, and only if daemon does not work, will it start up.
To execute management command, run the following expression from console/SSH:
bin/magento mirasvit:search-sphinx:manage --[command]
Running Reindex from console
Console reindexing can be run either for a whole store (without mode options), or for a selected Index (see more at Managing Indexes), and for a selected Store.
mirasvit:search:reindex --[mode]=[argument]
Possible modes are:
INDEX - allows for reindexing a particular index. [argument] value should be code if desired index.
STORE - allows for reindexing all indices at particular store. [argument] value should be code if desired store. Store codes can be seen in Stores -> All Stores in Magento 2 backend.
Tip
Possible codes of indices you can get directly at console by executing command
mirasvit:search:reindex --index=default
This command will display all indexes with codes in square brackets.
Modes can be used simultaneously, e.g. if you need to reindex the Product index (code is 'catalogsearch_fullindex') on store with code 'german', you need the following command:
mirasvit:search:reindex --index=catalogsearch_fullindex --store=german
Managing Stopwords from console
Console stopword managing allows you not only to import, but also to remove stopwords. For that, you will need the following command:
mirasvit:search:stopword [arguments]
Possible arguments are:
--file - defines, which CSV file will be used for stopwords importing.
--remove - optional argument, that commands to remove stopwords instead of importing. Requires previous argument.
--store=[store_code] - required argument, that forces import/remove action performing only on specific store. Store codes can be seen in Stores -> All Stores in Magento 2 backend.
Format of CSV file, which is used for managing stopwords, can be seen here.
Managing Synonyms from console
Console synonym managing allows you not only to import, but also to remove them. For that you will need the following command:
mirasvit:search:synonym [arguments]
Possible arguments are:
--file - defines which CSV file will be used for synonyms importing.
--remove - optional argument, that commands removing of synonyms instead of importing. Requires a previous argument.
--store=[store_code] - required argument that forces import/remove action performing only on a specific store. Store codes can be seen in Stores -> All Stores in Magento 2 backend.
The format of CSV file, which is used for managing synonyms, can be seen here.
Extension Upgrading
Please note these instructions are valid for
Magento 2.4 only. To upgrade the extension from previous Magento
versions (2.1.
- 2.3.), you need to disable and remove the previous extension and install the new one from scratch. To
do so, please follow:
To upgrade the extension, follow these steps:
- Back up your store's database and web directory.
-
Log in to the SSH console of your server and navigate to the root directory of the Magento 2 store.
If the extension was installed via:
-
Composer: run the command to update the current extension with all dependencies.
composer require mirasvit/module-search-ultimate:* --update-with-dependencies
Note
If you have the Hyva, run:
composer require mirasvit/module-search-ultimate-hyva:* --update-with-dependencies
Note
In some cases, the above command is not applicable, as it's not possible to update the current module, or you just need to upgrade all the Mirasvit modules in a bundle. In this case, the above command will not be effective.
Run instead composer update mirasvit/* command. It will update all the Mirasvit modules, installed in your store.
- Direct file upload: download the new extension package from our store and copy contents to the root Magento directory
-
Run the command to install updates:
php -f bin/magento setup:upgrade
-
Deploy static view files:
rm -rf pub/static/*
rm -rf var/view_preprocessed/*
php -f bin/magento setup:static-content:deploy
-
Clean the cache:
php -f bin/magento cache:clean
-
Rebuild the search index:
php -f bin/magento indexer:reindex catalogsearch_fulltext
Disabling the Extension
Temporarily Disable
To temporarily disable the extension, please follow these steps:
- Log in to the SSH console of your server and navigate to the root directory of the Magento 2 store.
-
Run this command to disable the extension:
php -f bin/magento module:disable Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchSphinx Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_SearchReport Mirasvit_SearchElastic Mirasvit_SearchGraphQl Mirasvit_SearchUltimate
Note
If you have the Hyva theme, run:
php -f bin/magento module:disable -f Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchSphinx Mirasvit_SearchAutocomplete Mirasvit_Misspell Mirasvit_SearchLanding Mirasvit_SearchReport Mirasvit_SearchElastic Mirasvit_SearchGraphQl Mirasvit_SearchUltimate Hyva_MirasvitSearch Hyva_MirasvitSearchAutocomplete Hyva_SearchMisspell
Remove the Extension
To uninstall the extension, please follow these steps:
- Log in to the SSH console of your server and navigate to the root directory of the Magento 2 store.
- Disable the extension.
-
Run this command to remove the extension:
composer remove mirasvit/module-search-ultimate
Note
If you have the Hyva theme, run:
composer remove mirasvit/module-search-ultimate mirasvit/module-search-ultimate-hyva
Change Log
2.7.8
(2026-04-20)
Fixed
- Fixed connection errors with the Sphinx search driver on PHP 8.2 and PHP 8.4 — deprecated
mysqli_init() and ping() calls replaced with compatible alternatives
- Sort By dropdown no longer appears in fullsize search mode when there are no results to sort
- "No results" message no longer flashes briefly while a search request is still loading in fullsize mode
- Pagination is now cleared when a search returns no results in fullsize mode
- Popular search suggestions now correctly appear only when the typed query is shorter than the configured minimum search length
2.7.7
(2026-03-25)
Features
- Log Autocomplete Search Terms
Improvements
- TypeAhead and Popular Suggestions in Full size autocomplete layout
Fixed
- Avoid setting search cookie on pages without prior search
- Magento 2.4.9 compatibility
- Type error on query param passed as array
2.7.6
(2026-02-27)
Improvements
- Default sort order now consistently available in autocomplete (including Fast Mode)
Fixed
- Fixed synonym import corrupting multibyte/UTF-8 characters
2.7.5
(2026-02-26)
Features
- Configurable keywords highlight toggle in search results
Improvements
- Windowed pagination for many-page results in autocomplete Full Size mode (shows page numbers instead of only prev/next)
2.7.4
(2026-02-13)
Fixed
- Fixed "No mapping found for field" errors in multi-store setups with OpenSearch 3.x (added unmapped_type fallback for sort fields)
- Fixed price filtering using wrong field for non-default customer groups and websites in autocomplete
2.7.3
(2026-02-12)
Fixed
- Fixed pagination not appearing on search results page when "Search In" category filtering is enabled
2.7.2
(2026-02-06)
Fixed
- Fixed Score Boost script errors on documents missing boosted fields (OpenSearch 3.x compatibility) — now uses safe field access
2.7.1
(2026-01-27)
Fixed
- Fixed pagination not rendering on search results page when current index had zero results
2.7.0
(2026-01-15)
Features
- Misspell correction now works independently for each search index — if a product search returns no results, it can suggest corrections per-index without affecting other tabs
- Added GraphQL resolvers for Mirasvit Blog, Ves Blog, and Ves Brand search indexes
Improvements
- Products Boost Rules now show a reminder to reindex Catalog Search after applying changes
- Category search bar is automatically hidden for categories set to "CMS Block only" display mode
2.6.15
(2025-12-16)
Fixed
- Fixed stale search results caused by over-aggressive static caching of search collections and index instances across store contexts
2.6.14
(2025-12-15)
Fixed
- Fixed "All Results" URL in autocomplete generating HTTP links instead of HTTPS
2.6.13
(2025-11-21)
Fixed
- Fixed synonyms with numeric values being incorrectly merged during parsing
2.6.12
(2025-11-13)
Improvements
- Search Autocomplete Fast Mode now works with Advanced Sorting (sort options apply correctly in full-size mode)
2.6.11
(2025-11-07)
Fixed
- Fixed synonym validation failing silently for non-ASCII/Unicode characters (added Unicode flag to regex)
- Fixed Magefan Blog index collection not loading correctly due to store_id handling
2.6.10
(2025-10-13)
Features
- Reindex a single product via console:
bin/magento mirasvit:search:reindex --one-product <id>
- Magefan SecondBlog search index support
Improvements
- Configurable maximum number of results when filtering search results by category
- Long-tail matching now applies to applicable child product attributes
Fixed
- Fixed missing store_id filter in Magefan Blog posts collection on search results page
2.6.9
(2025-09-12)
Improvements
- Field values exceeding 32 KB are now automatically truncated during indexing, preventing Elasticsearch indexing failures
2.6.8
(2025-08-27)
Fixed
- Fixed autocomplete Fast Mode accepting a limit value of zero from request parameters, causing empty results
2.6.7
(2025-08-21)
Improvements
- Category filter now appears in layered navigation within the search autocomplete dropdown
2.6.6
(2025-08-20)
Fixed
- Updated admin menu link for landing pages to point to the new Mirasvit_LandingPage module
- Fixed potential error in "Exclude out-of-stock" setting when product search index is not yet configured
2.6.5
(2025-08-18)
Fixed
- Fixed autocomplete pagination not working for non-product index types (Blog, CMS, etc.) when Fast Mode is disabled
2.6.4
(2025-08-15)
Features
- Configurable page size for search results in autocomplete dropdown (Full Size mode) — choose between Magento's default grid setting or autocomplete's own limit
Fixed
- Inactive categories no longer appear in layered navigation within the search autocomplete dropdown
2.6.3
(2025-07-29)
Features
- Extended explanation option in admin Search Results Validator showing detailed scoring breakdown
2.6.2
(2025-07-17)
Features
- Display additional product attributes (configurable) in autocomplete search results
2.6.1
(2025-07-07)
Fixed
- Fixed Amasty Mage245Fix compatibility — module status is now properly checked before applying its workarounds
- Fixed autocomplete layered navigation filters being expanded by default in Full Size mode (inverted boolean logic)
2.6.0
(2025-06-12)
Features
- Open autocomplete Full Size mode programmatically by dispatching the
mstOpenAutocomplete custom event
Improvements
- WCAG 2.2 AA compliance — search results and autocomplete now use semantic HTML (
<nav>, <form role="search">, proper <label> elements, ARIA attributes for tabs and list items)
2.5.5
(2025-05-26)
Fixed
- Fixed search engine status messages to be engine-agnostic for Magento 2.4.8 (works with both Elasticsearch and OpenSearch)
- Fixed OpenSearch client detection in autocomplete/instant search engine provider
- Fixed Product Boost rules not applying in autocomplete when sorting by
_score field
2.5.4
(2025-05-20)
Fixed
- Fixed stock status check running when MSI is only partially installed — now requires both
inventory_source_item and inventory_stock_sales_channel tables
2.5.3
(2025-05-16)
Fixed
- Fixed autocomplete config values explicitly set to "disabled" being silently overridden by legacy config fallback
2.5.2
(2025-04-23)
Fixed
- Fixed landing pages migration path
- Fixed OpenSearch client not being used when
opensearch engine is configured (was falling through to Elasticsearch 8 client)
2.5.1
(2025-04-14)
Features
- Boost Rules — select the time period for product popularity calculation (e.g., last 3 months, 6 months)
Improvements
- Boost Rules — improved popularity boost formula for better differentiation between products
- Magento 2.4.8 and PHP 8.4 compatibility
Fixed
- Fixed Search Terms index not working with MySQL engine
2.5.0
(2025-04-07)
Features
- Search results are now restored when navigating back in browser history (Full Size mode only)
Improvements
- Landing pages now use the integrated Mirasvit_LandingPage module for extended functionality
- Enhanced sorting behavior in autocomplete results (Full Size mode)
Fixed
- Fixed reindexing error when a category attribute was included in the products index configuration
- Fixed store parameter not being applied for
mirasvit:search:reindex console command
2.4.3
(2025-03-24)
Improvements
- Improved misspell check conditions in autocomplete to reduce false corrections
2.4.2
(2025-03-17)
Improvements
- Improved fallback search logic — now checks whether a redirect exists for the search term before triggering misspell correction
2.4.1
(2025-03-10)
Fixed
- Inactive categories no longer appear in the "Search In" category filter list
2.4.0
(2025-03-10)
Improvements
- Reorganized admin search settings structure with improved grouping and navigation
2.3.15
(2025-03-04)
Fixed
- Fixed autocomplete hanging indefinitely when search returns no results
2.3.14
(2025-02-21)
Improvements
- Spell correction is now skipped for search terms containing numbers (e.g., part numbers, SKUs)
2.3.13
(2025-02-17)
Fixed
- Fixed keyword highlighting not working in autocomplete category search results
2.3.12
(2025-02-11)
Fixed
- Fixed "too many redirects" loop when fallback search triggered repeated redirections
2.3.11
(2025-01-29)
Fixed
- Fixed Page Builder markup tags appearing in search autocomplete results instead of clean text
2.3.10
(2025-01-27)
Fixed
- Fixed incorrect stock status display for bundle and configurable products in search results
2.3.9
(2025-01-06)
Fixed
- Fixed Sphinx console command return type error
2.3.8
(2024-12-20)
Features
- Misspell notice in autocomplete — when spell correction is applied, a "Did you mean..." message appears in the dropdown
- Fallback search for autocomplete — if no results found, automatically retries with spell-corrected term
2.3.7
(2024-12-10)
Fixed
- Fixed compatibility issue with Amasty Shopby Lite affecting layered navigation on search results page
2.3.6
(2024-12-02)
Fixed
- Fixed "Exclude out-of-stock" functionality not working correctly with Multi-Source Inventory (MSI)
2.3.5
(2024-11-13)
Fixed
- Fixed compatibility issue with Amasty Shopby affecting search results filtering
2.3.4
(2024-11-04)
Fixed
- Fixed Sphinx search engine functionality issues
2.3.3
(2024-10-23)
Fixed
- Fixed search redirect not preserving GET parameters in target URL
- Fixed product price not displaying correctly in default autocomplete mode
2.3.2
(2024-10-16)
Fixed
- Fixed XSS vulnerability in search result tabs (HTML content was not properly escaped)
2.3.1
(2024-10-14)
Features
- Exclude out-of-stock products from search results (new configuration option)
2.3.0
(2024-10-08)
Improvements
- Hyva theme compatibility — now supported via the
mirasvit/module-search-ultimate-hyva package
- Layered navigation now positioned at the top in autocomplete Full Size layout
Fixed
2.2.71
(2024-10-02)
Fixed
- Fixed Product Boost Rule form display issues in admin panel
2.2.70
(2024-09-10)
Fixed
- Fixed BotDetectorService request handling error
2.2.69
(2024-09-05)
Fixed
- Fixed search weight not being applied correctly to product results
2.2.68
(2024-08-23)
Improvements
- Added module uninstall command support
Fixed
- Fixed uninstall compatibility issues
2.2.67
(2024-08-09)
Fixed
- Fixed search category tab timing out for categories with a large number of products
- Fixed Content Security Policy (CSP) compatibility issues
2.2.66
(2024-07-29)
Fixed
- Fixed compatibility issue with Mirasvit_Gdpr module
2.2.65
(2024-07-08)
Features
- Stock status indicator in autocomplete Full Size mode
Fixed
- Fixed product price visibility in Full Size mode not respecting store configuration
2.2.64
(2024-06-26)
Fixed
- Fixed HTML tags appearing in misspell "Did you mean..." message instead of plain text
2.2.63
(2024-06-25)
Fixed
- Fixed incorrect customer group detection for logged-in customers affecting price display
2.2.62
(2024-06-24)
Fixed
- Fixed search results not respecting Shared Catalog product assignments (B2B)
2.2.61
(2024-06-20)
Fixed
- Fixed category search results ignoring category permission restrictions
2.2.60
(2024-06-12)
Fixed
- Fixed empty URL for Knowledge Base articles in autocomplete Fast Mode
2.2.59
(2024-06-06)
Fixed
- Fixed Knowledge Base article URLs in search autocomplete results
2.2.58
(2024-05-23)
Fixed
- Fixed HTML tags appearing in Aheadworks Blog results on search results page
- Fixed Product Boost Rules not applying to GraphQL product search queries
2.2.57
(2024-05-08)
Fixed
- Fixed Aheadworks Blog search index compatibility issues
2.2.56
(2024-04-29)
Fixed
- Fixed Elasticsearch 8 compatibility issues
2.2.55
(2024-04-23)
Improvements
- Magento 2.4.7 compatibility updates
2.2.54
(2024-04-22)
Improvements
- Improved search query handling for OpenSearch — queries are now case-insensitive by default
2.2.53
(2024-04-17)
Improvements
- Updated translation file for Search Autocomplete
- Improved autocomplete suggestion caching
- Improved Quick Stat loading speed in admin panel
Fixed
- Fixed empty searchable attribute values being saved to the search index
2.2.52
(2024-03-22)
Fixed
- Fixed synonyms import not merging correctly with existing synonym groups
2.2.51
(2024-03-20)
Improvements
- Improved search results when "Search by child products" is enabled
Fixed
- Fixed regex error in searchable attributes mapping validation
2.2.50
(2024-03-12)
Fixed
- Fixed synonyms import not properly merging uppercase and lowercase terms into the same group
2.2.49
(2024-03-07)
Fixed
- Fixed undefined variable error in search results accuracy validator
2.2.48
(2024-03-07)
Improvements
- Improved admin search results validator — added sticky table header, weight labels, and truncation for long field values
2.2.47
(2024-03-06)
Features
- Product Boost Rule preview — see how rules affect product ranking before applying
Fixed
- Fixed Product Boost Rule saving without a store selected
2.2.46
(2024-03-04)
Fixed
- Fixed non-UTF-8 characters causing errors in the search results validator
2.2.45
(2024-03-04)
Improvements
- Extended debug/diagnostic options for OpenSearch engine
2.2.44
(2024-02-29)
Improvements
- Added logging for synonyms import process to help diagnose import issues
Fixed
- Fixed website and store scope not being set correctly during synonyms import
2.2.43
(2024-02-26)
Improvements
- Product index now excludes attributes not marked as "Use in Search" from the searchable list
Fixed
- Fixed URLs for Attribute and Search Terms indexes in Fast Mode
- Added template for Search Terms index in Full Size mode
- Fixed Attribute Index not available in Fast Mode
2.2.42
(2024-02-21)
Fixed
- Fixed Spell-Correction index issues with OpenSearch engine
2.2.41
(2024-02-20)
Features
- Product Boost Rule preview — visualize how a rule affects product ranking before applying it
2.2.40
(2024-02-19)
Fixed
- Fixed Magezon Page Builder content markup appearing in search autocomplete results
2.2.39
(2024-02-15)
Improvements
- Improved final price calculation for autocomplete product results
2.2.38
(2024-02-12)
Fixed
- Added missing template for Attribute index in autocomplete Full Size mode
2.2.37
(2024-02-07)
Improvements
- Increased
max_result_window limit for Elasticsearch indexes to support larger result sets
2.2.36
(2024-02-06)
Fixed
- Added synonym term validation to prevent invalid terms from breaking search indexes
2.2.35
(2024-01-26)
Fixed
- Fixed category URLs in search autocomplete (categories index) when URL rewrite is not set
- Fixed HTML tags appearing in category results in autocomplete Full Size mode
2.2.34
(2024-01-19)
Fixed
- Fixed time range selection for Product Boost Rules
- Fixed Elasticsearch 8 compatibility issues
2.2.33
(2024-01-05)
Improvements
- Search report logs are now automatically cleaned up by cron, retaining the last year of history
Fixed
- Fixed OpenSearch connection check failing
2.2.32
(2023-12-20)
Improvements
- Score Boost Rules now apply to search results in Fast Mode
2.2.31
(2023-12-18)
Fixed
- Fixed cached layout being served for landing pages instead of the correct page
2.2.30
(2023-12-18)
Improvements
- "Ignored Categories" selection on search index edit page now displays a tree view for easier navigation
Fixed
- Fixed potential error in text truncation logic
2.2.29
(2023-11-28)
Fixed
- Fixed HTML tags appearing in category search results in autocomplete
2.2.28
(2023-11-27)
Fixed
- Fixed PHP 8.2 compatibility issue
2.2.27
(2023-11-22)
Features
- Choose a price display strategy for autocomplete: "Direct" (fast, from database), "Short" (final price only via Magento), or "Default" (full price block with taxes, special prices, etc.)
Improvements
- Synonyms and stopwords now use CSV format instead of YAML for import/export
- Added default sorting option for Mirasvit Blog MX search results
2.2.26
(2023-11-21)
Fixed
- Fixed Blog MX search results showing posts from other stores
- Fixed bot detection service errors
2.2.25
(2023-11-06)
Fixed
- Fixed GraphQL search request errors
2.2.24
(2023-10-20)
Fixed
- Fixed Score Boost Rules not being applied correctly during indexation
2.2.23
(2023-10-17)
Improvements
- Added database indexes to score rule table for improved performance
2.2.22
(2023-10-16)
Improvements
- Optimized query for fetching review counts in autocomplete
- Added corrected search term to GraphQL response when spell correction is applied
2.2.21
(2023-10-09)
Fixed
- Fixed incorrect review count calculation in autocomplete search results
2.2.20
(2023-10-09)
Fixed
- Fixed error when creating a new search index
2.2.19
(2023-09-25)
Improvements
- Added primary key to score rule index table (resolves Adobe Commerce SWAT warning)
- Removed unnecessary blocks from landing pages
2.2.18
(2023-09-08)
Improvements
- Prevent removal of required attributes from search index configuration
- Added conflict checker for overlapping Score Boost Rules
Fixed
- Fixed compatibility with Mirasvit_Scroll (Ajax Scroll)
- Fixed "Search In" page value being duplicated in filter state
- Improved search by category functionality
2.2.17
(2023-08-29)
Fixed
- Fixed PHP type compatibility issues
2.2.16
(2023-08-21)
Improvements
- Completely rebuilt the admin search results validator, split into independent validators for accuracy and indexation checks
2.2.15
(2023-08-09)
Features
- Alternative price fetching strategy for autocomplete (via Magento) — slower but more reliable with taxes and third-party pricing extensions
2.2.14
(2023-08-08)
Fixed
- Fixed date attribute indexation error
2.2.13
(2023-08-04)
Fixed
- Fixed special characters breaking Elasticsearch indexing when content exceeds the field length limit
2.2.12
(2023-08-02)
Improvements
- Updated relevance boost strategy — increased differentiation between attributes with similar priority weights
2.2.11
(2023-08-01)
Fixed
- Fixed incorrect relevance calculation with OpenSearch engine
- Fixed Amasty Blog search index not filtering by post status
2.2.10
(2023-07-10)
Features
- Price slider filter in autocomplete Full Size mode
- Expandable/collapsible filter groups in autocomplete Full Size mode
Fixed
- Fixed filter sorting in autocomplete Full Size mode
2.2.9
(2023-07-04)
Improvements
- New Elasticsearch analyzer that significantly improves search quality without extra configuration
- New search relevance testing approach via GraphQL for better test coverage
- Updated popularity score algorithm to include bundle product sales
Fixed
- Fixed review count not loading in autocomplete
2.2.8
(2023-06-30)
Fixed
- Fixed product sorting by position on category pages with Sphinx engine
2.2.7
(2023-06-29)
Improvements
- Added store ID validation for autocomplete Fast Mode
Fixed
- Fixed product URLs in autocomplete using the wrong store view URL in multi-store setups
2.2.6
(2023-06-20)
Improvements
- Autocomplete Full Size mode now automatically switches to the next index tab if the current one returns zero results
Fixed
- Fixed conflict with Olegnax Infinity Scroll
- Fixed missing translations in autocomplete Full Size mode
2.2.5
(2023-06-16)
Improvements
- Minimum price display in autocomplete results
- Multi-Source Inventory (MSI) support for autocomplete stock status
Fixed
- Fixed Add to Cart button not working in autocomplete Full Size mode
2.2.4
(2023-06-15)
Improvements
- Updated autocomplete styling
- Additional diagnostic information in search results debugger
Fixed
- Fixed search input focus issue in Full Size mode
- Added missing translatable phrases
2.2.3
(2023-06-02)
Fixed
- Fixed full page cache serving stale search results
- Fixed indexing failure when product attribute value exceeds 32 KB
2.2.2
(2023-05-29)
Improvements
- Added "Apply All" button for Score Boost Rules for bulk application
- Improved CLI command for importing synonyms
2.2.1
(2023-05-16)
Improvements
- Revamped bot detector — uses both a built-in keyword dictionary and stopwords to filter bot queries. Bot-triggered searches still return results but are excluded from search term history and reports.
2.2.0
(2023-05-15)
Improvements
- Updated search GraphQL query syntax
Fixed
- Fixed multi-word synonyms not being applied correctly
- Fixed error when search term contains only stopwords
2.1.12
(2023-08-03)
Fixed
- Fixed SKU analyzer configuration issue
2.1.11
(2023-05-08)
Improvements
- Improved Elasticsearch search query for better relevance ranking
Fixed
- Fixed potential price formatting exception during reindex
2.1.10
(2023-05-02)
Fixed
- Fixed wrong pagination on Magento 2.4.5
2.1.9
(2023-04-17)
Improvements
- Added support for "cat" parameter in search autocomplete for category-scoped search
Fixed
- Fixed incorrect number of results in Advanced Search
2.1.8
(2023-04-10)
Improvements
- Refined CSS styles for autocomplete Full Size mode
2.1.7
(2023-04-10)
Improvements
- CSS improvements for autocomplete Full Size mode display
2.1.6
(2023-04-04)
Fixed
- Fixed autocomplete Fast Mode showing products that are not visible individually
2.1.5
(2023-03-29)
Fixed
- Fixed prices not displaying correctly in autocomplete when tax is included
- Fixed product thumbnail image issues in autocomplete
2.1.4
(2023-03-27)
Fixed
- Fixed empty product names in autocomplete (Adobe Commerce / Enterprise Edition only)
2.1.3
(2023-03-27)
Features
- Magefan Blog support in autocomplete Fast Mode
2.1.2
(2023-03-24)
Features
- Option to include or exclude empty categories from search indexation
2.1.1
(2023-03-20)
Fixed
- Fixed Score Boost Rules not applying when sorting is not set to relevance
- Fixed typeahead provider JSON decode error
2.1.0
(2023-03-16)
Features
- Option to enable/disable indexation of widgets in page content
Improvements
- Significantly improved indexation speed with Fast Mode enabled
- Revamped Elasticsearch search queries for better relevance
Fixed
- Fixed search not finding terms containing periods (e.g., "v2.0")
- Fixed import path for stopwords and synonyms files
- Fixed conflict with Mirasvit_Scroll module
- Fixed PHP 8.2 compatibility issues
2.0.97
(2023-02-23)
Features
- Mageplaza Blog support in autocomplete Fast Mode
2.0.96
(2023-02-17)
Fixed
- Fixed undefined offset error in autocomplete provider
2.0.95
(2023-02-15)
Fixed
- Fixed Elasticsearch "limit reached on the number of clauses" error with large synonym sets
- Fixed indexation error "analyzer/trigram has not been configured in mappings"
2.0.94
(2023-02-06)
Fixed
- Fixed GraphQL returning wrong total number of results when spell correction is applied
2.0.93
(2023-02-03)
Fixed
- Fixed compatibility with Amasty_Mage245Fix module
- Fixed Sphinx search engine sorting by name issue
2.0.91
(2023-01-30)
Fixed
- Fixed incorrect search results when using synonyms
- Added missing translatable phrases
2.0.90
(2023-01-18)
Fixed
- Fixed type error with MySQL search engine
2.0.89
(2023-01-12)
Fixed
- Fixed pagination and "View All" link in autocomplete Full Size mode
2.0.88
(2023-01-04)
Fixed
- Fixed "Search In" category filter showing categories from other stores
2.0.87
(2022-12-21)
Fixed
- Fixed Elasticsearch "Max Clause" error with complex queries
- Fixed product search weights not being applied correctly
2.0.86
(2022-12-05)
Fixed
- Fixed error saving search autocomplete configuration on Magento 2.4.5
2.0.85
(2022-11-09)
Fixed
- Fixed GraphQL error with
getTotal function
2.0.84
(2022-11-09)
Improvements
- Improved synonym relevance weighting in Elasticsearch queries
2.0.83
(2022-11-08)
Fixed
- Fixed error with large synonym sets exceeding query size limits
2.0.82
(2022-11-04)
Improvements
- Improved search Debug Toolbar with detailed diagnostic information
Fixed
- Fixed GraphQL misspell/spell correction handling
2.0.81
(2022-10-13)
Fixed
- Fixed GraphQL schema cleanup (removed unused fields and references)
2.0.80
(2022-10-10)
Fixed
- Fixed GraphQL objects missing
__typename field
2.0.79
(2022-09-28)
Fixed
- Fixed "Search In" category filter conditions
- Fixed category search compatibility with Amasty Finder
2.0.78
(2022-09-26)
Fixed
- Fixed category search compatibility with Amasty ShopBy
2.0.77
(2022-09-21)
Features
- Added search on category page — customers can search within a specific category using a dedicated search bar
2.0.76
(2022-09-20)
Fixed
- Fixed Sphinx engine indexing issues
- Fixed Magento Search Terms index not indexing correctly
- Fixed autocomplete scroll behavior jumping to top of results
2.0.75
(2022-09-08)
Fixed
- Fixed wrong offset identifier in autocomplete Fast Mode causing missing results
2.0.74
(2022-09-08)
Features
- Optional sidebar filters and pagination for autocomplete Full Size layout
Fixed
- Fixed duplicate product titles in autocomplete Full Size layout
- Fixed date format error in Score Boost Rules
2.0.73
(2022-08-31)
Fixed
- Fixed automatic price navigation step calculation error
- Fixed GraphQL compatibility issues
2.0.72
(2022-08-26)
Features
- "Search In" functionality — filter search results within a specific category
- Multiple keywords support for search landing pages
Fixed
- Fixed layered navigation showing on non-product search result tabs
2.0.71
(2022-08-19)
Features
- Misspell correction in autocomplete Fast Mode with Elasticsearch engine
Fixed
- Fixed "Headers already sent" error on search landing pages
2.0.70
(2022-08-15)
Fixed
- Magento 2.4.5 compatibility fixes
2.0.69
(2022-08-11)
Improvements
- Changed 404-to-search redirect from 301 (permanent) to 302 (temporary) to avoid browser caching issues
Fixed
- Fixed synonyms processing error
2.0.68
(2022-08-08)
Features
- Module uninstall command support
- Sphinx engine now supports catalog queries with default filters and sorting
Improvements
- Restored autocomplete Fast Mode for Sphinx engine
Fixed
- Fixed autocomplete images using admin domain in Fast Mode
- Fixed MySQL engine wildcard filter builder error
- Fixed blog index indexing issues
- Fixed synonyms and stopwords import
2.0.67
(2022-07-25)
Improvements
- Long-tail applicable attributes are now detected automatically
- Added categories blacklist for category search index
Fixed
- Fixed search results weighting calculation
- Fixed synonyms not matching correctly
- Fixed autocomplete Fast Mode using wrong store-specific price
- Fixed Mageplaza Blog Post indexing issues
2.0.66
(2022-07-05)
Fixed
- Fixed category search results using incorrect URLs in autocomplete
2.0.65
(2022-06-30)
Improvements
- Added total results count and aggregations to GraphQL search response
Fixed
- Fixed search query logger parameters
2.0.64
(2022-06-21)
Fixed
- Fixed "Unknown column 'search_weight'" error on first
setup:upgrade run
2.0.63
(2022-06-20)
Features
- Ajax "Add to Cart" option in search autocomplete
- ASCII folding is now configurable (optional)
Improvements
- ⚠️ Switched to declarative database schema
- Removed legacy search synonyms table for Magento 2.4+ (uses native synonyms)
Fixed
- Fixed GraphQL spell correction compatibility
- Fixed price attribute in autocomplete Fast Mode
2.0.62
(2022-05-27)
Fixed
- Fixed Long Tail SKU filter for GraphQL queries
- Fixed CMS Page indexing issues
2.0.61
(2022-05-19)
Improvements
- Improved search synonyms matching functionality
2.0.60
(2022-05-17)
Improvements
- Updated module-core dependency
2.0.59
(2022-05-12)
Fixed
- Fixed omit tabs functionality not working correctly
- Fixed "Undefined index" error in GraphQL for Category and Attribute search indexes
2.0.58
(2022-05-09)
Features
- Added description field to search landing pages
Fixed
- Fixed autocomplete stock status translation
- Fixed GraphQL product search pagination
- Fixed GraphQL CMS page index
2.0.57
(2022-04-20)
Fixed
- Fixed child products not being indexed correctly
- Fixed MySQL search engine compatibility
2.0.56
(2022-04-06)
Fixed
- Fixed doubled URL suffix in search autocomplete results
- Fixed version comparison compatibility with patched Magento versions
2.0.55
(2022-04-04)
Fixed
- Fixed search index status not being applied correctly
- PHP 8.1 and Magento 2.4.4 compatibility
2.0.54
(2022-03-21)
Fixed
- Fixed case sensitivity issue with search index names
- Fixed Amasty Blog Post instant provider
- Fixed Elasticsearch index prefix not being unique across installations
2.0.53
(2022-03-03)
Features
- Magento Search Query (popular search terms) now available as a search index in autocomplete
Fixed
- Fixed Mageplaza Blog Post indexing
- Fixed Blackbird Advanced Content indexing
- Fixed Fast Mode config not updating after reindex
2.0.52
(2022-01-17)
Fixed
- Fixed empty autocomplete placeholder showing when no search term entered
2.0.51
(2022-01-04)
Features
- Filter statement support for GraphQL search queries
Fixed
- Fixed search results applier for MySQL and Sphinx engines
2.0.50
(2021-12-20)
Fixed
- Fixed bot detector service conditions
- Fixed indexing issue with "Add Category Data" option enabled
- Fixed query service transliteration functionality
2.0.49
(2021-12-16)
Fixed
- Fixed "Price Navigation Step - Calculation Automatic" error for MySQL and Sphinx engines
- Fixed IP filter for bot detection service
2.0.48
(2021-12-15)
Improvements
- Improved bot/hack attempt detection
- Added accented character support for search queries
2.0.47
(2021-12-13)
Features
- Sorting support for GraphQL search queries
Fixed
- Fixed indexing issue with "Add Custom Options" enabled
- Fixed stock status display in search autocomplete
2.0.46
(2021-12-09)
Fixed
- Fixed GraphQL search pagination and sorting issues (page size and current page variables)
2.0.45
(2021-12-08)
Features
- Stock status indicator in search autocomplete results
Fixed
- Fixed "Unknown column 'search_index.sku' in order clause" error
2.0.44
(2021-11-25)
Features
- Quick Data Bar — at-a-glance search performance statistics in admin
Fixed
- Fixed indexing issue with "Add Custom Options" enabled
- Fixed landing page generating wrong recommendation links
- Fixed Amasty Blog indexing issues
2.0.43
(2021-11-08)
Improvements
- Updated search autocomplete styles for better appearance
2.0.42
(2021-11-04)
Fixed
- Restored VES Blog search index support
2.0.41
(2021-10-13)
Fixed
- Fixed GraphQL search query returning incorrect results
2.0.40
(2021-10-05)
Fixed
- Fixed autocomplete showing results for empty search terms
- Fixed product URLs pointing to admin in Fast Mode
- Fixed hack attempt detector false positives
- Fixed missing child products when "Search by child product" option is enabled
- Fixed autocomplete filters rendering without options
- Fixed child products indexing issue on Adobe Commerce (Enterprise Edition)
2.0.39
(2021-09-02)
Fixed
- Fixed error when price range starts from zero
- Fixed missing URLs on brand search index results
- Fixed search by child products returning incomplete results
2.0.38
(2021-08-13)
Features
- Mirasvit Brand search index — search and display brand pages in autocomplete
Improvements
- Product images in autocomplete now use the Magento
upsell_products_list image size instead of hardcoded dimensions
2.0.37
(2021-08-09)
Improvements
- Improved Fast Mode indexing speed
- Added filters to autocomplete Fast Mode Full Size layout
Fixed
- Fixed synonyms import errors being silently ignored
- Fixed sorting issues on Adobe Commerce with MySQL engine
- Fixed synonyms import failures
- Fixed WordPress blog results missing taxonomy terms in URLs
- Fixed type error on empty sort order with MySQL engine
- Fixed missing score rules table after fresh install
2.0.36
(2021-07-09)
Fixed
- Fixed attribute collection error in autocomplete config builder
- Fixed error creating Elasticsearch request
- Fixed autocomplete Fast Mode wildcard search issues
- Fixed various Fast Mode stability issues
2.0.35
(2021-06-30)
Features
- Mirasvit Blog search index support
Fixed
- Fixed misspell Elasticsearch indexing errors
- Fixed SM AttributeSearch compatibility
- Fixed autocomplete displaying Page Builder markup instead of clean text
- Fixed misspell indexing issues
- Fixed validator error when search indexes are missing
2.0.34
(2021-05-27)
Fixed
- Fixed child products not searchable with MySQL engine
- Fixed cron-based reindex issues
- Optimized misspell indexing process
- Fixed wrong "Add to Cart" URL in autocomplete
- Fixed environment emulation nesting error
- Fixed autocomplete expand/collapse on mobile devices
2.0.33
(2021-04-19)
Fixed
- Fixed wrong ACL permissions for synonyms management
- Fixed fallback search causing memory issues
- Fixed product sorting with MySQL search engine
- Fixed pagination issues
- Fixed cron-based reindex failures
2.0.32
(2021-04-19)
Improvements
- Improved mobile styles for autocomplete
Fixed
- Fixed PHP converting integer index keys causing sorting issues
2.0.31
(2021-04-13)
Fixed
- Fixed setup:upgrade notices
- Fixed autocomplete not canceling previous AJAX request when new search is typed
2.0.30
(2021-03-22)
Fixed
- Fixed Cyrillic characters causing misspell reindex failures
- Fixed missing Sphinx management buttons in admin
- Fixed search results keyword highlighting issues
2.0.29
(2021-03-17)
Fixed
- Fixed translation placeholders not being replaced in autocomplete
- Fixed search input disappearing on mobile
- Fixed Fast Mode returning incomplete results
- Fixed Page Builder content indexing issues
- Fixed landing page redirect not being enforced
- Fixed incorrect product URLs in autocomplete
2.0.28
(2021-03-03)
Fixed
- Fixed Score Boost Rules inline script not being applied when rules exist
- Fixed 404-to-search redirect handling
2.0.27
(2021-02-22)
Features
- Blackbird ContentManager search index support
Fixed
- Fixed Aheadworks Blog index issues
- Fixed Magezon Page Builder content not being processed for indexing
- Fixed "Add to Cart" button translation and cookie handling
2.0.26
(2021-02-04)
Fixed
- Fixed pagination issues
- Fixed Boost Rules only applying to first page of results
- Fixed missing synonyms in Fast Mode
- Fixed wrong argument type for instant provider
- Fixed GraphQL search issues
- Fixed negative individual search weight not being applied
- Fixed synonyms not matching numeric terms
- Fixed autocomplete failing when "session expired" error occurs
2.0.25
(2021-01-28)
Fixed
- Fixed Amasty Blog search compatibility
- Fixed JSON decoding failures after Magento update
- Fixed Magefan Blog reindex issues
- Fixed no results for search terms containing dashes (e.g., "part-number")
- Fixed numeric attribute search issues
- Fixed "Add to Cart" button cookie value
2.0.24
(2021-01-20)
Fixed
- Fixed category search index indexation errors
- Added verbose output for indexation issues
- Fixed Magento Marketplace compatibility (require_once detection)
2.0.23
(2021-01-19)
Fixed
- Fixed incorrect search term highlighting and missing highlight entries
- Fixed MySQL engine
group_concat_max_len limit for long attribute values
2.0.22
(2021-01-13)
Fixed
- Fixed Sphinx engine compatibility with Magento Marketplace
2.0.21
(2021-01-12)
Fixed
- Fixed unable to edit category tree conditions in Score Boost Rules
2.0.20
(2021-01-11)
Fixed
- Fixed incorrect synonyms data from instant provider
- Fixed missing categories filter with MySQL engine
- Fixed search results showing all products on one page instead of paginating
2.0.19
(2021-01-06)
Fixed
- Fixed search typeahead not suggesting terms
- Fixed match phrase processing error
- Fixed no autocomplete results showing after fresh install
- Fixed blank search results page when category index is first tab with no results
2.0.18
(2020-12-17)
Fixed
- Restored debug toolbar template
2.0.17
(2020-12-14)
Fixed
- Fixed missing product price in autocomplete Fast Mode
2.0.16
(2020-12-10)
Improvements
- Added confirmation dialog when resetting search indexes
2.0.15
(2020-12-09)
Fixed
- Fixed "Undefined offset" error in misspell functionality
- Fixed issues managing autocomplete search indexes
2.0.14
(2020-11-26)
Fixed
- Fixed Score Boost Rules not working with Elasticsearch engine
- Fixed type error during autocomplete Fast Mode reindex
2.0.13
(2020-11-25)
Features
- Mirasvit Knowledge Base tags are now searchable attributes
Fixed
- Fixed error processing numeric search attributes in Fast Mode
2.0.12
(2020-11-24)
Fixed
- Fixed numeric attributes search query processing
- Restored "Reset Store Indexes" button in admin
2.0.11
(2020-10-30)
Features
- GraphQL search support — full search functionality available via GraphQL queries, including product, category, CMS, attribute, and blog post results
Fixed
- Fixed short search terms returning no results
- Fixed Amasty Parts Finder compatibility
2.0.10
(2020-10-20)
Improvements
- 404-to-search redirects no longer save the 404 URL as a search term in search history
Fixed
- Fixed indexation issues on Magento 2.4.1
- Fixed error when redirecting an empty search term to homepage
2.0.9
(2020-10-06)
Improvements
- Improved spell correction accuracy and performance
- Improved spell correction messages and notifications
Fixed
- Fixed multi-index search issues
- Fixed suggester missing search term
- Fixed Sphinx "Reset" action clearing custom base path folder
2.0.8
(2020-10-05)
Fixed
- Fixed Sphinx and MySQL search pagination
- Fixed Elasticsearch 6 Fast Mode compatibility
2.0.7
(2020-09-21)
Fixed
- Restored third-party module search indexes
2.0.6
(2020-09-17)
Fixed
- Fixed attribute search index issues
2.0.5
(2020-09-14)
Fixed
- Fixed CMS page index issues
- Fixed multi-index support
- Fixed Amasty Part Finder compatibility
- Fixed product filter issues
2.0.4
(2020-09-02)
Fixed
- Fixed synonyms being discarded on landing page search results
- Added missing translations
2.0.3
(2020-08-31)
Features
- Products Boost Rules (renamed from Score Boost Rules) — boost or suppress products in search results based on configurable rules
Improvements
- Added search debug service for troubleshooting
Fixed
- Fixed stopwords import issues
- Fixed Amasty Parts Finder compatibility
2.0.2
(2020-08-26)
Fixed
- Fixed Sphinx indexation issues
- Fixed MySQL search engine errors
- Fixed Elasticsearch 7 connection issues
- Restored WordPress Blog search index
- Fixed category indexation
- Fixed string processor errors
2.0.1
(2020-08-14)
Improvements
Fixed
- Fixed fresh installation errors
- Fixed Sphinx and Elasticsearch connection issues
- Fixed category indexation problems
- Fixed stopwords handling
- Fixed SKU field deletion protection
2.0.0
(2020-08-04)
Improvements
- ⚠️ Starting with 2.0.0 — module-search-ultimate is the single unified package for Magento 2.4+
- ⚠️ Versions up to 1.1.7 support Magento 2.1–2.3 via separate submodules. Magento 2.4+ uses only the
mirasvit/module-search-ultimate package.
Fixed
- "Products in categories" and "Popular suggestions" indexes are no longer available in Magento 2.4+ (deprecated by Magento core changes)
Legacy Submodule Changelogs
The following changelogs cover the individual submodules that were merged into module-search-ultimate starting with version 2.0.0. They are preserved here for historical reference.
Search [mirasvit/module-search]
1.0.151
(2020-09-17)
Fixed
- Fixed CMS page index with widget indexing
1.0.150
(2020-09-07)
Fixed
- Fixed Mageplaza_AjaxLayer sorting
- Fixed non-searchable attributes being included in index
- Fixed Codazon_ajaxlayerednavpro compatibility
- Fixed multiple attribute index status with Elasticsearch
- Fixed native Elasticsearch 7 compatibility
- Fixed 404-to-search redirect looping on 404 URLs
- Fixed query highlight issues
1.0.149
(2020-06-16)
Improvements
- Added incompatibility notice for Fast Mode Autocomplete options
Fixed
- Fixed special characters appearing in highlighted results
- Fixed Mana_layerednavigationajax paging compatibility
- Fixed incorrect stemming behavior
1.0.148
(2020-06-02)
Fixed
- Fixed "Array to string conversion" error on reindex
- Fixed Amasty Blog posts links
- Fixed unexpected numeric results
- Fixed environment emulation nesting error
- Fixed search results tabs display
- Fixed category search returning zero relevance
1.0.147
(2020-04-30)
Fixed
- Fixed category reindex issue on Magento 2.3.5 Enterprise
- Fixed select attributes being overridden
1.0.146
(2020-04-23)
Fixed
- Fixed Score Boost Rules indexing issues
- Fixed suggested search terms with MySQL entries
- Fixed CMS pages indexing
- Fixed WeltPixel LRN compatibility
1.0.145
(2020-04-14)
Fixed
- Fixed WeltPixel LRN compatibility
- Fixed CMS pages indexing
- Fixed suggested search terms filtering
- Fixed Score Boost Rules indexing
1.0.144
(2020-04-07)
Fixed
- Fixed JSON-encoded values in Elasticsearch indexer
- Fixed search results highlight preserving original case
- Fixed multi-select attributes reindex when "Search by child products" is disabled
- Fixed empty categories being indexed
1.0.143
(2020-03-18)
Fixed
- Fixed bundle products indexing (child products now included by default)
- Improved Score Rules indexing speed
- Fixed Magento SharedCatalog search
- Fixed popular suggestions wildcard exceptions
- Fixed upgrade schema issues
1.0.142
(2020-03-05)
Fixed
- Fixed serialization issue on Magento 2.1
1.0.141
(2020-02-18)
Fixed
- Fixed plugin loadEntities compatibility issue
1.0.140
(2020-02-13)
Fixed
- Fixed SQL query log accidentally displayed on frontend
1.0.139
(2020-02-12)
Fixed
- Fixed "Environment emulation nesting is not allowed" error with CMS page index
- Fixed duplicate
mst_search_weight entry on setup:upgrade
- Fixed search highlight replacing content in wrong placeholder
1.0.138
(2020-02-03)
Fixed
- Magento 2.3.4 compatibility
1.0.137
(2019-12-17)
Fixed
- Fixed search results highlight behavior
1.0.136
(2019-11-28)
Fixed
- Fixed search results highlight issues
1.0.135
(2019-11-27)
Fixed
- Fixed unicode character handling in search
1.0.134
(2019-11-25)
Fixed
- Fixed empty results display for empty or minimum-length search queries
1.0.133
(2019-11-13)
Fixed
- Fixed multi-store search redirect not working correctly
1.0.132
(2019-11-11)
Fixed
- Fixed class declaration conflicts
- Fixed undefined Elasticsearch factories
- Fixed Magento 2.1.12 EE setup error
1.0.131
(2019-10-16)
Fixed
- Magento 2.3.3 compatibility
- Fixed Score Rule not being applied
1.0.130
(2019-10-09)
Fixed
- Fixed individual search weight not saving
1.0.129
(2019-10-09)
Fixed
- Added informative error messages for synonyms and stopwords import failures
- Fixed duplicate CMS page index options
- Fixed individual search weight not saving
1.0.128
(2019-09-10)
Fixed
- Fixed validator form on Magento 2.3.0
1.0.127
(2019-09-03)
Fixed
- Fixed filtering of Synonyms, Stopwords, and Score Rules in admin grids
1.0.126
(2019-08-28)
Improvements
- Improved synonyms import process
1.0.125
(2019-08-27)
Fixed
- Fixed YAML parsing issues in synonyms/stopwords import
1.0.124
(2019-07-30)
Fixed
- Fixed search results validator issues
- Fixed Advanced Search on Magento 2.3.2
1.0.123
(2019-07-08)
Features
- Fishpig Glossary search index support
Fixed
- Fixed Magento 2.3.2 Advanced Search compatibility
1.0.122
(2019-06-13)
Fixed
- Fixed mass update of search weights
- Fixed compilation issue with TemplateMonster/AjaxCatalog
- Fixed Magento 2.3.1 Elasticsearch compatibility
- Fixed doubled field values in CMS index
1.0.121
(2019-04-24)
Fixed
- Fixed Fast Mode initialization issues
1.0.120
(2019-04-08)
Features
- Autocomplete Fast Mode config file auto-generated on search reindex
Fixed
- Fixed similar results appearing in multiple attribute indexes
- Fixed environment emulation nesting error
1.0.119
(2019-03-21)
Fixed
- Fixed Manadev compatibility
1.0.118
(2019-03-19)
Fixed
- Fixed Manadev compatibility
1.0.117
(2019-01-04)
Fixed
- Fixed JS error on index attributes configuration page
- Fixed conflict with Mageplaza_LayeredNavigation
1.0.116
(2018-12-29)
Features
- Search by Aheadworks Blog Post tags
Improvements
- Mageplaza Ajax Layer compatibility
Fixed
- Fixed compatibility with TemplateMonsters_AjaxCatalog
1.0.114
(2018-12-25)
Improvements
- Renamed
search_weight column to mst_search_weight to prevent conflicts after module disable
- BlueFoot compatibility
1.0.113
(2018-12-14)
Fixed
- Fixed saving index attributes for new indexes
1.0.112
(2018-12-13)
Features
- Product image in search results is now clickable
Fixed
- Fixed store switcher URL issues
1.0.111
(2018-12-06)
Fixed
- Fixed store switcher on multi-store search results
1.0.110
(2018-12-06)
Fixed
- Fixed store switching on multi-store search results
1.0.109
(2018-12-05)
Fixed
- Fixed search weight being lost during mass product update
1.0.108
(2018-11-29)
Fixed
- Magento 2.3 compatibility
- Fixed incorrect results for queries with special characters
1.0.107
(2018-11-15)
Fixed
- Fixed search results caching
- Fixed bundle products appearing in results when "Search by child products" was disabled
1.0.106
(2018-11-13)
Fixed
- Fixed "Push out-of-stock products to bottom" not working correctly
1.0.105
(2018-11-13)
Improvements
- Added migration validation for WeltPixel_CmsBlockScheduler
Fixed
- Fixed class generation issue on Magento Cloud
- Fixed highlight issue with special characters
1.0.104
(2018-11-05)
Fixed
- Fixed styling issue with Aheadworks Blog search results
1.0.103
(2018-11-05)
Fixed
- Fixed search results highlighting issues
1.0.102
(2018-11-02)
Fixed
- Fixed PHP 5.6 syntax error
1.0.101
(2018-10-29)
Features
- Search results validator — detects different search engine settings across environments
Fixed
- Fixed products index edit page errors
1.0.100
(2018-10-15)
Fixed
- Fixed slow admin page load caused by JS rendering time
1.0.99
(2018-10-12)
Fixed
- Fixed bundled products indexing
- Fixed search results highlighter
1.0.98
(2018-10-09)
Fixed
- Fixed reindex issue with
mirasvit:search:reindex command
1.0.97
(2018-10-09)
Fixed
- Fixed autocomplete provider errors
- Fixed search results highlighter
1.0.96
(2018-10-03)
Fixed
- Fixed attribute configuration issues
1.0.95
(2018-10-03)
Fixed
1.0.94
(2018-10-01)
Improvements
- Search results from other indexes (CMS, Blog, etc.) are shown alongside product results when product result count is low
1.0.93
(2018-09-28)
Features
- Category thumbnail images in search results
1.0.92
(2018-09-26)
Fixed
- Fixed Blackbird ContentManager compatibility
1.0.91
(2018-09-26)
Features
- Blackbird ContentManager search index
1.0.90
(2018-09-21)
Fixed
- Fixed multi-select attribute indexing
1.0.89
(2018-09-21)
Fixed
- Fixed module disable plugin error
1.0.88
(2018-09-21)
Improvements
- Search results validator — detects conflicts with other search extensions
1.0.87
(2018-09-20)
Features
1.0.86
(2018-09-20)
Fixed
- Fixed reindex issue with native MySQL engine
- Fixed error after module disable
1.0.85
(2018-09-18)
Fixed
- Fixed unavailable index type on index edit screen
1.0.84
(2018-09-17)
Features
- Multiple Catalog Attribute indexes — create separate attribute indexes for different attribute groups
1.0.83
(2018-09-11)
Fixed
- Fixed ScoreServiceInterface error
1.0.82
(2018-09-10)
Features
- Score Boost Rules — boost or suppress products based on configurable conditions
Fixed
- Fixed Score Rule "Save & Continue" button for new rules
1.0.81
(2018-09-06)
Fixed
- Fixed admin ACL permissions
1.0.80
(2018-09-06)
Features
- Score Boost Rules for product search ranking
- Added "Apply" button to Score Rule edit form
Fixed
- Fixed UI component load error on Magento 2.1.2
- Fixed SKU weight configuration
1.0.79
(2018-08-27)
Improvements
- Custom search weight application logic
Fixed
- Fixed attribute synchronization issues
1.0.78
(2018-08-01)
Features
Fixed
- Fixed SSL certificate verification failure in autocomplete speed validator
1.0.77
(2018-06-08)
Fixed
- Fixed empty node error in search configuration
1.0.76
(2018-05-17)
Fixed
- Fixed "Search only by active categories" option
- Fixed incorrect Sold QTY attribute settings
1.0.75
(2018-03-06)
Features
- Search results validator and search speed test
- Relevance adjustment based on sold items quantity
1.0.74
(2018-03-06)
Fixed
- Fixed product ordering issues
1.0.73
(2018-03-06)
Features
- Mirasvit Gift Registry search index
1.0.72
(2018-02-13)
Features
- Aheadworks Blog search index
1.0.71
(2018-02-12)
Fixed
1.0.70
(2018-02-01)
Fixed
- Fixed special characters (%) in suggested queries
1.0.69
(2018-01-30)
Fixed
- Fixed multi-store search results
1.0.68
(2018-01-16)
Fixed
- Fixed translations in suggestion template
1.0.67
(2018-01-15)
Improvements
- Search engine status visualization in admin
Fixed
- Fixed Mageplaza Blog index
1.0.66
(2018-01-09)
Fixed
- Fixed autocomplete issues
1.0.65
(2017-12-14)
Fixed
- Magento 2.2.2 — removed symfony/yaml requirement
1.0.64
(2017-12-14)
Improvements
- Strip HTML tags from CMS Pages index content
1.0.63
(2017-12-13)
Improvements
- Improved search within categories functionality
1.0.62
(2017-12-06)
Fixed
- Fixed performance issues with complex synonyms
1.0.61
(2017-12-01)
Improvements
- Selective reindex:
bin/magento mirasvit:search:reindex --store <id> --index <identifier>
1.0.60
(2017-12-01)
Fixed
- Fixed product sorting issues
1.0.59
(2017-11-29)
Fixed
- Added store filter to Magefan Blog index
1.0.58
(2017-11-21)
Improvements
- Added migration script to convert serialized values to JSON format
1.0.57
(2017-11-20)
Fixed
- Fixed attribute joining issues
1.0.56
(2017-11-17)
Fixed
- Fixed long-tail expression form
1.0.55
(2017-10-17)
Improvements
- Toggle to show/hide suggested search terms on search results page
1.0.54
(2017-10-17)
Fixed
- Fixed data mapper issues
- Fixed JSON decode errors
1.0.53
(2017-10-12)
Features
Fixed
- Fixed indexed text being incorrectly lowercased
1.0.52
(2017-10-05)
Features
- Match Mode selection — choose between AND or OR matching for search terms
1.0.51
(2017-09-28)
Fixed
- Fixed unserialize issues (migrated to JSON)
1.0.50
(2017-09-27)
Fixed
- Magento 2.2 compatibility
- Fixed No Results page issues
- Fixed UI error on index edit page
1.0.47
(2017-09-08)
Fixed
- Fixed product data mapper issues
1.0.46
(2017-09-06)
Fixed
- Fixed Search Report display
- Fixed HTML tag filtering
1.0.45
(2017-09-05)
Fixed
- Improved HTML tag stripping in indexed content
1.0.44
(2017-09-04)
Improvements
- Added links to documentation in admin
Fixed
- Fixed search weight synchronization
1.0.43
(2017-08-31)
Fixed
- Fixed empty results in search reports
1.0.42
(2017-08-14)
Fixed
- Fixed tab display issues
- Fixed store environment emulation
1.0.41
(2017-08-08)
Fixed
- Fixed slow JS rendering in admin backend
1.0.40
(2017-08-04)
Features
- Sort products by stock status
1.0.39
(2017-07-28)
Fixed
- Fixed synonyms processing
1.0.37
(2017-07-21)
Fixed
- Fixed responsive styles for search index tabs
- Fixed synonyms and stopwords not being lowercased on save
- Fixed blog indexation issues
1.0.36
(2017-06-30)
Fixed
- Fixed local synonyms/stopwords dictionary loading
1.0.35
(2017-06-27)
Improvements
- Added URL parameters for WordPress Blog search results
Fixed
- Fixed search weight issues
1.0.34
(2017-06-22)
Fixed
- Fixed index invalidation issues
1.0.33
(2017-06-21)
Features
- Force sort order option for products in search results
1.0.32
(2017-06-19)
Fixed
- Fixed Bundled Products indexing on Enterprise Edition
- Fixed synonyms processing
1.0.31
(2017-06-19)
Fixed
1.0.30
(2017-06-16)
Fixed
- Fixed attribute configuration
- Fixed attribute synchronization
- Fixed index status not updating after property/attribute changes
1.0.27
(2017-06-07)
Improvements
- Added media type filtering for 404-to-search redirects
Fixed
- Fixed installation script
1.0.26
(2017-06-07)
Improvements
Fixed
- Fixed Enterprise Edition bundle product issues
1.0.25
(2017-05-29)
Fixed
1.0.24
(2017-05-24)
Fixed
- Fixed Replace Words functionality
1.0.23
(2017-05-24)
Improvements
- Renamed "Indices" to "Indexes" across the UI
1.0.22
(2017-05-23)
Fixed
- Fixed local synonyms/stopwords file loading
1.0.21
(2017-05-18)
Improvements
- Added long-tail search hint for admin configuration
Fixed
- Fixed search_weight attribute issues
- Fixed custom search weight application
1.0.20
(2017-05-04)
Improvements
- Reindex progress visualization
Fixed
- Fixed engine status checker
1.0.19
(2017-04-26)
Features
- Mageplaza Blog search index
Fixed
- Fixed index properties saving
1.0.18
(2017-04-18)
Fixed
- Fixed CMS page reindex issues
1.0.17
(2017-04-18)
Fixed
- Fixed custom search weight issues
1.0.16
(2017-04-13)
Fixed
- Fixed EngineResolver path
1.0.15
(2017-04-12)
Fixed
- Fixed EngineResolver path
1.0.14
(2017-04-10)
Fixed
- Fixed Enterprise Edition reindex issues
- Fixed autocomplete provider
1.0.13
(2017-04-07)
Fixed
- Fixed Attribute index error
1.0.12
(2017-04-06)
Fixed
- Fixed installation script
1.0.11
(2017-04-06)
Fixed
- Fixed saving index properties
1.0.10
(2017-04-06)
Improvements
- Added prefix for search index database tables
1.0.9
(2017-04-05)
Fixed
- Fixed clean installation errors
1.0.8
(2017-04-05)
Improvements
- Changed locale resolver for stemming
Fixed
- Fixed autocomplete provider
1.0.7
(2017-04-04)
Fixed
- Fixed autocomplete issues
- Fixed stopwords import
1.0.6
(2017-04-04)
Fixed
1.0.5
(2017-03-31)
Fixed
- Fixed installation issues
1.0.4
(2017-03-31)
Fixed
1.0.3
(2017-03-09)
Fixed
1.0.2
(2017-03-06)
Improvements
- Improved synonyms import interface
Fixed
- Fixed synonyms processing
1.0.1
(2017-03-03)
Improvements
Fixed
1.0.0
(2017-02-17)
Features
- Cloud service for synonyms and stopwords dictionaries
- Initial release (split from mirasvit/module-search-sphinx)
Fixed
- Fixed out-of-stock product filtering
Search Sphinx [mirasvit/module-search-sphinx]
1.1.56
(2020-10-05)
Fixed
- Fixed "Reset Sphinx" action clearing custom base path folder
1.1.55
(2020-09-07)
Improvements
- Added notification for Search Autocomplete Fast Mode
Fixed
- Fixed Sphinx 3.1.1 compatibility
1.1.54
(2020-05-14)
Improvements
- Improved Sphinx status checking
Fixed
- Fixed Fast Mode missing index
1.1.53
(2020-04-13)
Improvements
- Improved Sphinx status checking
Fixed
- Fixed missing "Add to Cart" button in Fast Mode
1.1.52
(2020-03-03)
Fixed
- Fixed autocomplete spinner not hiding when no results found
- Fixed fallback engine on category view request
1.1.51
(2020-01-02)
Improvements
- Warning when Sphinx port is already used by another instance
1.1.50
(2019-11-13)
Improvements
- Display solution text along with error messages
1.1.49
(2019-08-13)
Fixed
- Fixed Magento Marketplace compatibility
1.1.48
(2019-08-02)
Fixed
- Fixed Advanced Search issues
- Fixed "Reset" action preserving Sphinx data folder
1.1.47
(2019-06-27)
Fixed
- Magento 2.3.2 compatibility
1.1.46
(2019-05-21)
Fixed
- Fixed Sphinx reindex issues
1.1.45
(2019-04-18)
Fixed
- Fixed non-searchable attributes being included during reindex
1.1.44
(2019-04-01)
Features
- Advanced search options, synonyms, and stopwords support in Fast Mode
1.1.43
(2018-11-29)
Fixed
- Fixed search in multi-store setups with Fast Mode
1.1.42
(2018-11-29)
Fixed
- Magento 2.3 compatibility
1.1.41
(2018-11-01)
Fixed
- Fixed missing BP constant error
1.1.40
(2018-10-24)
Fixed
- Fixed cleanIndex for Sphinx engine
1.1.39
(2018-10-16)
Fixed
- Fixed "Instance for '' not found" error
- Fixed unexpected BAD_NUMERIC error
1.1.38
(2018-09-20)
Fixed
1.1.37
(2018-09-20)
Fixed
1.1.36
(2018-09-19)
Fixed
- Fixed Ves Blog compatibility
1.1.35
(2018-09-12)
Improvements
- Support for multiple indexes of the same type
1.1.34
(2018-09-11)
Fixed
- Fixed Fast Autocomplete issues
1.1.33
(2018-07-31)
Improvements
- Improved full reindex speed
1.1.32
(2018-07-11)
Fixed
- Fixed Sphinx not finding keywords with dashes
1.1.31
(2018-07-05)
Improvements
- Improved wildcard matching to prioritize exact matches over partial matches
1.1.30
(2018-07-02)
Improvements
- Auto-start Sphinx daemon on search
1.1.29
(2018-06-18)
Fixed
1.1.28
(2018-06-18)
Fixed
- Fixed autocomplete configuration issues
1.1.27
(2018-06-14)
Fixed
1.1.26
(2018-06-14)
Features
- Fast Mode for Search Autocomplete — instant results without server round-trip
1.1.25
(2018-04-20)
Fixed
- Fixed Sphinx special character handling
1.1.24
(2018-02-16)
Features
- Gift Registry search index for Sphinx engine
1.1.23
(2017-12-18)
Fixed
- Fixed synonyms processing
1.1.22
(2017-12-14)
Fixed
- Removed symfony/yaml requirement
1.1.21
(2017-11-24)
Fixed
- Fixed "MySQL server has gone away" error
- PHP 7.2 compatibility
1.1.20
(2017-10-24)
Fixed
1.1.19
(2017-10-17)
Fixed
- Fixed relative path issues
1.1.18
(2017-10-11)
Features
- Custom Sphinx installation path support
1.1.17
(2017-10-06)
Features
- Custom charset_table support for Sphinx
1.1.16
(2017-09-26)
Fixed
- Magento 2.2 compatibility
1.1.15
(2017-09-21)
Fixed
- Fixed character escaping issues
1.1.14
(2017-09-15)
Fixed
- Fixed fresh installation issues
1.1.13
(2017-08-11)
Fixed
- Fixed category page issues
1.1.12
(2017-08-10)
Fixed
- Fixed "not-words" support with Sphinx engine
1.1.11
(2017-07-28)
Fixed
- Fixed category page issues
1.1.10
(2017-07-21)
Features
- Option to enable/disable Sphinx daemon auto-start
1.1.9
(2017-06-29)
Fixed
- Fixed Knowledge Base provider
1.1.8
(2017-06-26)
Fixed
- Fixed search weight issues
1.1.7
(2017-06-20)
Fixed
- Fixed search relevance calculation
1.1.6
(2017-05-19)
Fixed
- Fixed minimum infix length configuration
- Fixed single-character search
1.1.4
(2017-05-05)
Features
- Sphinx management via CLI commands
1.1.3
(2017-04-14)
Fixed
- Fixed suggestions data provider
1.1.2
(2017-04-13)
Fixed
1.1.1
(2017-04-04)
Fixed
- Fixed module requirements
1.1.0
(2017-04-04)
Improvements
- Split into separate modules
1.0.60
(2017-02-06)
Fixed
- Fixed default sort direction
1.0.59
(2017-02-06)
Fixed
- Fixed data serialization issues
- Fixed "push out-of-stock products" feature
1.0.57
(2017-01-24)
Fixed
- Fixed Dutch language singularize stemming
- Fixed catalog attribute index
1.0.56
(2017-01-20)
Improvements
- Increased Sphinx max_children limit
1.0.55
(2017-01-20)
Features
- Catalog Attributes search index
1.0.54
(2017-01-13)
Fixed
- Fixed store-based configuration
1.0.53
(2017-01-12)
Features
- Ves Brands search index
- Ves Blog search index
Improvements
- Backend interface improvements
1.0.52
(2016-12-23)
Fixed
- Fixed out-of-stock products filtering
1.0.51
(2016-12-21)
Fixed
1.0.50
(2016-12-16)
Features
1.0.49
(2016-12-01)
Improvements
- Improved stemming — now based on current store locale
1.0.48
(2016-11-30)
Features
- Custom search weight for individual products
1.0.47
(2016-11-23)
Fixed
- Fixed search term highlighter
1.0.46
(2016-11-21)
Fixed
- Fixed possible swatches conflict
1.0.45
(2016-11-21)
Improvements
- Magento 2.2.0 compatibility
1.0.44
(2016-11-17)
Fixed
- Fixed highlighting issue with ampersand (&) character
- Fixed compare option on search results page
1.0.43
(2016-10-31)
Features
- Generate Sphinx configuration for external server
Fixed
- Fixed single-character wildcard search
- Fixed search term highlighter
- Fixed number in attribute code
1.0.40
(2016-10-12)
Fixed
- Fixed memory limit during indexation
- Fixed built-in search with very large descriptions
1.0.38
(2016-10-10)
Fixed
1.0.37
(2016-10-04)
1.0.36
(2016-09-27)
Features
- Custom search weight for individual products
1.0.34
(2016-09-07)
Improvements
- CMS block content indexed during category reindex
Fixed
- Fixed multi-store results redirect
1.0.32
(2016-08-19)
Features
- Search by CMS block content within pages
Fixed
- Fixed Sphinx attribute issues
1.0.31
(2016-08-09)
Fixed
- Fixed Sphinx index attribute issues
1.0.30
(2016-08-06)
Fixed
- Fixed category index in multi-store configuration
1.0.28
(2016-07-07)
Features
- Pagination for WordPress Blog search results
Fixed
- Fixed temporary table creation on external WordPress database
1.0.27
(2016-07-06)
Fixed
- Fixed inline block display when searching CMS pages
- Fixed Sphinx compatibility with Magento 2.1
- Fixed multi-store configuration issues
1.0.26
(2016-06-29)
Fixed
- Fixed results limit on category pages
1.0.25
(2016-06-29)
Improvements
- Added additional exceptions for 404-to-search redirects
1.0.24
(2016-06-24)
Fixed
- Magento 2.1 compatibility
- Fixed "Enable redirect from 404 to search results" feature
1.0.23
(2016-06-14)
Features
- Ability to reset Sphinx daemon from admin
1.0.22
(2016-06-08)
Fixed
- Fixed multi-store search results
1.0.21
(2016-06-07)
Features
- Magefan Blog search index
1.0.20
(2016-05-24)
Improvements
- Added special characters to Sphinx charset table
1.0.19
(2016-05-19)
Improvements
- Bundled SphinxQL library within the module
Fixed
- Fixed synonyms processing
1.0.18
(2016-05-17)
Improvements
- Added file extension exceptions to 404 redirect observer
Fixed
- Fixed min_word_len for search with dashes (e.g., "0-1")
1.0.17
(2016-05-16)
Fixed
- Fixed synonyms processing
1.0.15, 1.0.16
(2016-05-12)
Improvements
- Improved query builder performance
Fixed
- Fixed Sphinx query error after adding new attributes
1.0.14
(2016-04-26)
Fixed
1.0.13
(2016-04-20)
Features
- Console command for reindexing search indexes
Fixed
- Fixed search by child product SKU
- Fixed active search tab CSS when HTML minification enabled
- Fixed admin menu issues
- Fixed MySQL score builder
1.0.12
(2016-04-07)
Fixed
- Fixed area code issue in CLI mode
- Fixed JS error with HTML minification
- Fixed plural query handling
1.0.11
(2016-03-25)
Features
- Mirasvit Knowledge Base integration
1.0.10
(2016-03-17)
Features
- Search products only in active categories option
Improvements
- Default index configuration
Fixed
- Fixed score SQL query issues
- Fixed results limit
1.0.9
(2016-03-09)
Features
- Mirasvit Blog MX search index
- Console commands for import/remove synonyms and stopwords
- Default lemmatizer for EN, DE languages
- Fallback engine for Sphinx
Improvements
- Default index configuration
- Improved 404-to-search feature
- Improved Sphinx configuration
Fixed
- Fixed stopwords import controller
- Added Symfony/Yaml dependency
- Fixed synonyms and stopwords import
- Fixed product list toolbar
- Fixed Manadev_LayeredNavigation compatibility
1.0.8
(2016-02-24)
Fixed
- Fixed segmentation fault (PHP 7) during reindex
1.0.7
(2016-02-15)
Fixed
- Fixed special characters in Sphinx query (@)
- Fixed "Default Category" appearing in category search results
- Fixed product count at category pages (limit, offset)
1.0.6
(2016-02-02)
Fixed
- Fixed non-cacheable "search.google.sitelinks" block
- Fixed upgrade script for synonyms and stopwords
- Fixed searchd command not found in console output
1.0.5
(2016-01-31)
Features
- Multi-store search results
Search Autocomplete & Suggest [mirasvit/module-search-autocomplete]
1.2.3
(2020-07-23)
Improvements
- Hide search on search icon click
Fixed
- Fixed missing products in Fast Mode results caused by newlines in data
1.2.2
(2020-07-08)
Fixed
- Fixed wrong price data in Fast Mode
- Fixed search term not showing in "no results" text in Fast Mode
- Fixed search results displaying inline instead of stacked
- Fixed product reviews backward compatibility
- Fixed image proportions in autocomplete
- Fixed rating display
- Improved Fast Mode reindex performance
1.2.1
(2020-05-14)
Fixed
- Fixed Amasty Blog post links
- Fixed extra GET parameters in URLs in Fast Mode
1.2.0
(2020-05-07)
Improvements
- Improved Fast Mode reindex speed
Fixed
- Fixed MariaDB compatibility
- Removed search box JS from checkout page to avoid conflicts
1.1.109
(2020-04-24)
Fixed
- Fixed HTML entity display issues
- Fixed word wrapping on results title
- Fixed suggested search terms filtering
1.1.108
(2020-04-07)
Fixed
- Improved Fast Mode server performance
- Fixed wrong category URLs
- Fixed wrong "Add to Cart" URL in Fast Mode
- Fixed Fast Mode product URLs differing from regular results
- Fixed "category product" index display
- Fixed Fast Mode translations
1.1.107
(2020-03-04)
Fixed
- Fixed old search results visible while new search is loading
- Fixed wrong product URL in Fast Mode
- Fixed in-stock filter being pre-applied
1.1.106
(2020-02-12)
Fixed
- Fixed "Invalid attribute name: store_id" on reindex
- Fixed category product arrow styling
- Fixed wrong product URL in multi-store Fast Mode
1.1.105
(2020-01-02)
Fixed
- Fixed native search autocomplete not being disabled
1.1.104
(2019-12-18)
Fixed
- Fixed Blackbird ContentManager index
1.1.103
(2019-12-16)
Features
- Blackbird ContentManager search index
Improvements
- Product search index refactoring
1.1.102
(2019-12-09)
Fixed
- Fixed rating display issues
1.1.101
(2019-12-03)
Fixed
- Fixed wrong search results breadcrumbs
- Fixed rating display
1.1.100
(2019-11-25)
Improvements
- Uses default Magento price block for autocomplete pricing
1.1.99
(2019-11-25)
Fixed
- Fixed "Add to Cart" translation
- Fixed missing product rating
- Fixed category index URLs in Fast Mode
- Fixed CMS page index URLs in Fast Mode
1.1.98
(2019-11-14)
Fixed
- Fixed conflict with Webkul ShowPriceAfterLogin
1.1.97
(2019-11-12)
Fixed
- Fixed search button not clickable when selecting from Popular Suggestions
1.1.96
(2019-08-08)
Fixed
- Fixed wrong layer resolver
1.1.95
(2019-08-06)
Fixed
- Fixed prices for multi-store setup in Fast Mode
- Fixed product thumbnails in Fast Mode
1.1.94
(2019-07-31)
Fixed
- Fixed autocomplete remaining visible when cart popup is shown
1.1.93
(2019-07-30)
Features
- Fishpig Glossary search index support
Fixed
- Fixed native search form active state
- Fixed nested environment emulation error
- Improved reindex speed
- Fixed blinking autocomplete with multiple search forms
1.1.92
(2019-06-19)
Fixed
- Fixed HTML entities rendering
- Fixed Knowledge Base article template typo
- Fixed autocomplete losing focus state
1.1.91
(2019-04-26)
Improvements
- Added notification message after enabling Fast Mode
Fixed
- Fixed IE 10 compatibility
1.1.90
(2019-04-24)
Fixed
- Fixed Fast Mode config file generation on reindex
- Fixed Fast Mode index display order
1.1.89
(2019-04-12)
Fixed
- Fixed incorrect module conflict declaration
1.1.88
(2019-04-08)
Fixed
- Fixed similar results appearing in multiple attribute indexes
1.1.87
(2019-04-01)
Improvements
- Advanced search options, synonyms, and stopwords support in Fast Mode
Fixed
- Fixed translations for multi-store search in Fast Mode
1.1.86
(2019-03-13)
Fixed
- Fixed multi-store search in Fast Mode
Search MySQL [mirasvit/module-search-mysql]
1.0.39
(2020-09-07)
Fixed
- Fixed Mana_layerednavigationajax paging compatibility
- Improved indexer handler
1.0.38
(2020-04-13)
Improvements
- Performance optimizations
1.0.37
(2020-02-18)
Fixed
- Magento 2.3.4 compatibility
1.0.36
(2019-11-11)
Fixed
- Fixed ambiguous class declaration
1.0.35
(2019-08-13)
Fixed
- Fixed Magento Marketplace compatibility
1.0.34
(2019-08-06)
Fixed
- Fixed Advanced Search issues
1.0.33
(2019-06-27)
Fixed
1.0.32
(2019-06-27)
Fixed
- Magento 2.3.2 compatibility
1.0.31
(2019-05-08)
Fixed
1.0.29
(2018-02-25)
Fixed
- Fixed DI compilation issue
1.0.28
(2018-02-25)
Fixed
- Magento 2.1.14 EE compatibility
1.0.27
(2018-12-10)
Fixed
- Fixed Magento 2.3 index switcher error
1.0.26
(2018-11-29)
Fixed
- Magento 2.3 compatibility
1.0.25
(2018-10-16)
Fixed
- Fixed "Instance for _ not found" error
1.0.24
(2018-10-12)
Fixed
- Fixed undefined offset error with built-in engine
1.0.23
(2018-10-09)
Improvements
1.0.22
(2018-09-26)
Fixed
1.0.21
(2018-09-21)
Improvements
1.0.20
(2018-09-21)
Fixed
- Fixed multi-select attribute processing
1.0.19
(2018-09-20)
Fixed
1.0.18
(2018-09-20)
Fixed
1.0.17
(2018-09-19)
Fixed
- Magento 2.1 compatibility
1.0.16
(2018-09-12)
Features
- Multiple Catalog Attribute indexes support
1.0.15
(2018-09-07)
Fixed
- Magento 2.1 compatibility
1.0.14
(2018-09-05)
Improvements
- Magento 2.1 compatibility
1.0.13
(2018-01-30)
Fixed
- Fixed searching by custom product options
1.0.12
(2017-11-20)
Fixed
- Fixed search_weight column issues
1.0.11
(2017-11-16)
Fixed
- Fixed search weight issues
1.0.10
(2017-11-15)
Fixed
- Fixed search_weight column issues
1.0.9
(2017-11-13)
Fixed
1.0.8
(2017-09-27)
Fixed
1.0.5
(2017-09-26)
Fixed
1.0.4
(2017-08-08)
Fixed
- Fixed "Not Words" handling
- Fixed stopwords processing
1.0.3
(2017-05-04)
Fixed
- Fixed empty query after applying stopwords
1.0.2
(2017-04-13)
Fixed
1.0.1
(2017-04-10)
Features
- Suggestion provider for Advanced Search
Search Landing Page [mirasvit/module-search-landing]
1.0.10
(2020-09-29)
Fixed
- Fixed misspell-related issues
1.0.9
(2020-03-05)
Improvements
1.0.8
(2019-09-09)
Fixed
- Fixed code quality issues
1.0.7
(2019-06-04)
Fixed
- Fixed different URL keys for landing pages on different stores
1.0.6
(2018-11-29)
Fixed
- Magento 2.3 compatibility
1.0.5
(2018-10-10)
Improvements
1.0.4
(2018-04-12)
Features
- Redirect search term to landing page URL key
1.0.3
(2017-09-26)
Fixed
- Magento 2.2 compatibility
1.0.2
(2017-07-25)
Fixed
1.0.1
(2017-05-03)
Fixed
1.0.0
(2017-05-03)
Search Spell Correction [mirasvit/module-misspell]
1.0.37
(2020-07-28)
Improvements
- Improved spell correction speed
Fixed
- Fixed spell correction running on every new query instead of only when needed
- Improved spell correction result quality
- Improved fallback search functionality
1.0.36
(2020-03-16)
Improvements
1.0.35
(2020-01-24)
Improvements
- Improved performance with InnoDB tables
1.0.34
(2019-10-08)
Fixed
- Fixed misspell word splitting
- Changed misspell tables to MyISAM engine for better full-text search
1.0.33
(2019-09-18)
Fixed
- Fixed spell correction not returning suggested results
1.0.32
(2019-08-13)
Fixed
- Fixed Magento Marketplace compatibility
1.0.31
(2019-05-27)
Fixed
- Fixed generators returning values (PHP compatibility)
1.0.29
(2019-02-12)
Fixed
- Fixed "Allowed memory size" error during misspell indexation
1.0.28
(2018-11-29)
Fixed
- Magento 2.3 compatibility
1.0.27
(2018-10-01)
Fixed
1.0.26
(2018-09-19)
Fixed
- Fixed first suggestion not appearing in some cases
1.0.24
(2018-05-31)
Fixed
- Fixed Cyrillic terms indexation
1.0.23
(2018-04-11)
Fixed
- Fixed database error 22003 during indexation
1.0.22
(2017-12-25)
Features
- Integrated spell correction with Search Autocomplete
- Added reindex validator
1.0.21
(2017-12-13)
Improvements
- Improved fallback search logic
1.0.20
(2017-11-17)
Fixed
1.0.19
(2017-10-26)
Fixed
- Fixed null values during indexation
1.0.18
(2017-09-28)
Fixed
- Fixed calculation of number of results for suggested search phrases
1.0.17
(2017-09-26)
Fixed
- Magento 2.2 compatibility
- Fixed highlighting issues
1.0.16
(2017-08-09)
Fixed
1.0.15
(2017-07-12)
Fixed
- Fixed Changelog changes issues
1.0.14
(2017-07-10)
Improvements
- Improved fallback search logic
1.0.13
(2017-06-20)
Fixed
- Fixed Amasty Shopby compatibility
1.0.12
(2017-05-10)
Improvements
- Spell correction index is automatically removed when disabled
1.0.11
(2017-04-11)
Improvements
- Switched to API interfaces
1.0.10
(2017-02-20)
Improvements
- Changed all string functions to multibyte (mb_*) equivalents
1.0.9
(2017-02-03)
Improvements
- Added recurring setup script to check fulltext indexes
1.0.8
(2016-11-21)
Improvements
- Magento 2.2.0 compatibility
1.0.7
(2016-06-24)
Fixed
- Magento 2.1 compatibility
1.0.6
(2016-06-16)
Fixed
- Fixed index mode change for misspell index
1.0.5
(2016-04-27)
Improvements
1.0.4
(2016-02-23)
Fixed
- Fixed segmentation fault (PHP 7) during reindex
1.0.3
(2016-02-07)
- Initial documented release
Search Report [mirasvit/module-search-report]
1.0.8
(2020-03-16)
Improvements
1.0.6
(2019-11-14)
Fixed
- Fixed conflict with Paysera payment methods
1.0.5
(2018-08-21)
Fixed
- Fixed report settings not working
1.0.4
(2018-04-20)
Fixed
- Fixed report by search terms
1.0.3
(2018-02-14)
Improvements
- Switched to new module-report version
Fixed
- Fixed secure cookie details
1.0.2
(2017-09-26)
Fixed
- Magento 2.2 compatibility
1.0.1
(2017-07-21)
Fixed
- Fixed "Circular dependency" error