Meilisearch Engine

v2.2.3 Annual Subscription Updated Sep 1, 2026

Meilisearch Engine

Plugs Meilisearch into Magento's native search adapter: fast, typo-tolerant and multilingual, on hardware a small VPS can carry.
Hyvä Compatible Magento 2.4.4 Magento 2.4.5 Magento 2.4.6 Magento 2.4.7 Mage-OS 2.0 Mage-OS 2.1
€399.00
Try the live demo
  • 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

Meilisearch Engine

Replace Magento's MySQL or OpenSearch with Meilisearch — and get a search engine that's fast, typo-tolerant, multilingual, and runs on a tiny VPS. This module is a production-grade adapter on top of the open-source Walkwizus Meilisearch base: it plugs Meilisearch into Magento's native AdapterInterface, then adds the operational layer that makes it usable at scale — multi-level cache, partial sync, index protection with auto-backup, smart pagination, customer-group pricing, configurable ranking rules, and a polished Hyvä-friendly autocomplete.

Search results are cached at three levels (browser localStorage, Magento backend cache shared across users, and a dedicated category-page cache) so repeated queries never hit Meilisearch twice. A custom search proxy controller routes autocomplete through Magento, which means the backend cache is genuinely shared across all visitors instead of bypassed by direct JS calls. Behind the scenes, an ERP-driven full sync becomes a partial sync: only changed fields (qty, price, status) are pushed, with MD5 hash-based change detection.

Who it's for

  • Merchants tired of slow Elasticsearch/OpenSearch and the JVM memory bill that comes with it
  • Stores with large catalogs (10k–500k SKUs) where typo tolerance and instant autocomplete matter more than complex DSL queries
  • Multilingual stores (EN, FR, NL, ES bundled) that need translated facet labels out of the box
  • Stores driven by an ERP that imports 10–50× per day, where full reindex of Elasticsearch is overkill
  • Teams that want fine-grained control over ranking rules, searchable/filterable/sortable attributes, and document content

Key benefits

  • Full Magento search adapter — drop-in replacement for Elasticsearch via the native AdapterInterface. Compatible with category pages, layered navigation, autocomplete, and search results.
  • Enhanced autocomplete — 6-product grid with image, name, SKU, customer-group price, working Add-to-Cart button (AJAX), auto-success message. Configurable min characters and debounce.
  • Partial SKU search — auto-generated sku_parts field finds a product by 333-2-17 even if the full SKU is 0010333-2-17. Two trim strategies pre-computed at index time.
  • Multi-level cache — localStorage (browser, 15-min TTL), Magento backend cache shared across users (2-hour TTL), and category-page cache (30-min TTL). Manual flush from admin.
  • Partial sync — only changed fields (qty, price, status…) pushed to Meilisearch when ERP imports run. MD5 hash detection skips unchanged products. Batches of 10,000 by default.
  • Index protection & auto-backup — settings are backed up before every cleanIndex and auto-restored after, with validation. Last 10 backups kept under var/meilisearch_backups/. Health-check CLI command.
  • Smart pagination — ellipsis-style page numbers, jump-to-page dropdown for large result sets, item-count display, responsive mobile filter popup.
  • Customer-group pricingprice_0, price_1, price_2… indexed per customer group; the frontend picks the right one. Compatible with faceted search and price sorting. TVAC stored once, no double taxation.
  • Custom ranking rules — define your own ranking sequence (words, typo, proximity, attribute, sort, exactness, plus popularity:desc, created_at:desc and others) from the admin.
  • Index drop alerts — get an email when an index is deleted, with full operation logging.

Compatibility

  • Magento 2.4.x / Mage-OS equivalent
  • PHP 8.1, 8.2, 8.3
  • Requires wimakeit/module-core 3.0.9, walkwizus/magento2-module-meilisearch 1.0.46, meilisearch/meilisearch-php
  • Works with Hyvä, Breeze and Luma frontends
  • Meilisearch server 1.6+ required (any tier — the official Docker image is recommended)
  • Compatible with MSI (multi-source inventory) and standard single-source setups
  • Companion modules: wimakeit/module-meilisearch-ai for semantic search, wimakeit/module-indexer for catalog reindex optimization

Install this module via Composer. Make sure your auth.json is configured with your Wimakeit credentials.

Terminal
$ composer require wimakeit/module-meilisearch-engine:^2.2.3
$ bin/magento setup:upgrade
$ bin/magento setup:di:compile

Installation notes

