Search Pro
v1.6.1
Search Pro
- Updates and support included for 12 months
- License key delivered immediately by email
- 30-day money-back guarantee
- Full documentation included
- Compatible with Hyvä themes
- Composer-ready installation
**Search Pro** is the paid extension of wimakeit/module-search. It adds merchandising and analytics features on top of the free autocomplete module.
Installeer deze module via Composer. Zorg ervoor dat uw auth.json is geconfigureerd met uw Wimakeit-inloggegevens.
$ composer require wimakeit/module-search-pro:^1.6.1
$ bin/magento setup:upgrade
$ bin/magento setup:di:compile
- Versie
- v1.6.1
- Ondersteuning
- 12 maanden
- Last updated
- 10 nov. 2026
- Magento
- Magento 2.4.4 Magento 2.4.5 Magento 2.4.6 Magento 2.4.7 Mage-OS 2.0 Mage-OS 2.1
- PHP
- PHP 8.1 PHP 8.2 PHP 8.3
- Hyvä
- Compatibel
- Pakket
-
wimakeit/module-search-pro
Compatibility checker
Pick your stack to see if this module fits.
v1.6.1
- The category autocomplete took a minute or more per query on a large tree (Rack-It: 3,950 categories), and a few keystrokes tied up every PHP worker. The check for a disabled ancestor was a correlated NOT EXISTS that MariaDB ran against the whole tree for every row. The disabled subtrees are now read once and applied as path filters: about 0.1 s per query, same results.
v1.6.0
- Category autocomplete: every word of the query has to appear, in any order, in one of the searched attributes. "galerie citan" now finds "Galerie de toit pour Mercedes-Benz Citan", which the whole phrase as one wildcard never matched. One-letter words are ignored and a query keeps at most six words.
- Category suggestions are ranked broadest first (lowest level), then in the menu's order (family position, then own position), then by name, instead of alphabetically.
Fixed
- A category under a disabled ancestor was suggested although the menu hides it, and categories of another store's tree could take the slots before being filtered out, leaving fewer suggestions than the limit.
- SQL errors in the category lookup are logged instead of silently returning no suggestion.
v1.5.1
- A query matching a common substring of product names ("kit chaine") showed no product in the autocomplete while announcing thousands of results: the substring matches were placed first and the candidate list was capped right after, which pushed every search-engine hit out. When those substring matches were not visible in the store, nothing was left. The cap now only applies to the substring matches.
Een bug gevonden? Laat het ons weten.
Een kort formulier opent in een nieuw tabblad — de modulenaam en uw taal zijn al ingevuld. Beschrijf wat u probeerde, wat misging, en wij komen binnen één werkdag bij u terug.
Een bug melden voor Search ProHulp nodig?
Ons team helpt u graag met de integratie.