v2.4.1

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.

  1. Increase max_execution_time parameter either in .htaccess, or directly in PHP.ini.

  2. 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

  • Search Engine Settings

    How to Check:

    • Navigate to System -> Search Management -> Settings -> Search Engine Configuration. If the option Search Engine is set to Built-In Engine or MYSQL, this is the probable cause.

    How to Resolve:

    • If you have Mirasvit MYSQL Search Module version below 1.0.23, upgrade it to latest version, as it contains significant improvements that speed up the built-in search engine.
    • Enable the option Fast Mode in Autocomplete settings at System -> Settings -> Mirasvit Extensions -> Search Autocomplete section.
    • If this will not help, consider a recommendation from next option.

  • Large Quantity of Products

    How to Check:

    • Navigate to Catalog -> Products section. If you have more than 14k records there, this is the probably cause.

    How to Resolve:

    • Replace Build-In Engine to External Sphinx Engine in option Search Engine at System -> Search Management -> Settings -> Search Engine Configuration.

      Search Sphinx shall be installed first, and then connected to your store.

  • High-load Cron tasks

    How to Check:

    • Install Cron Scheduler for M2.
    • Navigate to System -> Cron Scheduler by KiwiCommerce -> All cron jobs section and System -> Cron Scheduler by KiwiCommerce -> Cron job schedule timeline. Check there execution time and results of cron tasks. If some of them are stuck or executed for too long period, this is the probably cause.

    How to Resolve:

    • Disable or reconfigure all cron tasks, which are stuck or taking too much time.

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

  • If your Sphinx Search Engine is installed on the same server run the following steps:

    • Click "Reset" in Search Engine Configuration (backend)
    • Click "Restart Sphinx Daemon" in Search Engine Configuration (backend)
    • Reindex Search indexes by running bin/magento indexer:reindex catalogsearch_fulltext (CLI) or in System / Search Management / Search Indexes (Backend)
  • If your Sphinx Search Engine is installed on a remote server run the following steps:
    • Click "Generate configuration file"
    • Copy generated file to your remote server
    • Run killall -9 searchd on your remote server
    • Start sphinx daemon using the command searchd --config <path to config/sphinx.conf>
    • Reindex Search indexes by running bin/magento indexer:reindex catalogsearch_fulltext (CLI) or in System / Search Management / Search Indexes (Backend)