Skip to main content

zorka.search

zorka.search (zorka.search) searches products, offers and catalog sections in on-premise Bitrix. It builds its own index from original field values and connects it to storefront search and the modern Bitrix24 CRM product selector.

This guide covers 1.0.1, including the settings-save fix. Version 1.x removes Zorka’s private updater, bundled key and Updates tab. Follow the update instructions for a package supplied by the developer or an available Bitrix Marketplace update.

Version history and release descriptions.

Features​

  • Distinguishes string codes such as 000123 and 123, preserving zeros and punctuation.
  • Supports exact values, word matching and substring matching. Product-name substring search finds PASSAT-150 for passat 150.
  • Lets you enable basic fields and adjust match ranking.
  • Places sections first in standard autocomplete and adds their products when no products match directly.
  • Supports section aliases and product-name phrase groups such as iphone = айфон.
  • Tries an English-to-Russian keyboard layout correction when the original search returns no results.
  • Queues changes made through Bitrix APIs and rebuilds products or sections separately, through the browser or cron.

Get started​

  1. Install the module and select catalogs.
  2. Configure fields and ranking.
  3. Build the index and test queries in the admin panel.
  4. Connect the storefront and CRM.
  5. Optionally add synonyms and a cron schedule.

For existing installations, see updates and removal and troubleshooting.

The search index​

The module matches queries against selected catalogs using its own string index. Standard storefront results also use Bitrix URL and permission metadata. Native infoblock and property indexing flags therefore still apply; the module's rebuild updates the required metadata through Bitrix APIs.

It cannot restore zeros already lost when a numeric property was saved. Store identifiers with leading zeros in a string property.

This version does not implement morphology or general typo correction. Russian пушка and пушки are not automatically equivalent. Use a suitable fragment or explicit synonyms. See integration limits.

Optional Manticore engine: installation and connection.

Version 1.0.0 improves MySQL candidate filtering by selected catalogs. MySQL and Manticore retain the same literal matching rules. Installing Manticore remains a separate Install and enable action.