The standard composer require + setup:upgrade + setup:di:compile flow applies. The points below cover what's specific to this module.

Required dependencies

PackageVersion
wimakeit/module-core3.0.9+
walkwizus/magento2-module-meilisearch1.0.70+
meilisearch/meilisearch-php2.0.0-beta.6+

The Meilisearch PHP SDK v2 is still a pre-release, so Composer will refuse to resolve it under the default stability. Allow it for that package only:

composer require meilisearch/meilisearch-php:^2.0.0-beta.6@beta

Composer will pull the rest automatically from the Wimakeit registry. The Walkwizus base modules (MeilisearchBase, MeilisearchCatalog, MeilisearchFrontend, MeilisearchIndices, MeilisearchMerchandising) should also be installed:

composer require walkwizus/module-meilisearch-base \
  walkwizus/module-meilisearch-catalog \
  walkwizus/module-meilisearch-frontend \
  walkwizus/module-meilisearch-indices \
  walkwizus/module-meilisearch-merchandising

External services

This module requires a Meilisearch server (1.6+).

Run Meilisearch (Docker)

docker run -d --name meilisearch \
  -p 7700:7700 \
  -e MEILI_MASTER_KEY='YOUR_MASTER_KEY' \
  -v $(pwd)/meili_data:/meili_data \
  getmeili/meilisearch:latest

Dashboard: http://localhost:7700. For production, put it behind HTTPS and firewall the master-key port.

Connection settings

Configure the server in Stores → Configuration → Wimakeit → Meilisearch Engine → Server Connection (encrypted):

