Sieve – Faceted Filter for WooCommerce

1.1.13

• Fixed: ticking a parent category (Clothing above Shirts) in the category tree returned no products, and the parent showed no count. A product is now indexed under every ancestor of its categories, the way a WooCommerce category archive counts it, so a parent’s count includes its subcategories. The index rebuilds itself once after the update.
• Fixed: facet counts and the price range bounds included products the grid does not show: products hidden from the catalogue, and out-of-stock products when “Hide out of stock items” is on. A count now matches the number of products the shopper gets when ticking it.
• Fixed: on phones the filter drawer closed after every change, so only one filter could be picked per opening and the “Show results” bar was never reached. The drawer now stays open until “Show results” or a tap on the backdrop.
• Uninstall now also removes the swatch colours and images stored on attribute terms.
• The package no longer carries the ESLint configuration file.

1.1.12

• The package no longer carries the compare engine, which Sieve never loads.

1.1.11

• Hardening: filter parameters read from the page URL by the shortcode and the block are now sanitised at the moment they are read, not only later in the URL parser.
• Fixed: an image swatch URL containing percent-encoded characters (for example %20 for a space) lost them on save, because the value went through a text sanitiser before the URL sanitiser. The URL is now sanitised with esc_url_raw() only.
• The package no longer carries seven shared storefront engines Sieve never loads (wishlist, quick view, add-ons, bundles, checkout, gift cards, media).

1.1.10

• Changed: a code comment claimed WooCommerce verifies a nonce on the add-to-cart form. That form carries no nonce, so the comment now says so. Comment correction only, no change in behaviour.

1.1.9

• Fixed: the first index build ran inside an admin page load. On a large catalogue that single request had to read every product, so the admin was slow while the index was being built and, past a few thousand products, the request could time out and start over from scratch on a later page load. The build now runs on a background cron tick in batches of 200 products, records the highest product ID it reached and carries on from there, and reads the list of products to index with one direct query per batch instead of get_posts(), so another plugin’s pre_get_posts filter can no longer add to, reorder or trim the set Sieve indexes. The saved position carries the version that wrote it and is ignored when it does not match, so a build interrupted by a plugin update starts over instead of finishing with half the catalogue indexed by the previous version. A tick that finds the indexing lock held books a retry rather than dropping the build. On a site with wp-cron switched off (DISABLE_WP_CRON), where a scheduled event may never run at all, admin pages index one batch inline instead: one batch per page load, not the whole catalogue in one request. Developers can change the batch size with the sieve_index_batch_size filter.
• Fixed: rebuilding the index emptied it first, so filters and predictive search answered from an empty or half-filled table until the rebuild finished. The rebuild now replaces each product’s rows in place and only at the end drops what is left over from products that no longer exist, so the previous index stays readable while the new one is written over it.
• Changed: the manual “Rebuild index” button on the settings screen walks the catalogue in those same batches and drops the per-request object cache between them, so the products it has already indexed are not all held in memory at once. On a site running a persistent object cache drop-in that cache is left in place, because clearing it is not this plugin’s to do.
• Note: 1.1.6, 1.1.7 and 1.1.8 were development versions and were never published on WordPress.org. Upgrading from 1.1.5 brings all of the above at once.

1.1.5

• Fixed: the PRO upgrade promo kept selling to people who had already bought the paid edition. Only the banner could be dismissed, so the sidebar promo and the locked feature cards followed a paying customer around for good. The promo now checks whether the paid edition is active and steps aside when it is.
• Fixed: arrow glyphs in the admin menu paths, and in the strings handed to translators. An arrow inside a translatable string makes the glyph every translator’s problem and changes the layout in any locale that drops it.