Magento – where can i remove the resultnumber for search

ce-1.9.0.1search

enter image description here when adding a search term,sometimes ther eis a dropdown with results sowing also a number before it (the number of expected results?)

Is that a setting somewhere or would i need to do something in code?

thanks

Best Answer

To explain what happens during your search auto-suggest, I add some information about the search-functionality related to this here:

Searching for 'trousers' (actually 'trou') in the demo shop: GET http://demo.magentocommerce.com/catalogsearch/ajax/suggest/?q=trou gives you the following return via AJAX:

<div id="search_autocomplete" class="search-autocomplete" style="position: absolute; left: 0px; top: 40px; width: 300px; display: none;">
  <ul>
    <li class="selected" style="display:none"></li>
    <li class="odd first" title="trousers">
       <span class="amount">1</span>
       trousers
    </li>
    <li class="even last" title="trouser">
       <span class="amount">4</span>
       trouser
    </li>
  </ul>
</div>

From the request above you can see that the suggestAction from the CatalogSearch AjaxController.php is called. The suggestAction calls $this->getResponse()->setBody($this->getLayout()->createBlock('catalogsearch/autocomplete')->toHtml()); to return the search-output. Opening app/code/core/Mage/CatalogSearch/Block/Autocomplete.php you will see that the HTML-code for your autosuggest-text is created there which is shown above.

In the _toHtml() function there is an inline-element named <span class="amount"> which shows the number of results for the term. You might have a CSS-rule for .amount or one of the other CSS-classes around .search-autocomplete which were modified. Or there might have been someone/something rewriting the app/code/core/Mage/CatalogSearch/Block/Autocomplete.php block class.

Related Solutions

Magento – Removing catalog/layer/view.phtml gives wrong search results

The key to the fact that the layer block needs to be there can be found in Mage_CatalogSearch_Block_Layer in the construct.

/**
 * Internal constructor
 */
protected function _construct()
{
    parent::_construct();
    Mage::register('current_layer', $this->getLayer(), true);
}

The second line is the key: Mage::register('current_layer', $this->getLayer(), true); without this line none of the search results will display correctly. What this does is tell the system what the current state of the search is.

This will set the current layer as type Mage_CatalogSearch_Model_Layer but if this line is not run then later on the layer gets set as type Mage_Catalog_Model_Layer. The two models have two similar but different prepareCollection functions.

Mage_CatalogSearch_Model_Layer

Has an important call to addSearchFilter

public function prepareProductCollection($collection)
{
    $collection
        ->addAttributeToSelect(Mage::getSingleton('catalog/config')->getProductAttributes())
        ->addSearchFilter(Mage::helper('catalogsearch')->getQuery()->getQueryText())
        ->setStore(Mage::app()->getStore())
        ->addMinimalPrice()
        ->addFinalPrice()
        ->addTaxPercents()
        ->addStoreFilter()
        ->addUrlRewrite();

    Mage::getSingleton('catalog/product_status')->addVisibleFilterToCollection($collection);
    Mage::getSingleton('catalog/product_visibility')->addVisibleInSearchFilterToCollection($collection);

    return $this;
}

Mage_Catalog_Model_Layer

Has no addition of addSearchFilter and does not set or filter on the store.

public function prepareProductCollection($collection)
{
    $collection
        ->addAttributeToSelect(Mage::getSingleton('catalog/config')->getProductAttributes())
        ->addMinimalPrice()
        ->addFinalPrice()
        ->addTaxPercents()
        ->addUrlRewrite($this->getCurrentCategory()->getId());

    Mage::getSingleton('catalog/product_status')->addVisibleFilterToCollection($collection);
    Mage::getSingleton('catalog/product_visibility')->addVisibleInCatalogFilterToCollection($collection);

    return $this;
}

Magento – How tomprove Native Magento Search Functionality

The key problem of native magento search is that search use "OR" logic. I.e. if you receive correct results for search phrase with one word, you will receive wrong result for search phrase with 2+ words.

You can change search logic in core file Fulltext.php (code/core/Mage/CatalogSearch/Model) http://mirasvit.com/qa/magento-search.html

Or use ready solution (Mirasvit Sphinx Search Ultimate) with much better search logic/algorithm http://mirasvit.com/magento-extensions/sphinx-search-ultimate.html

Best Answer

Related Solutions

Magento – Removing catalog/layer/view.phtml gives wrong search results

Magento – How tomprove Native Magento Search Functionality

Related Topic