Advanced Sphinx Search Pro is the most adaptive Magento 2 search engine! It gives customers search needs in a split second and provides highly relevant results.
First, please find your extension in your account in the My Downloadable Products section. Then, start with Installation option. It is best to follow our step-by-step guide in order to configure the best search results.
First of all, you need to install our extension, and then, separately, install the search engine on your server. Here you will find instructions, on how to do it on different platforms.
Then you will need to connect Sphinx Engine, and configure search results.
This should be a good beginning!
php -f bin/magento module:enable Mirasvit_Search Mirasvit_SearchSphinx Mirasvit_SearchMysql to enable the extension.php -f bin/magento setup:upgrade to install the extension.php -f bin/magento cache:clean to clean the cache.rm -rf pub/static/frontend/*; rm -rf pub/static/backend/*; rm -rf var/view_preprocessed/*;php -f bin/magento setup:static-content:deployphp -f bin/magento module:enable Mirasvit_Search Mirasvit_SearchSphinx Mirasvit_SearchMysql to enable the extension.php -f bin/magento setup:upgrade to install the extension.php -f bin/magento cache:clean to clean the cache.rm -rf pub/static/frontend/*; rm -rf pub/static/backend/*; rm -rf var/view_preprocessed/*;php -f bin/magento setup:static-content:deployHere you can quickly navigate across all functionality settings we have. Please use the list below to navigate.
This section covers all topics, necessary for working with indices, and consists of the following subsections:
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Search Indexes are the most important part of your search subsystem. The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query. Without an index, the search engine would scan every document on your store, which would require considerable time and computing power.
This section covers all topics, necessary for working with indexes, and consists of the following subsections:
Our Magento 2 Elasticsearch Extension or Sphinx Extension can combine all indexes, existing in your configuration, to boost search and give your customers the most relevant results. It brings them all to a single grid, located at System -> Search Management -> Search Indexes, from where you can configure them.
Each index, added to this grid, displayes the following properties:
Additional Action column provides common actions, that can be performed directly from grid, such as:
Back to top
To add a new index to Mirasvit Search extension, go to System -> Search Management -> Search Indexes and press Add New Index.
Index record creation are divided into two stages: setting common settings and specific, which depend from their type. Common settings are shown in General Settings subsection:
Press Save and Continue Edit to proceed to index configuration stage.
Properties - type-dependent specific options section. Read more below, or pick a link from type values, described in (2) step.
On installation three indexes will be automatically created and configured: Product, Category and CMS Page.
Back to top
Product Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Specific options of this type will be shown on Properies section of Index edit page:
Back to top
Category Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's no specific options for this type of index.
Back to top
CMS Page Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
There's only one specific option for this type on Properies section of Index edit page:
Back to top
Unlike of other indexes, this one can be created only for specific attribute, which should be displayed as separate section in Search Results.
This attribute should be previously enabled for Advanced Search. It can be done at Stores -> Attributes -> Product grid. Pick up desired attribute, then jump to Storefront Properties subsection and then make them available for search by setting to Yes two options: Use in Search and Visible in Advanced Search.
After saving product you can configure Attribute Index for this attribute at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Back to top
Wordpress Blog Index can be created at System -> Search Management -> Search Indexes grid. Read more here about adding new index.
Database Connection Name - connection name of the wordpress database.
If WordPress is installed on the same database, the correct value is default.
'db' => array(
'table_prefix' => '',
'connection' => array(
'default' => array(
'host' => 'localhost',
'dbname' => 'store',
'username' => 'root',
'password' => 'password',
'active' => '1',
),
),
),If WordPress is installed on the separate database, you need to create a new connection in file app/etc/env.php.
'db' => [
'table_prefix' => '',
'connection' => [
'default' => [
'host' => 'localhost',
'dbname' => 'dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
],
'wpconnection' => [
'host' => 'localhost',
'dbname' => 'your_wp_dbname',
'username' => 'username',
'password' => 'password',
'active' => '1',
]
]
],
'resource' => [
'default_setup' => [
'connection' => 'default'
],
'wp_setup' => [
'connection' => 'wpconnection'
]
],Url Template - the full URL for your posts with dynamical variables.
Typical base urls should look like example below below:
http://example.com/blog/{post_name}.html
http://example.com/blog/?p={ID}
http://example.com/{category_slug}/{post_name}.htmlBack to top
Sometimes it's need to have specific type of Index, which is either not included to our Magento 2 Elasticsearch Extension or Sphinx 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 repository http://github.com/mirasvit/module-search-extended
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.
git branch.app/code/Mirasvit/SearchExtended/Index/ and rename subpath Magento/Review/Review/ to the required one ([provider]/[module]/[entity])app/code/Mirasvit/SearchExtended/Index/[provider]/[module]/[entity]/Index.php
getName(), getPrimaryKey() and getIdentifier() methodsgetAttributes() methodbuildSearchCollection() and getSearchableEntities()app/code/Mirasvit/SearchExtended/etc/di.xmlAdjust layout file app/code/Mirasvit/SearchExtended/view/frontend/layout/catalogsearch_result_index.xml
Rename template name/path and adjust it /app/code/Mirasvit/SearchExtended/view/frontend/templates/index/magento/review/review.phtml
If everything was correct, you can add index of your custom type like any regular index.
/vendor/mirasvit/module-search-autocomplete/src/SearchAutocomplete/Model/Index folder<Company>/<Extension>/<EntityType>.php i.e. /vendor/mirasvit/module-search-autocomplete/src/SearchAutocomplete/Model/Index/Ves/Blog/Post.php/vendor/mirasvit/module-search-autocomplete/src/SearchAutocomplete/etc/di.xml and add item to type name="Mirasvit\SearchAutocomplete\Model\Index\Pool" argumentsThis section describes, how you can customize and greatly improve the relevance of your search results by configuring Search Settings.
The most important part is Global Search Configuration. It is located at System -> Search Management -> Settings -> Mirasvit Extensions -> Search, and divided into the following sections:
Our extension allows you to power up search either with default Magento search engine, or with external engine. Option Search Engine selects, which engine should be in charge, and has three possible values:
Third possible value depends from precise extension, that you're using. Mirasvit provides two search applications, that share this option, but support different search engines.
Sphinx Search Ultimate
Sphinx Search Ultimate, as it derives from its name, allows you to use Sphinx Engine on the dedicated server, or on the same server of your store.
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 better used for stores with products quantity below 50k and without need of layered navigation or aggregated search requests. Read more about this engine key features.
Sphinx Search Ultimate adds to the option Global Search Configuration -> Search Engine Configuration -> Search Engine possible value External Sphinx Engine.
External Sphinx Engine also triggers additional options for configuring and managing Sphinx Daemon:
For Sphinx installed on the same server with your Magento store :
For Sphinx installed on the dedicated (remote) server :
Search Engine Configuration section contains Additional Configuration subsection, visible for External Sphinx engine only. It allows you to tune up Sphinx configuration file, and contains the following settings:
[magento_root_directory]/var/sphinx/ location.searchd Search Daemon. Read more about it here.Elastic Search Ultimate
Magento 2 Elasticsearch Extension, as it derives from its name, allows you to use Elastic Engine on the dedicated server, or on the same server of your store.
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 50k of products and/or support of Layered Navigation. Read more about its key features.
Elastic Search Ultimate adds to the option Global Search Configuration -> Search Engine Configuration -> Search Engine possible value Elasticsearch Engine.
Elasticsearch Engine also triggers additional options for configuring and managing Sphinx Daemon:
127.0.0.1 by default).9200).It also features two buttons, that allows you to check Elastic Search connection:
Back to Top
mirasvit/module-search-autocomplete is installed and enabled.Back to Top
This option is useful when you have store-dependant 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.
Enable Multi-Store Search Results - if you enable this option, search results will be displayed in tabs. Each tab has a number of results for a storeview and corresponds to one of your storeviews. This option triggers an additional sub-option:
Stores - allows you to select, which storeviews should be included in a multi-store search.
Autocomplete always returns results from the current store only. It can not display search results from another storeviews.
Back to Top
This section describes the Long-Tail Search feature, that will allow you to have correct search results for words that contain dashes or other non-alphabetic symbols. You can also replace on-the fly the most typical errors customers can make in complex product names.
For example, we have a product Canon PowerShot SX500 IS. But customer can request Canon PowerShot SX-500IS, which default search will not find, because it differs from actual product label.
It's because Magento by default during reindex uses only correct product labels from database, and thus, index will contain only them - making products with complex names "ineligible" for search.
This is where "Long-tail" search come. During reindex and search this feature recognizes the keywords rather by pattern and replaces it either to the empty or some other characters, "correcting" customer's request on-the fly.
In example above the SX500 IS can be converted to the SX500IS and during the search, the SX-500IS also be converted to the SX500IS by replacing '-' symbol to empty char.
This way search will be able to find products by several combinations of spelling the product's name.
Also, please learn more about configuring Long-Tail Search for your store in our Blog article.
Back to Top
Go to System / Search Management / Settings / Mirasvit Extensions / Search
In the section Search Settings go to the option Long tail.
There you can set up regular expressions to receive required search results.
Match Expression - the regular expression(s) that parses words for further replacing.
Parsing goes for search index, during an indexing process, and goes for search phrases during search.
E.g. /([a-zA-Z0-9]*[\-\/][a-zA-Z0-9]*[\-\/]*[a-zA-Z0-9]*)/
/[\-\/]/empty value.Back to Top
Here is some of most useful cases of long-tail search, implemented as corresponding rules.
Automatically remove '-' symbol from product names
Create a rule with the following parameters:
/[a-zA-Z0-9]*-[a-zA-Z0-9]*/ SX500-123, GLX-11A, GLZX-VXV, GLZ/123, GLZV 123, CNC-PWR1/-/SX500123, GLX11A, GLZXVXV, GLZ/123, GLZV-123-123, CNCPWR1Automatically remove '-' and '/' symbols from product names
Create a rule with the following parameters:
/[a-zA-Z0-9]*[ \-\/][a-zA-Z0-9]*/ SX500-123, GLX-11A, GLZX-VXV, GLZ/123, GLZV 123, CNC-PWR1/[ \-\/]/SX500123, GLX11A, GLZXVXV, GLZ123, GLZV123, CNCPWR1Automatically make solid all products names with separators
Create a rule with the following parameters:
/[a-zA-Z0-9]*[-\/][a-zA-Z0-9]*([-\/][a-zA-Z0-9]*)?/ SX500-123, GLX-11A, GLZX-VXV, GLZ/123, GLZV-123-123, CNC-PWR1/[-\/]/SX500123, GLX11A, GLZXVXV, GLZ123, GLZV123123, CNCPWR1Automatically fix misspelled product's name
Create a rule with the following parameters:
/([a-zA-Z0-9]*[\- ][a-zA-Z0-9]*[\-][a-zA-Z0-9]*)/VHC68B-80, VHC-68B-80, VHC68B80/[\- ]/VHC68B80Back to Top
Long-Tail expressions, which are used in Search Sphinx for M1 and M2 sliightly differ.
In M1 Search Sphinx you can enter one or more expressions to match, separated by '|' character. In M2 you can not.
Consider the following expression for Search Sphinx for M1:
/[a-zA-Z0-9][ -/][a-zA-Z0-9]([ -/][a-zA-Z0-9]*)?/|/[a-zA-Z]{1,3}[0-9]{1,3}/ /[ -/]/|/([a-zA-Z]{1,3})([0-9]{1,3})/$1 $2
It actually contains two separate regexps to match: /[a-zA-Z0-9][ -/][a-zA-Z0-9]([ -/][a-zA-Z0-9]*)?/ and /[a-zA-Z]{1,3}[0-9]{1,3}/ with respective separate expressions for replace.
You need either to reformat that expression, so it will match in single expression, or rewrite this rule as a set of two:
First rule
This rule will implement the first part of original M1 expression.
/[a-zA-Z0-9][ -/][a-zA-Z0-9]([ -/][a-zA-Z0-9]*)?//[ -/]/$1 $2Second rule
This rule will implement the second part of original M1 expression.
/[a-zA-Z]{1,3}[0-9]{1,3}//([a-zA-Z]{1,3})([0-9]{1,3})/$1 $2Back to Top
Landing search page is special search result page, with a static URL, where customers are redirected on using some search expression.
Let us have a large number of frequently asked (or just a promotional set) models of Samsung phones with black coat. So we create a separate promotional page, say, http://store.com/black-samsung-phone.html, and bind it to the search phrase "black samsung phone". Then, when customer will request a black Samsung phone, it will be immediately sent to your special page.
Also it supports the following logic .We create a separate promotional page, say, http://store.com/black-samsung-phone.html, and bind it to the search phrase "black samsung phone". When customer will go to this (specific) URL search results for "black samsung phone" will be immediately built on it.
All such a pages can be managed from System -> Search Management -> Manage Landing Pages grid.
shoes/all, then full URL would be https://example/shoes/all/.Synonyms are keywords with the same or similar meaning. All of them are located at System -> Search Management -> Manage Synonyms section.
You can either manually add synonyms, or import them from YAML-formatted file.
On creation page, fill the following fields:
Synonyms - comma-separated list of synonyms. It should contain at least one keyword. Each of them should match the following requirements:
It should have length, greater than 1 character.
Term: clock
Synonyms: watchThen, if customer issues "clock" query, all watches will be found.
Our extension uses YAML file format for synonyms importing. It should resemble the following format:
-
term: [TERM_1]
synonyms: [SYN_1]
-
term: [TERM_2]
synonyms: [SYN_2]Name of this file should be equal to your language code in capital case. Codes can be found here, use column 639-1 for that.
EN.yaml, and it's content should be:
-
term: abiogenesis
synonyms: autogenesis,autogeny,spontaneous generation
-
term: abject
synonyms: low,miserable,scummy,scurvy,resigned,unhopeful
-
term: abjection
synonyms: abasement,degradation
-
term: abjectly
synonyms: resignedlyTo import synonyms, perform the following steps:
[magento_root]/ folder.Stopwords are words that have little lexical meaning or ambiguous meaning and are not useful during the search (ex. and, or, the, a, with, etc). Therefore, these words should be removed from search phrases to make them relevant.
You can either manually add stopwords, or import them from YAML-formatted file.
Our extension uses YAML file format for stopwords importing. It should resemble the following format:
[ID_1]:[Stopword_1]
[ID_2]:[Stopword_2]
[ID_3]:[Stopword_3]
Name of this file should be equal to your language code in capital case. Codes can be found here, use column 639-1 for that.
EN.yaml, and it's content should be:
1:"but"
2:"now"
3:"what"
4:"except"To import stopwords from such a file, perform the following steps:
[magento_root]/ folder.Score Boost Rules are powerful tool, which allows you to affect relevancy of search results, depending on certain conditions.
When 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.
But inside these groups items are listed strictly by their relevance to search query, which calculated for each item separately as item rank. Position in search results list depends from 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 list, which is extremely useful for promotion and marketing purposes.
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/
Conditions are broken into two parts.
Apply the rule only for following products - allows you to define, which combination of products makes Rule apply.
Both of them use the same pattern, as other rules in Magento 2, and enclosed into logical blocks If ALL of these conditions are TRUE/FALSE (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 Score Boost Rules work.
Erin Recommends Promo
This example allows you to move products, that were recommended by your editorial board (it is defined by custom attribute Erin Recommends), to the top of search results.
Title: Erin Recommends Promo
Score Factor: Increase by 10 points Initial Score
Apply the rule only for the following products:
Erin Recommends is Yes
Analog Watches to the End
This rule drops to the very bottom all analog watches, when customer search includes "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
Apply the rule only when the following conditions are met:Search Query contains watch
New Products Promo
This example allows you to uplift promotional products higher than others, but not necessary at the top.
Title: New Products Promo
Score Factor: increase by 5 points Initial Score
Apply the rule only for the following products:
New is Yes
Our extension arranges relevance of found products using Global Settings. But sometimes (for example, for promotional purposes) you need to forcibly move one or more specific products to the top, or vice versa, to the bottom of search results.
It can be done via special option Search Weight, added by our extension to the general settings of the Product Edit Pages.
This weight is the relative position, where product will be placed on search result page. It ranges from 100 (product or category will always appear at the top of search results list) to -100 (product or category will always appear at the bottom of search results list).
This section contains the most common problems, that customer can encounter, and how they can be resolved:
Please, make sure about the following:
Possible cause: too small max_execution_time PHP parameter, which is not enough to complete requests with large number of words.
Solution: there can be two possible solutions.
Increase max_execution_time parameter either in .htaccess, or directly in PHP.ini.
Typically it is enough to decrease the latter parameter, until search will work correctly.
Search Engine Settings
How to Check:
How to Resolve:
Large Quantity of Products (for Sphinx Search Pro and Ultimate extensions)
How to Check:
How to Resolve:
Large Quantity of Products (for Elastic Search Ultimate extension) How to Check:
How to Resolve:
High-load Crontasks
How to Check:
How to Resolve:
Conflicts with other vendor's search extensions
How to Check:
How to Resolve:
Disable this extension and check your search speed: php bin/magento module:disable <module_name>
public function getSocialIconsHtml()$block = $this->getLayout()->createBlock, place this code before
$socialIconsBlock = !empty($this->getSocialIconsBlock())?$this->getSocialIconsBlock():'Aheadworks\Blog\Block\Sharethis';$this->getSocialIconsBlock() after createBlock with $socialIconsBlock$socialIconsBlock = !empty($this->getSocialIconsBlock())?$this->getSocialIconsBlock():'Aheadworks\Blog\Block\Sharethis'; $block = $this->getLayout()->createBlock( $socialIconsBlock,...If your Sphinx Search Engine installed on same server run the following steps:
1) Whether you have Elastic or Sphinx search Ultimate extension, and use a built-in engine with over 20K products, consider using external search engines. To check your engine settings you may find at System -> Search Management -> Settings -> Mirasvit Extensions -> Search.
2) In case you already use an external search engine, you may check if it has a unique Index Prefix for your store for Elastic Search
or try to stop and restart Sphinx Daemon, then run reindex.
3) You have a Fast Mode enabled at System / Settings / Mirasvit Extensions / Search Autocomplete section: the disadvantages include the increased indexing time of the search index. Otherwise, disable this feature to speed up reindexing time.
4) Additionally disable some options in Product Settings content appearance such as Show Thumbnail, Rating, etc at System / Settings / Mirasvit Extensions / Search Autocomplete section.
5) Make sure there are no duplicate searchable attributes or searchable attributes with search weight = 1 at the Product Index in System -> Search Management -> Search Indexes, otherwise delete those searchable attributes and try reindex.
6) Take a look also on Magento Best Practices for reindexing here.
When happens: We installed on our staging/dev/test site and configured different ports on staging and on live. But the sphinx engine is not connecting on our staging site, keep getting the error message:
Sometimes you can see unwanted, strange search terms in Reports, Hot searches in the autocomplete or in the Related Search Terms and think it is spam or generated by our extension.
Actually, they are the most searched Search Terms in your Magento, more details find in official Magento documentation here. You can clear some of the search terms and it won't appear: go to Marketing > SEO & Search > Search Terms, find the necessary term and delete it, otherwise, you will need to delete them in the database.
Usually, it is a server error. The cause for the problem can be found in the server logs at /var/log/elasticsearch/ directory. First of all, make sure it is configured properly, reset elastic search indicies from the console curl -XDELETE localhost:9200/* and run re-index bin/magento indexer:reindex catalogsearch_fulltext.
Also, here is the best Magento practices to resolve elastic search problems.
If you would like to use our extension with Sphinx Engine, you need to install it first.
Installation includes a set of actions, that should be performed under root privileges. Actions can differ depending on selected platform. Here is the most used cases:
After installation run full reindex of Sphinx Engine indexes to fully enable your new search engine.
Execute from console/SSH under root privileges the following command:
sudo apt-get install sphinxsearch
Back to Top or proceed to Connection with Sphinx Engine
Execute from console/SSH under root privileges the following command:
sudo yum install sphinxsearch
Back to Top or proceed to Connection with Sphinx Engine
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.gztar xvf sphinx-2.2.11-release.tar.gzcd sphinx-2.2.11-releasewget http://snowball.tartarus.org/dist/libstemmer_c.tgztar xvf libstemmer_c.tgz./configure --with-libstemmermakemake installLearn 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:
To configure morphology and charset tables for additional languages, perform the following actions:
/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.
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
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+451Read more about character tables here.
Back to Top or proceed to Connection with Sphinx Engine
In some cases automatic installation either does not start, or even is not possible. Then you can manually install Sphinx:
wget http://sphinxsearch.com/files/sphinx-2.2.11-release.tar.gztar xvf sphinx-2.2.11-release.tar.gzcd sphinx-2.2.11-release./configuremakemake installConfiguration file will be generated automatically.
Back to Top or proceed to Connection with Sphinx Engine
After 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 store, or on dedicated separate server.
/usr/local/bin/).
php -f bin/magento indexer:reindex catalogsearch_fulltext to reindex search indexes.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.
searchd --config <path to config/sphinx.conf> nc -zv sphinx_server_ip sphinx_server_port to check if port open.Our Search Sphinx extension also have a command-line interface, which can be used from console or SSH.
Here is the list of available commands. (for bin/magento):
mirasvit:search-sphinx:manage - sphinx engine managementmirasvit:search:reindex - reindex all search indexes (same as indexer:reindex catalogsearch_fulltext)mirasvit:search:stopword - manage stopwordsmirasvit:search:synonym- manage synonymsConsole management of Search Sphinx includes the following commands:
start - starts Search Daemonstop - stops Search Daemonrestart - kills Search Daemon process and starts it with clean datareset - cleans search temporary datastatus - displays current status of Search Sphinx engine.ensure - special command, which automatically checks status, and only if daemon do not work, start it up.To execute management command, run the following expression from console/SSH:
bin/magento mirasvit:search-sphinx:manage --[command]Console reindexing can be run either for a whole store (without mode options), or for a selected Index (see more at Managing Indices), and for selected Store.
mirasvit:search:reindex --[mode]=[argument]Possible modes are:
INDEX - allows to reindex particular index. [argument] value should be code if desired index.STORE - allows to reindex 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.mirasvit:search:reindex --index=defaultModes can be used simultaneously, e. q. if you need to reindex Product index (code is 'catalogsearch_fullindex') on store with code 'german', you need the following command:
mirasvit:search:reindex --index=catalogsearch_fullindex --store=germanConsole 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 YAML 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 YAML file, which is used for managing stopwords, can be seen here.
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 YAML file will be used for synonyms importing.--remove - optional argument, that commands to remove synonyms 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 YAML file, which is used for managing synonyms, can be seen here.
To upgrade the extension follow these steps:
composer require mirasvit/module-search-sphinx:* --update-with-dependencies to update current extension with all dependencies.
composer update mirasvit/* command. It will update all Mirasvit modules, installed on your store. php -f bin/magento setup:upgrade to install the updates.php -f bin/magento cache:clean to clean the cache.Deploy static view files
rm -rf pub/static/frontend/*; rm -rf pub/static/backend/*; rm -rf var/view_preprocessed/*; php -f bin/magento setup:static-content:deploy
To temporarily disable the extension please follow the next steps:
php -f bin/magento module:disable Mirasvit_Search Mirasvit_SearchMysql Mirasvit_SearchSphinx to disable the extension.To uninstall the extension please follow these steps:
composer remove mirasvit/module-search-sphinx to remove the extension.php -f bin/magento setup:upgrade.(2020-11-26)
(2020-10-05)
(2020-09-07)
(2020-05-14)
(2020-04-13)
(2020-03-03)
(2020-01-02)
(2019-11-13)
(2019-08-13)
(2019-08-02)
(2019-06-27)
(2019-05-21)
(2019-04-18)
(2019-04-01)
(2018-11-29)
(2018-11-29)
(2018-11-01)
(2018-10-24)
(2018-10-16)
(2018-09-20)
(2018-09-20)
(2018-09-19)
(2018-09-12)
(2018-09-11)
(2018-07-31)
(2018-07-11)
(2018-07-05)
(2018-07-02)
(2018-06-18)
(2018-06-18)
(2018-06-14)
(2018-06-14)
(2018-04-20)
(2018-02-16)
(2017-12-18)
(2017-12-14)
(2017-11-24)
(2017-10-24)
(2017-10-17)
(2017-10-11)
(2017-10-06)
(2017-09-26)
(2017-09-21)
(2017-09-15)
(2017-08-11)
(2017-08-10)
(2017-07-28)
(2017-07-21)
(2017-06-29)
(2017-06-26)
(2017-06-20)
(2017-05-19)
(2017-05-05)
(2017-04-14)
(2017-04-13)
(2017-04-04)
(2017-04-04)
(2017-02-06)
(2017-02-06)
(2017-01-24)
(2017-01-20)
(2017-01-20)
(2017-01-13)
(2017-01-12)
(2016-12-23)
(2016-12-21)
(2016-12-16)
(2016-12-01)
(2016-11-23)
(2016-11-21)
(2016-11-21)
(2016-11-17)
(2016-10-31)
(2016-10-12)
(2016-10-10)
(2016-10-04)
(2016-09-27)
(2016-09-07)
(2016-08-19)
(2016-08-09)
(2016-08-06)
(2016-07-07)
(2016-07-06)
(2016-06-29)
(2016-06-29)
(2016-06-24)
(2016-06-14)
(2016-06-08)
(2016-06-07)
(2016-05-24)
(2016-05-19)
(2016-05-17)
(2016-05-16)
(2016-05-12)
(2016-04-26)
(2016-04-20)
(2016-04-07)
(2016-03-25)
(2016-03-17)
(2016-03-09)
(2016-02-24)
(2016-02-15)
(2016-02-02)
(2016-01-31)