Skip to main content

Updating, disabling and uninstalling

Version history. These instructions cover 1.0.1. Upgrading from 1.0.0 or 0.1.34 does not require an index rebuild solely for this release. Adding indexed fields or changing sources still requires a rebuild.

Updates in version 1.x​

Version 1.x removes Zorka’s private updater, bundled access key and Updates tab. Instructions for that tab belong to historical 0.x releases. Use a package supplied by the developer or Bitrix Marketplace when the update becomes available there. Updating this guide does not update your site automatically.

Through Bitrix Marketplace​

  1. Back up site files and the database.
  2. Open Marketplace → Solution updates, check available updates and select zorka.search.
  3. Complete installation, open the settings and check the version under Marketplace → Installed solutions.
  4. Reload storefront and CRM pages and test a product name, a code and a section.

From a supplied full package​

  1. Back up files and the database. Obtain zorka.search-1.0.1.zip from the developer.
  2. Copy the contents of its zorka.search directory over the existing /bitrix/modules/zorka.search/. Avoid a second nested directory. Updating does not require uninstalling the module.
  3. When upgrading manually from 0.x, remove the old updater files: lib/updater.php, lib/updatepackage.php, install/update-access.php, assets/updates.js. The standard Marketplace migration package removes these files and three legacy status options automatically. Existing backup directories are retained.
  4. Reopen the settings, check the version, save settings and test search. The selected engine, settings and index are retained. Installing Manticore remains a separate button action.

Settings-save fix for an installed 1.0.0​

For Class "CCatalogSku" not found, obtain zorka.search-1.0.1-hotfix-settings.zip. Back up and replace only these two files from its zorka.search directory:

  • /bitrix/modules/zorka.search/lib/admin/settings.php;
  • /bitrix/modules/zorka.search/install/version.php.

Reopen the settings and save again. This fix does not require uninstalling, resetting settings or rebuilding the index. Cause and verification.

If the old version remains visible, first check the actual loaded path, duplicate copies under /local/modules/, and file contents. Only after confirming the new files should you investigate the hosting provider’s OPcache refresh procedure.

Disable integrations​

Uncheck Поиск магазина (Storefront search) and/or Товары и категории в CRM Б24 on the Catalogs tab, save and reload open pages. Disabling storefront integration restores the previously saved search engine. A later engine choice made by the administrator is preserved.

Uninstall and restore native operation​

  1. Use Marketplace → Installed solutions → zorka.search → Uninstall. Keep the module directory in place until uninstall completes: it contains the cleanup code.
  2. Read any cron cleanup warning. If automatic cleanup is unavailable or jobs were created manually, remove the module’s own jobs from the site user’s crontab.
  3. Fully reindex native Bitrix search using the link on the uninstall completion page.
  4. Reload open storefront and CRM pages and test native results.

The previous engine is restored, including an originally absent engine option. A later manual choice is retained. The module removes its handlers, agent, own cron blocks and unchanged integration files. Other jobs and user-modified files are preserved. Managed Manticore is stopped and automatic restart disabled; its data is retained. An external Manticore service used by other projects is not removed.

Products, sections, properties, prices and stock data are retained. Module index tables, settings and synonyms remain for reinstalling and no longer participate in site operation once the module is unregistered. Reinstallation does not enable storefront or CRM integration automatically.

Rollback of 1.0.0 was tested on a separate BitrixVM with native Bitrix, MySQL, an absent option and a later manual engine change. Native search, suggestions and CRM also worked with the module directory physically absent. Uninstall code is unchanged in 1.0.1. This does not replace testing custom modifications on your site.

Returning to an older release​

Restore a consistent backup of files and data. Since 0.1.23, phrase synonyms use a separate table; replacing files alone does not copy new dictionary changes back into the old option.