Heurix Search intercepts WooCommerce product search and replaces the results\nwith ones computed by the Heurix engine -- without touching your templates, your\nfaceted filters or your product pages. Only which products come out, and in\nwhat order, changes.<\/p>\n\n
What the plugin does:<\/strong><\/p>\n\n What the plugin does not do (v0.2.1):<\/strong><\/p>\n\n The headers above carry only versions that have REALLY BEEN RUN. Recorded on\n22 September 2026, completed on the 23rd.<\/p>\n\n ONE OF THOSE LINES IS LESS PRECISE THAN THE MEASUREMENT, AND THE PARSER IS WHY.\n Tested up to says 7.1; WordPress 7.1.2 is what ran. Plugin Check 2.1.0 -- the\nofficial wordpress.org tool -- rejects the third number: \"invalid_tested_upto_minor\n[...] should only include major versions 7.1\", an ERROR, measured on this plugin\non 23 September 2026. The exact number is on the WordPress line below.<\/p>\n\n What this means for you: on WooCommerce 6.0 or older, Heurix search shows the\nfirst page and returns an empty second one. The plugin does not detect this -- it\ndoes not read the WooCommerce version, only whether it is present.<\/p>\n\n THE TWO BOUNDS GUARD EACH OTHER, AND THAT IS MEASURED. WordPress refuses to\nactivate a plugin whose So \"Requires at least: 5.9\" is not an idle line. WordPress 5.9 to 6.2 officially\naccept PHP 5.6.20, and we have exercised them only under 8.1 -- but a site on\nPHP 7.x cannot activate this plugin at all, since \"Requires PHP: 8.1\" IS STILL A PRECAUTIONARY BOUND. 8.1.34 and 8.5.10 are\nexercised; nothing below. It is the one holding the whole thing up, and it has\nnever been taken down.<\/p>\n\n A THIRD BOUND, DECLARED ON PURPOSE: WooCommerce MUST BE ACTIVE TO ACTIVATE THIS\nPLUGIN, on WordPress 6.5 and later. That is the plugin dependency header, added\nat the request of the wordpress.org review. Two things it is worth knowing,\nmeasured on 27 September 2026:<\/p>\n\n On WordPress 5.9 to 6.4 the header does nothing at all -- it is ignored in\nsilence, and does not even show on the Plugins screen. There, as before, the\nplugin activates without WooCommerce and simply does nothing: it tells you so on\nthe Plugins screen, and native WooCommerce search is untouched.<\/p>\n\n An active Heurix account, with a server API key (prefix This plugin is an interface to Heurix, a hosted search service\n(https:\/\/heurix.fr). Ranking, typo tolerance and trade synonyms are computed by\nthe service; the plugin handles indexing and the replacement of results.<\/p>\n\n No feature of the plugin is locked, time-limited, or held back for a paid\nversion.<\/strong> All the code shipped is active from activation onwards, with no\nlicence key and no subscription check, and the zip contains no dormant code\nwaiting to be unlocked. What you pay for is the service, not the plugin.<\/p>\n\n\n
\n
Compatibility: what has actually been run<\/h4>\n\n
\n
wordpress.version<\/code>) and the\narchive verified against its published sha1.\nThe lower bound is measured under PHP 8.1, and it is WordPress that sets it,\nnot this plugin: 5.8.17 and 5.6.21 do not start under PHP 8.1, because mysqli\nthrows by default there and their wp-db.php<\/code> does not set\n mysqli_report( MYSQLI_REPORT_OFF ). That line appears in WordPress 5.9,\nwith the WordPress comment that names PHP 8.1.\nNOT MEASURED: WordPress 5.8 and earlier under a PHP they accept (they go down\nto 5.6.20). That would need a PHP 7.x, ruled out on 23 September -- the\nHomebrew formula has been dead since 2022, it would mean a third-party tap and\none more php-fpm. That gap cannot open on a merchant's site: WordPress refuses\nto activate a plugin whose Requires PHP<\/code> is not satisfied, and ours asks for\n8.1.<\/li>\nloop_shop_per_page<\/code> has no effect, page 2 comes out empty), 6.1.0 holds. The\nlines \"WC requires at least: 7.0\" and \"WC tested up to: 9.0\" announced until\n22 September rested on nothing at all.\nNot measured: the intermediate versions of each branch (the runs cover 4.9.5,\n5.9.2, 6.0.0, 6.1.0, 6.2.0, 6.3.0, 6.5.0, 6.7.0, 6.9.5, 7.0.0, 7.9.2, 8.9.5,\n9.9.7, 10.9.4, 11.1.2), and WooCommerce 3.9.5, which stops on a PHP error\nbefore reaching the measurement.<\/li>\n<\/ul>\n\nRequires at least<\/code> or Requires PHP<\/code> is not satisfied --\nverified on 23 September 2026, both ways:<\/p>\n\n\"Current WordPress version (6.9.9) does not meet minimum requirements\n [...] The plugin requires WordPress 7.1.\"\n\"Current versions of WordPress (6.9.9) and PHP (8.1.34) do not meet\n minimum requirements [...] requires WordPress 7.1 and PHP 9.9.\"\n<\/code><\/pre>\n\nRequires PHP: 8.1<\/code> forbids\nit. What we have not measured therefore cannot happen on a merchant's site.<\/p>\n\n\n
Requirements<\/h4>\n\n
hx_<\/code>) and a catalog\ncreated. See heurix.fr\/docs<\/a> to get started.<\/p>\n\nThe external service, what it costs, and what it receives<\/h4>\n\n