| 开发者 | motylanogha |
|---|---|
| 更新时间 | 2026年11月21日 01:17 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[sieve] shortcode[sieve] shortcode or the "Sieve Filter" block.Yes. Sieve filters WooCommerce product archives and any page where you place the filter.
No. Filtering happens via AJAX with the URL kept in sync so results are shareable.
Sieve can filter WooCommerce products by categories, tags, attributes, price, stock status, on-sale state and a keyword search field. It also supports range sliders, searchable options, color/image swatches, active-filter chips and sorting.
Yes. Sieve builds a product filter index, so AJAX filter requests do not need to run slow live joins for every category, attribute and price query.
Use the [sieve] shortcode or the "Sieve Filter" block. Both render the facets, the results grid, sorting, active-filter chips and pagination together.
Use the [sieve_search] shortcode or the "Sieve Search" block. As shoppers type, a dropdown shows matching products with thumbnails and prices; it is fully keyboard accessible and falls back to the standard product search when JavaScript is unavailable.
Yes. The filter UI is built for keyboard use and screen readers, with labelled regions, accessible controls, polite result-count announcements and reduced-motion support.
Yes. Sieve includes a mobile filter drawer with a sticky apply bar, so shoppers can filter products without fighting a long sidebar on small screens.
Yes. This plugin is compatible with WordPress Multisite. Network activate it or activate it on individual sites; each site keeps its own settings and data.
meta:{key}), shown as a range slider or as checkboxes. Sieve itself indexes no meta: an add-on supplies the values through the new sieve_index_rows filter, can label them (sieve_meta_value_label) and can ask for a full index rebuild with do_action( 'sieve_request_reindex' ).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.[sieve_search] box, the Sieve Search block or the Elementor widget produced no dropdown, no thumbnails and no prices; it only worked as a plain search form on Enter. The script ships again, and the build now fails if any enqueued file is missing from the package.