SettingDefault
Server Address(empty — e.g. http://localhost:7700 or https://meilisearch.example.com)
API Key(empty — read-only search key, stored encrypted)
Master Key(empty — admin key for settings/indexes, stored encrypted; falls back to API Key)

Then point Magento at Meilisearch in Stores → Configuration → Catalog → Catalog → Catalog Search:

FieldValue
Search EngineMeilisearch
Index Prefixmagento_ (or your own)

MSI modules

Inventory modules must be enabled for stock filtering to work:

bin/magento module:enable Magento_Inventory Magento_InventoryApi \
  Magento_InventorySales Magento_InventorySalesApi \
  Magento_InventoryIndexer Magento_InventoryCatalog \
  Magento_InventoryCatalogApi Magento_InventoryConfiguration \
  Magento_InventoryConfigurationApi Magento_InventorySourceSelectionApi

ACL permissions

ResourceDefault
Wimakeit_MeilisearchEngine::config (edit module configuration)granted to Administrator role only

Configuration

Stores → Configuration → Wimakeit → Meilisearch Engine

General

SettingDefault
Enable Debug LoggingNo — leave off in production

Search settings

SettingDefault
Maximum Results10000
Autocomplete Results Limit6

Autocomplete behavior

SettingDefault
Minimum Characters3
Debounce Delay (ms)500

Search cache

SettingDefault
Enable Frontend Cache (localStorage)Yes
Frontend Cache TTL (seconds)900 (15 min)
Max Cached Queries (localStorage)150
Enable Backend Cache (Magento cache)Yes
Backend Cache TTL (seconds)7200 (2 h)
Use Search ProxyYes — routes autocomplete through Magento so backend cache is shared
Enable Category Page CacheYes
Category Cache TTL (seconds)1800 (30 min)
Flush CacheManual button in admin

Document content

SettingDefault
Include DescriptionYes
Description Max Length150 (set 0 for no truncation)

Layered navigation

SettingDefault
Enable Stock Availability FilterNo

Custom ranking rules

SettingDefault
Ruleswords, typo, proximity, attribute, sort, exactness (one per line; add popularity:desc, created_at:desc, etc.)
Reset Ranking RulesButton — restore defaults

Index drop alerts

SettingDefault
Enable Email AlertsNo
Notification Emails(empty — comma-separated list)

Embedders (AI Search)

SettingDefault
Embedders Configuration (JSON)(empty — managed by wimakeit/module-meilisearch-ai if installed)

Partial sync

SettingDefault
EnabledYes
Sync Fieldsqty, price, prixHT, status, codeDispo
Batch Size10000

Debug

SettingDefault
Throw Exceptions on Search ErrorNo — development only

CLI commands

# Server and indexes status
bin/magento wimakeit:meilisearch:status

# Push admin settings to Meilisearch
bin/magento wimakeit:meilisearch:sync-settings

# Health check + manage backups
bin/magento wimakeit:meilisearch:health
bin/magento wimakeit:meilisearch:health --backup
bin/magento wimakeit:meilisearch:health --list-backups
bin/magento wimakeit:meilisearch:health --restore=var/meilisearch_backups/backup_XXXXXXXX.json

# Clean succeeded/canceled tasks
bin/magento wimakeit:meilisearch:clean-tasks

# Reindex a specific Meilisearch index by UID
bin/magento wimakeit:meilisearch:reindex <index_uid>
bin/magento wimakeit:meilisearch:reindex <index_uid> --clear

# Reindex specific products by SKU
bin/magento wimakeit:meilisearch:reindex-skus SKU1,SKU2,SKU3

# Inspect partial-sync state
bin/magento wimakeit:meilisearch:sync-state
bin/magento wimakeit:meilisearch:sync-state --clear

Cron jobs (registered automatically)

JobSchedule
wimakeit_meilisearch_process_reindex_queue (process the per-product reindex queue)every minute
wimakeit_meilisearch_clean_tasks (purge succeeded/canceled Meilisearch tasks)daily at 2 AM

No setup needed — just make sure Magento cron is running.

Initial reindex

After install, reindex in this order:

bin/magento indexer:reindex catalog_category_product
bin/magento indexer:reindex catalog_product_category
bin/magento indexer:reindex meilisearch_categories_fulltext
bin/magento indexer:reindex catalogsearch_fulltext
bin/magento wimakeit:meilisearch:sync-settings

If you also installed wimakeit/module-indexer, you can replace the first four lines with bin/magento wimakeit:indexer:reindex-all.

Version
v2.2.3
License
Annual Subscription
Support
12 months
Last updated
Sep 1, 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ä
Compatible
Package
wimakeit/module-meilisearch-engine

Compatibility checker

Pick your stack to see if this module fits.

Compatibility 4

Yes. Meilisearch Engine is tested against Magento Open Source 2.4.4 → 2.4.7, Adobe Commerce on the same line, and Mage-OS 2.0+ — on PHP 8.1, 8.2 and 8.3. The Specifications tab lists the exact tested combinations. If your stack is in the list, we guarantee a clean install. Wimakeit is an Adobe-certified Magento agency based in Presles (Charleroi / Namur region), Wallonia, Belgium and runs every module against the same matrix we ship to enterprise clients across Belgium, France and the Netherlands.
Yes — fully. Meilisearch Engine ships a native Hyvä-compatible frontend (Tailwind + Alpine.js) and integrates with Hyvä Checkout when applicable. No companion fallback module needed. Every Hyvä-marked module is built and maintained by the same Wimakeit team that ships Hyvä builds for production stores.
Hyvä Storefront (Tailwind + Alpine.js, server-rendered) and Hyvä Checkout (React-based, headless on top of Magento) are two distinct packages. Meilisearch Engine ships native Hyvä Storefront compatibility — its frontend is rendered through Hyvä templates with no Luma fallback. Hyvä Checkout integration is delivered when the module has a checkout-step touchpoint (custom payment input, terms checkbox, etc.); otherwise the module runs server-side without any Hyvä Checkout customisation needed. See the Specifications tab for the exact Hyvä integration scope of this module.
Yes. Meilisearch Engine respects the standard Magento scope (default / website / store / store_view). Every configuration is overridable per store view. Frontend labels use Magento's standard translation files — shipped in French, English and Dutch out of the box. Currencies follow your Magento currency setup with no extra wiring. A typical Wimakeit Magento store runs an fr_BE / nl_BE / en_GB triplet from a single backend — Meilisearch Engine is ready for this B2B / international setup.

Pricing & licensing 4

€199 — one-time payment, perpetual licence, no recurring fees. Includes 1 year of minor updates + email support in French, English and Dutch, 1 production domain + 1 staging/dev domain. Renewing the support window after year 1 is optional. Volume licences are negotiated directly — write to contact@wimakeit.com for agency or multi-store pricing.
Yes. Meilisearch Engine has a live demo on demo.wimakeit.be/module-meilisearch-engine where you can poke around the admin and frontend with a real install pre-populated with sample data. For longer evaluations, request an evaluation licence via our contact form — evaluations cover the same scope as the paid licence and convert to a permanent key on purchase.
We review refund requests case by case. If the module doesn't deliver what was advertised, email contact@wimakeit.com from the address tied to your licence. The refund policy is published on the terms page and applies to every module sold through this marketplace.
Meilisearch Engine is distributed under a commercial proprietary licence — not MIT, GPL or any other open-source licence. The PHP source ships in vendor/wimakeit/ once you composer require the package, so you can read it, audit it, and patch it locally for your own Magento install. You may NOT redistribute it, sublicense it, publish it on a public package registry, or sell it on. One licence = one production domain + one staging/dev domain (see terms for the full EULA). Wimakeit modules are NOT part of Magento's open-source repository on packagist.org — they are distributed exclusively via the private Composer registry packages.wimakeit.be.

Installation & updates 6

Run composer require wimakeit/module-meilisearch-engine:^1.12.2, then bin/magento setup:upgrade, bin/magento setup:di:compile, and finally bin/magento cache:flush. The Installation tab on this page lists every configuration step (ACLs, cron jobs, default values) so a deploy takes minutes, not hours. If you need a hand, Wimakeit offers Magento installation services from our Wallonian office (Presles, between Charleroi and Namur).
Step 1: get a token on packages.wimakeit.be → My account → Tokens. Step 2: at the root of your project add to auth.json: {"http-basic": {"packages.wimakeit.be": {"username": "YOUR-EMAIL", "password": "YOUR-TOKEN"}}}. Step 3: register the repo: composer config repositories.wimakeit composer https://packages.wimakeit.be. Step 4: composer require wimakeit/module-meilisearch-engine:^1.12.2. In CI/CD pipelines, inject COMPOSER_AUTH as a JSON env var instead of committing auth.json.
Most merchants are live within 30 minutes: composer install (1-2 min) → setup:upgrade + di:compile (5-10 min depending on stack size) → admin configuration (5-15 min following the Installation tab) → smoke test on a product or order. Allow extra time if you have a custom theme overriding similar templates. The Wimakeit team has shipped this exact module to B2B and DTC stores across Belgium.
Meilisearch Engine is built for Magento 2.4.x / Mage-OS 2.0+ and has no Magento 1 equivalent. When migrating from Magento 1, the Wimakeit team handles the audit, the data migration and the integration of Meilisearch Engine into the new backend as part of a Magento migration project. Migrating from Adobe Commerce to Mage-OS is transparent for Meilisearch Engine: same composer require, same module code, same database schema — no fork to maintain, no licence change.
Updates ship through your composer dependency (this exact package), hosted on Wimakeit's private Composer repository at packages.wimakeit.be. Each release is announced on the Changelog tab + the Wimakeit news and follows semantic versioning — composer update is safe within a major.
All .phtml templates are overridable from your theme: copy the file into app/design/frontend/{YourVendor}/{theme}/Wimakeit_{Module}/templates/ keeping the same relative path. Blocks, ViewModels and Helpers are overridable via DI preference in your own custom module — declare <preference for="Wimakeit\…\OriginalClass" type="YourVendor\Override\Class" /> in etc/di.xml. Layout XML is extended (preferred) or overridden the standard Magento way. Wimakeit modules never use the final keyword on classes you might reasonably want to override — overriding is a first-class scenario, not a hack.

Support & security 3

Open a ticket through the contact form on wimakeit.be or email contact@wimakeit.com with the module name, version, Magento/Mage-OS version and the steps to reproduce. Fixes ship in the next patch release. Wimakeit support is staffed in French, English and Dutch on business days (CET working hours).
Send security reports privately to contact@wimakeit.com with a clear [SECURITY] subject prefix — please include the module name, version and the steps to reproduce. We acknowledge promptly on business days and credit reporters in the Changelog if they wish. Wimakeit is a Belgian SRL (société à responsabilité limitée) bound by Belgian and EU privacy and disclosure law.
Yes. Meilisearch Engine stores only the data its feature scope requires, never tracks shoppers across sites, and ships zero third-party calls by default. Combine it with the Wimakeit GDPR module to publish cookie banners and data-subject request forms compliant with Belgian, French and Dutch DPA guidance. Wimakeit's EU-based hosting partners (OVH Roubaix / Gravelines, Cblue Gembloux) keep every customer's data inside the EU.

About Wimakeit 1

Wimakeit is an Adobe-certified Magento partner agency based in Presles, Wallonia (between Charleroi and Namur), Belgium, building Magento and Mage-OS stores since 2020 across BE / FR / NL. Every module on this marketplace runs in production on at least one Wimakeit client (we eat our own dog food). Direct line to the developers who built the code, multilingual support (FR / EN / NL), CET business hours, no offshore handoff. See our portfolio for the kind of Magento builds we ship.

Found something not covered by the FAQ?

Report a bug or ask a question — the form is prefilled with this module.

Report a bug

Changelog

Categories: Security, Feature, Fix, Perf, Admin, Deps.

[2.2.1] - 2026-08-10

Fix

  • Category pages no longer all return the same products: cached listings are keyed per category, filter set and customer group.
  • Layered navigation filters and product ranking now survive a cache hit instead of coming back empty.
  • Cached results are cleared when the catalog is reindexed, a product changes or a category is saved — no more stale listings until the cache expires.
  • Products are no longer left behind in the index when a deletion and an update overlap.

Perf

  • Full page cache restored across the whole storefront: a search block was disabling it on every frontend page, not just on search and category pages.
  • Search no longer writes a log line per request, which filled log files on busy catalogs.

[2.1.2] - 2026-08-07

Deps

  • PHP 8.5 certified — constraint widened to >=8.1 <8.6.

[2.1.1] - 2026-07-09

Fix

  • Installation no longer fails during setup:di:compile: three catalog attribute mappers still carried an outdated signature.

[2.1.0] - 2026-07-08

Feature

  • Layered navigation now works with Meilisearch: every "filterable in navigation" dropdown attribute is indexed so its facet returns the matching products.

[2.0.0] - 2026-07-07

Feature

  • Compatible with Magento / Mage-OS 2.4.9 through walkwizus 1.0.70 and the Meilisearch PHP v2 SDK.

Fix

  • Indexing writes documents again: a full reindex used to report success while pushing nothing to Meilisearch.
  • Category and search pages return products again instead of coming back empty.
  • Price-per-customer-group and category indexing overrides apply again after the upstream code was relocated.

Deps

  • Requires walkwizus/magento2-module-meilisearch ^1.0.70 and meilisearch/meilisearch-php ^2.0.0-beta.6. The Meilisearch SDK v2 is still pre-release, so the consuming project must allow its beta stability.

[1.12.8] - 2026-06-30

Fix

  • Category pages always show their products: when a category's position sort is missing from the search index, the proxy automatically retries without it instead of returning an empty page.

[1.12.7] - 2026-06-29

Fix

  • Accents now display correctly in autocomplete and search results: the search proxy decodes leftover HTML entities (such as &#233; for é) in indexed text — no reindex needed.

[1.12.6] - 2026-06-24

Fix

  • Products kept available by a manual stock override or a backorder are no longer indexed as out of stock.

[1.12.5] - 2026-06-05

Deps

  • PHP 8.4 deprecation cleanup — explicit-nullable params across constructors. No behavior change.

[1.12.4] - 2026-06-05

Deps

  • Marketing documentation refreshed to list PHP 8.4 in the supported PHP range.

[1.12.3] - 2026-06-05

Deps

  • PHP 8.4 certified — constraint widened to >=8.1 <8.5.

[1.12.2] - 2026-05-28

Fix

  • Adapter no longer crashes when Meilisearch returns a facet that isn't marked as filterable — it falls back to a safe empty result instead of throwing.

[1.12.1] - 2026-05-28

Fix

  • Autocomplete prices respect customer VAT settings again. calculateDisplayPrice reapplies the tax-inclusive / tax-exclusive rule per customer, so the price shown in the autocomplete matches the cart and product page.

[1.12.0] - 2026-05-28

Fix

  • Bundle product prices in autocomplete and search now match the storefront. The price mapper computes the rendered bundle price (option selections + price view) instead of only the base price.

[1.11.0] - 2026-05-28

Fix

  • Bundle products whose description is stored as an array no longer cause "Array to string conversion" warnings during reindex — the description truncate helper handles both shapes.

[1.10.34] - 2026-05-27

Feature

  • Autocomplete now exposes hasSearchedTerm, noResults and showAutocomplete Knockout observables, so themes can render a real "no results" state and keep the autocomplete container visible while loading.

[1.10.33] - 2026-05-12

Admin

  • Admin dashboard widget code extracted to companion module wimakeit/module-meilisearch-engine-admin-dashboard. The main module is now installable on stores that don't use wimakeit/module-admin-dashboard.

Deps

  • To keep the Meilisearch indexer/health widget on the admin dashboard, install wimakeit/module-meilisearch-engine-admin-dashboard alongside this module.

[1.10.32] - 2026-05-11

Feature

  • wmi_stock_status is now part of the partial-sync field map — stock status changes propagate to Meilisearch incrementally instead of waiting for a full reindex.

[1.10.31] - 2026-05-10

Feature

  • New Enable Debug Logging toggle (Stores → Configuration → Wimakeit → Meilisearch Engine → General), off by default. 9 hot paths (reindex queue cron, task cleanup, cache observer, multisearch controller, searchable updater, search cache, sync state, search adapter, partial sync) emit info/debug/notice/warning only when the toggle is on; error/critical always log.

Perf

  • Production stores stop emitting tens of thousands of trace lines per day in var/log/system.log once the toggle is left off.

Deps

  • Requires wimakeit/module-core 3.0.9+ for the shared debug logger virtual type.

[1.10.30] - 2026-05-08

Admin

  • Admin menu group standardized — module appears under a top-level Wimakeit_MeilisearchEngine entry with a Settings child that opens directly on the configuration section.
  • Config section path renamed from wimakeit_meilisearch to wimakeit_meilisearch_engine for consistency with the other Wimakeit modules. A data patch migrates existing core_config_data rows automatically on setup:upgrade — no manual reconfiguration needed.

[1.10.29] - 2026-04-29

Deps

  • Certified PHP 8.1 → 8.3 support. Composer php constraint tightened to >=8.1 <8.4.
  • Fixed implicit-nullable parameter declarations flagged by PHP 8.4-rc deprecation notices.

[1.10.28] - 2026-04-23

Fix

  • Category listings on stores with HT catalog prices (tax/calculation/price_includes_tax=0) now apply VAT correctly. Block\CustomerGroup::isPriceIncludingTax() returns the real Tax\Model\Config::priceIncludesTax() instead of a hard-coded true, so both TTC and Anowave TaxSwitch HT toggles render correct prices on autocomplete and live-search.
  • New ViewModel\Ssr preference applies the same tax rule server-side so SSR HTML of category and search listings matches the client-side rendering. Index stays raw (no risk of double-taxation elsewhere).

[1.10.27] - 2026-04-23

Fix

  • Reverted 1.10.26 (VAT applied at index time). That approach would have caused double-taxation on autocomplete and live-search paths, which apply VAT client-side. Prices are back to being indexed HT when the catalog is configured as HT — VAT is applied in the theme override instead.

[1.10.22] - 2026-04-16

Fix

  • Empty product grids on pages with a price facet (e.g. /fr/nos-libraires/<name>) fixed. IndexSettingsUpdater now registers price_<groupId> for every customer group as both filterable and sortable, so Meilisearch accepts the facet query the adapter builds.

[1.10.16] - 2026-03-19

Fix

  • Category page filters, sorting and pagination work again. The isSsrMode() check in search.js was disabling JS subscriptions on SSR-rendered category pages — now SSR initial state is used for first render only, while JS handles dynamic user interactions.
  • Loading spinner no longer stays stuck on SSR pages (added searchState.isLoading(false) after init).
  • Autocomplete hitsPerPage now respects catalog/frontend/grid_per_page instead of a hard-coded fallback.

[1.8.7] - 2026-02-24

Feature

  • Progress bar support during Meilisearch sync — new progressCallback parameter on syncBatch() and syncFromCsv() for real-time CLI feedback.

Fix

  • SKU values are now consistently handled as strings throughout SyncStateManager and PartialSyncService to prevent PHP type errors.
  • getIndexName() correctly resolved (was incorrectly calling resolve()).

[1.8.6] - 2026-02-24

Fix

  • Added string casting on SKU in SyncStateManager iteration loops (preloadHashes, updateHashBatch, getChangedSkus, deleteHashes).
  • Added string casting on SKU in PartialSyncService::syncBatch().

[1.8.5] - 2026-02-24

Fix

  • Index name resolver: switched from resolve() to getIndexName() for compatibility with Walkwizus MeilisearchBase.

[1.8.4] - 2026-02-24

Fix

  • SyncStateManager::hasChanged(), getStoredHash(), updateHash() now accept string|int for the SKU parameter with internal string casting.

[1.8.3] - 2026-02-24

Fix

  • PartialSyncService::buildPartialDocument() accepts int|string for entityId (matches what fetchPairs returns).

[1.8.2] - 2026-02-24

Fix

  • Replaced non-existent ClientManager with ConnectionManager from Walkwizus MeilisearchBase.

[1.8.0] - 2026-02-23

Feature

  • Partial Sync Service: send only changed fields (stock, price, status) to Meilisearch instead of full documents. Drastically reduces indexing load on ERP-driven imports.
  • SyncStateManager performs hash-based change detection to skip unchanged products.
  • New PartialSyncConfig admin section.

Admin

  • Sync now uses partial updates for stock/price changes; full reindex only when needed.

[1.6.4] - 2026-02-23

Fix

  • Search proxy UTF-8 error fixed via sanitizeUtf8() to handle malformed characters in Meilisearch responses (prevents JSON serialization errors).
  • Search proxy SearchQuery conversion fixed ("Call to a member function toArray() on array") by converting frontend JSON arrays to proper Meilisearch\Contracts\SearchQuery objects.
  • Double tax on prices fixed (e.g. 20.05 → 21.25). Meilisearch stores TVAC, so priceIncludesTax now always returns true in CustomerGroup block.

Admin

  • Simplified calculateDisplayPrice() in product.js — prices are passed through (Meilisearch already stores TVAC).

[1.6.3] - 2026-02-19

Feature

  • Meilisearch Search Proxy — new controller /meilisearch/search/multisearch routes autocomplete searches through Magento, so the backend cache is truly shared across all users/browsers. Configurable via Admin → Search Cache → "Use Search Proxy" (on by default). Falls back to direct Meilisearch if the proxy fails.

Admin

  • Autocomplete JS now calls the Magento proxy by default; direct Meilisearch call remains the fallback.

[1.6.2] - 2026-02-19

Fix

  • Backend cache now shared across users/browsers. SearchCacheService was using a generic CacheInterface instead of the dedicated meilisearch_search cache type — switched to FrontendPool so the cache type is honored. Respects bin/magento cache:enable meilisearch_search.

[1.6.1] - 2026-02-19

Feature

  • Multi-level cache system with configurable TTL. Frontend localStorage cache (default 5 min, max 100 queries) for autocomplete; backend Magento cache (default 15 min) shared across users; native Magento cache type meilisearch_search so the standard cache management UI and CLI work.
  • New admin Autocomplete Behavior group: Minimum Characters (default 3) and Debounce delay (default 500 ms).
  • New Debug section with "Throw On Error" — surfaces search errors to users instead of silent empty results (development only).
  • New admin button to manually flush the Meilisearch backend cache.

Security

  • API key validation in RetryableApiClient rejects placeholder values (CHANGE_ME, YOUR_API_KEY, etc.).
  • Search errors no longer expose stack traces by default.

Perf

  • Optimized task polling with exponential backoff (250 ms initial, 3 s max).
  • Model\Config has a bounded in-memory cache (MAX_CACHE_SIZE 100) for parsed config values.
  • DescriptionTruncatePlugin::truncateHtml() rewritten with early exits and fewer string operations.

Fix

  • Unbounded memory leak in Observer\ReindexProductAfterSave (static $processedProductIds now capped at 1000).
  • ObjectManager anti-pattern in SearchAdapter\ResponseFactory replaced with proper factory injection.
  • N+1 queries in Cron\ProcessReindexQueue replaced with batch product preload and attribute caching.
  • Reflection in SafeIndexerPlugin and SaveIndexValidatorPlugin replaced with injected SearchIndexNameResolver.
  • Silent search failures in SearchAdapter\Adapter get user-facing error messages (gated by debug mode).

[1.4.7] - 2026-02-06

Feature

  • New Document Content admin group: toggle Include Description on/off and set Description Max Length (default 150 chars). Truncates at word boundary, strips HTML, normalizes whitespace.
  • DescriptionTruncatePlugin on AttributeMapper::map() removes or truncates description/short_description depending on config.

Fix

  • Synced system.xml with upstream — restored the missing autocomplete_limit field and layered_navigation group.

Perf

  • Index size optimization: descriptions can be excluded entirely or trimmed to reduce Meilisearch index footprint.

[1.3.14] - 2026-01-20

Deps

  • Composer patch for Walkwizus SettingsManager to fix return-type compatibility with meilisearch-php 1.16.x (reverts return types to array).

[1.3.11] - 2026-01-19

Fix

  • SkipWalkwizusIndexerPlugin return type fixed from void to IndexerInterface (resolves "Return value must be of type IndexerInterface, null returned" during catalogsearch_fulltext reindex).
  • Plugin re-added to di.xml (was missing from source module).

[1.3.6] - 2026-01-09

Fix

  • SafeIndexerPlugin reflection error resolved by reading the property from BaseIndexerHandler instead of the interceptor (was failing during reindex with "Property searchIndexNameResolver does not exist").

[1.3.5] - 2026-01-08

Fix

  • .block.filter .filter-content max-width 100% on mobile.

[1.3.4] - 2026-01-08

Fix

  • Mobile filter button visibility (display: flex !important).
  • Z-index hierarchy fixed: button (900), overlay (999), popup (1000).
  • .filter-option padding set to 5px.
  • noUiSlider handle positioning fixed (top: -3px, 20 px size).
  • Desktop hide rule loosened so the mobile override applies properly.

[1.3.3] - 2026-01-08

Feature

  • Mobile Filter Popup: floating "Filters" button fixed to the bottom of the screen, badge counter for active filters, slide-in popup from the right (85% width, max 340 px), dark overlay with click-to-close and Escape-key support, sticky footer with "Apply Filters" button, iOS scroll lock with position restoration.
  • Override of Walkwizus facets.html template with full mobile popup structure.

Admin

  • Refactored layer-navigation styles: clear desktop/mobile separation, CSS custom property --header-height, transform/visibility for smooth animations.

[1.3.1] - 2026-01-08

Feature

  • Smart pagination JS: ellipsis-style page numbers as a Knockout.js override of the Walkwizus pagination component.
  • Full styles for layered navigation (checkbox, swatch, price slider).

Fix

  • Pagination was rendering every page number instead of using ellipsis.

[1.3.0] - 2026-01-08

Feature

  • New IndexHealthMonitor service to detect missing attributes.
  • New SettingsBackupService for automatic backup/restore of index settings (stored in var/meilisearch_backups/).
  • New IndexSettingsValidator to verify settings were actually saved on Meilisearch.
  • New RetryableApiClient HTTP client with exponential backoff and retry.
  • New SaveIndexValidatorPlugin validates index health after every saveIndex to catch silent failures.
  • New CLI Health Check command (wimakeit:meilisearch:health): check health, create backups (--backup), list backups (--list-backups), restore (--restore=…).
  • Configurable Maximum Results admin setting (was hard-coded to 10 000).
  • Smart pagination with ellipsis, jump-to-page dropdown for >10 pages, item-count display, responsive design.
  • Translation files for en_US, fr_FR, nl_NL, es_ES covering all UI strings.

Security

  • escapeFilterValue() in Mapper.php prevents filter injection.
  • escapeHtml() in product.js prevents XSS on autocomplete render.
  • SSL verification (CURLOPT_SSL_VERIFYPEER) enabled in RetryableApiClient.
  • File-permission checks in SettingsBackupService before writing.
  • All settings changes logged with full context for audit.

Perf

  • Layered-navigation facet config (labels, options) cached in memory per store.
  • CleanTasksCommand and CleanTasks cron switched to RetryableApiClient (replaces raw cURL).

Fix

  • Settings no longer silently lost during cleanIndex (auto-backup + auto-restore).
  • Attribute updates validated to ensure they were actually persisted.
  • Strict comparison for swatch type checks.
  • Division-by-zero in jitter calculation fixed.

[1.0.6] - 2026-01-08

Fix

  • SafeIndexerPlugin return types corrected (must return IndexerInterface, not void). Prevents "Return value must be of type IndexerInterface, null returned" during indexation.

[1.0.2] - 2025-12-15

Fix

  • Removed hard dependency on Anowave\TaxSwitch in the CustomerGroup block — prevents errors when that module is not installed.

[1.0.0] - 2024-12-15

Feature

  • Initial release.
  • Custom Meilisearch search adapter for Magento 2.
  • Enhanced autocomplete frontend (6-product grid) with image, name, SKU, price, AJAX Add-to-Cart.
  • Partial SKU search (sku_parts field).
  • Dynamic attribute management (searchable / filterable / sortable from admin).
  • Auto-configuration of Magento attributes ("Use in Search = Yes" toggled automatically).
  • New CLI wimakeit:meilisearch:sync-settings.
  • Customer-group-based pricing (price_<group>) in autocomplete and listings.
  • Custom ranking rules support.

Deps

  • Requires walkwizus/magento2-module-meilisearch.

Found a bug? Tell us about it.

A short form opens in a new tab — the module name and your language are already filled in. Share what you tried, what went wrong, and we will get back to you within one business day.

Report a bug for Meilisearch Engine
Module SKU: wimakeit-module-meilisearch-engine · Language: en_US

Need help?

Our team is available to assist with integration.

Contact us
Planifier un appel