A block for block themes, a widget for sidebars, and an Elementor widget with its own\nStyle tab<\/li>\n<\/ul>\n\nPlaced above the products automatically, or with the widget or the\n [codebold_filters] shortcode.<\/p>\n\n
The plugin, and the rest of the CodeBold Commerce suite, are at\nhttps:\/\/codeboldcommerce.com\/smart-filters\/ \u2014 that is where the documentation lives and\nwhere support is answered.<\/p>\n\n
A CodeBold IT Solutions product. https:\/\/codeboldtech.com<\/p>\n\n
External services<\/h3>\n\n
This plugin makes no request to any server, ever \u2014 not ours, not anyone else's. There is\nno licence check, no registration, no usage tracking and no telemetry. Nothing leaves your\nsite when a shopper filters your shop, and nothing leaves it when you open the settings\nscreen either. The settings screen is set in your system font.<\/p>\n\n\n
\n- Install and activate.<\/li>\n
- That is all \u2014 filters appear on your shop and category pages.<\/li>\n
- WooCommerce, then Smart Filters, to choose what shoppers narrow by, what order the\ngroups are in and where the panel goes. The panel is drawn beside the settings as you\nchange them.<\/li>\n<\/ol>\n\n\n
\nDoes it work with my theme?<\/h3><\/dt>\nIt narrows the theme's own product list rather than drawing its own, so the products\nkeep looking exactly as your theme draws them.<\/p><\/dd>\n
Does it need JavaScript?<\/h3><\/dt>\nNo. Every control is an ordinary link. The script is an enhancement that swaps the\nresults in place instead of reloading.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.8.6<\/h4>\n\n\n- The settings screen no longer fetches its typefaces from Google Fonts. It draws in your\nsystem font instead, so opening it makes no request to any server, ever \u2014 the same\npromise the plugin already made about the shop and the shopper<\/li>\n<\/ul>\n\n
0.8.5<\/h4>\n\n\n- The first version offered publicly. Nothing here changes what the filters do or how\nthey look \u2014 it is the pass a plugin gets before strangers read it<\/li>\n
- Reading the address now removes WordPress own slashes before matching a term. No shop\nwill see a difference, because the characters WordPress escapes do not survive into a\nterm slug in the first place; it is correct rather than lucky, which is the standard\nthe directory holds a plugin to<\/li>\n
- The uninstall routine no longer writes to $blog_id while it runs. On a network it\nvisits every site in turn, and the loop was assigning to WordPress own global \u2014 the\nsame one switch_to_blog() and restore_current_blog() manage between those lines<\/li>\n
- Term ids reach the counting queries as placeholders rather than written into the\nstatement already cast. The query is identical; the difference is that a reader can see\nit is prepared without first tracing where the ids came from<\/li>\n
- Translations are left to WordPress, which has loaded them for plugins in the directory\nsince 4.6, and does it at the first string rather than on every page. The plugin was\nloading a second copy eagerly<\/li>\n
- The settings screen now says who made it and where the documentation is<\/li>\n
- The plugin header pointed at a domain that no longer resolves<\/li>\n
- Every external request the plugin makes is now written down in the readme. There is one:\nthree typefaces on the settings screen, and a filter that turns it off<\/li>\n
- Each hand-written query now carries, in the source beside it, why it is written that\nway \u2014 which values are placeholders, which are table aliases that cannot be, and where\nthe caching happens. Static analysis reads one function at a time and could not tell;\na person reading the code should not have to work it out either<\/li>\n<\/ul>\n\n
0.8.3<\/h4>\n\n\n- A sweep for the rest of the same bug, rather than waiting to be shown each one. What is\nwritten on top of the accent colour is now a setting of its own: white is right on the\ndefault blue and unreadable on a bright green, so a chosen size chip, the price Go\nbutton and the count on the filter button all follow one property instead of five\nhardcoded whites<\/li>\n
- The dark panel style tells the browser it is dark, so the price range's arrows, the\nsearch box's clear button and any scrollbar inside it are drawn to match<\/li>\n
- On the settings screen: placeholder text, text selection, the dismiss cross on our own\nnotice, a read-only licence field, and the focus ring WordPress draws in its own blue<\/li>\n
- Autofill no longer turns a field white. Chrome paints a saved value with its own\nnear-white background and there is no property that overrides it \u2014 it has to be drawn\nover, which it now is<\/li>\n<\/ul>\n\n
0.8.2<\/h4>\n\n\n- The dropdowns on the settings screen were unreadable: a select was given a dark\nbackground, and the browser kept drawing its options in the default dark ink on top of\nit. Everything the browser paints for itself \u2014 select menus, number field arrows,\nscrollbars \u2014 is now told the surface is dark<\/li>\n<\/ul>\n\n
0.8.1<\/h4>\n\n\n- An extension point after the settings form closes, so an add-on can carry a form of\nits own \u2014 a licence key field, for one. A form inside a form is not a thing HTML has<\/li>\n<\/ul>\n\n
0.8.0<\/h4>\n\n\n- Filters of your own. An add-on \u2014 or a shop with a developer \u2014 can register a filter on\nanything, and the panel draws it, counts it, clears it and narrows the shop with it\nexactly as it does its own. See the FilterType class<\/li>\n
- Counts take registered filters into account, in both directions: they are counted like\nevery other group, and every other group is counted against them<\/li>\n
- Larger type and stronger contrast on the settings screen. Nothing smaller than 12.5px,\nbody text at 15.5px, and labels off the faintest ink \u2014 it is read by shopkeepers, some\nof them for an hour at a time, and it was too small<\/li>\n
- Other plugins' admin notices are left alone. WordPress moves every notice on the page\ninside this screen's wrapper, and the dark styling was repainting them in our colours \u2014\na warning from another plugin arrived wearing our green<\/li>\n<\/ul>\n\n
0.7.0<\/h4>\n\n\n- The settings screen is now a dark console in CodeBold Commerce's own colours and\ntypefaces, sitting inside the WordPress admin it belongs to<\/li>\n
- A Panel style setting for the shop front: \"Match my theme\", which is the default and\nwhat it has always done, or \"CodeBold dark\". Colours only \u2014 the panel keeps your\nshop's typeface either way, because a plugin's fonts are not a cost a shopper should\npay for on a product page<\/li>\n<\/ul>\n\n
0.6.1<\/h4>\n\n\n- A Pro tab on the settings screen, listing what a paid version would add. One tab,\nreached by choosing it: no dashboard banner, no dismissible notice on somebody else's\nscreen, and nothing greyed out in the middle of a setting that works<\/li>\n<\/ul>\n\n
0.6.0<\/h4>\n\n\n- Filter by category, brand and tag. Every shop already has these and the panel could\noffer none of them, so a shop selling four brands had to make Brand an attribute as\nwell and keep the two in step by hand<\/li>\n
- A parent category is counted across everything filed beneath it. Clicking one returns\nthe whole branch, so counting only what is filed directly against it promised one\nnumber and delivered another \u2014 usually zero, on a shop that files at the leaves<\/li>\n
- The counts are worked out for the whole panel in one query instead of one per group,\neach of which used to pull every matching product id through PHP. Four queries became\none; eight became three<\/li>\n
- Counts now take In stock and On sale into account. They did not, so with \"In stock\nonly\" ticked the number beside an option said eleven where the shopper was about to be\nshown four<\/li>\n
- A new settings screen: three tabs, groups you can drag into order, a name of your own\nfor any of them, a plain-language account of where the filters will appear, and the\npanel drawn beside the settings as you change them<\/li>\n
- A search box on any group with more than a dozen options<\/li>\n
- A Product Filters block for block themes<\/li>\n
- The Elementor widget now offers categories and brands as well as attributes, a sort\ntoggle, its own \"show more\" threshold, and typography and colour in the Style tab<\/li>\n
- Sort can be turned off where a theme already has its own<\/li>\n<\/ul>\n\n
0.5.4<\/h4>\n\n\n- Group headings are styled by their class rather than by the element carrying it. A\ngroup that cannot collapse renders a heading instead of a button, and only the button\nwas styled \u2014 so on any theme that sizes its headings, that one group appeared several\ntimes larger than its neighbours<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"Let shoppers narrow your shop by size, colour, price and availability, in any theme, with or without JavaScript.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/366550","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=366550"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/codeboldtech"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=366550"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=366550"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=366550"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=366550"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=366550"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=366550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}