2.2.0

Front listings

• Classic themes (Twenty Twenty-One checked): a listing carries alignwide, so the theme widens it past its reading column; the current page's number was invisible without a primary preset (the accent fell back on currentColor, read where it is used: now a registered color); Show more was centered.
• Checkboxes of a list are drawn by the kit (a framed box, the accent when ticked, a tick; forced-colors and reduced motion honoured) over the native input, which stays the control. Chips keep theirs. Checked on Twenty Twenty-Five (light, the Midnight variation) and Twenty Twenty-One.
• Date fields of a range stack when the column is narrow; the filters sheet is sized in %, not vw (a classic scrollbar made it overflow by its width).
• The current page's number was unreadable on themes that color links with some specificity (Twenty Twenty-Five): it was written in the color of its background.
• UI kit: the default look as documented tokens (the theme's presets, a site's --meiliscout-color-*, the admin's palette) resolved on the listing's elements, so a dark section of a theme gets a dark listing; chips ('display' => 'chips'), a panel (<dialog>) for the filters, buttons that take the theme's button style; a facet with no value to show is hidden; a specimen of every component at /?meiliscout-ui-kit (administrators, WP_DEBUG). Checked on Twenty Twenty-Five (light, a dark section), Twenty Twenty-One and at 375 px.
• Upgrading: the colors found in the theme's palette, or chosen in Settings › Listings, are no longer --meiliscout-color-* on :root but --meiliscout-palette-* on the listing's elements; a theme reading those variables outside a listing sets its own.
• A yes/no facet showed its title twice. Themes styling every button strongly (Twenty Twenty-One) turned Show more and the active filters into dark blocks.
• The search field lost the listing's search (?q=…): it was bound to a value the store did not have, with or without JavaScript.
• Year facets: 'source' => 'date' (published) or 'date:modified' lists the years of the posts' date with their counts, newest first, combined with or; ?<key>=2025,2024 in the URL; also in the Facet block (Year of publication). Written by the date_query builder, like WP_Query's year.
• Date range facet: 'source' => 'date', 'type' => 'range' (also A range of dates in the Facet block): two date fields within what the posts have, ?period=2025-03-01..2025-06-30, the last day included whole, chips in the site's date format. Written by the date_query builder; shared PHP/JS cases (tests/fixtures/listings/date-cases.json). The client's plan template is version 4: a page cached with the previous one reloads its listing as the server rendered it.
• Toolbar above the results: the total, the sort, the active-filter chips and the reset link sit over the results, in their column (.meiliscout-listing__main), not at the foot of the filters; Apply moved to the filters' panel. Upgrading: a stylesheet reading .meiliscout-listing__filters .meiliscout-listing__toolbar no longer matches.
• Filters panel on small screens: below 782 px a listing's search and facets go behind a Filters (n) button and open as a sheet, with See N results at its foot (the live count of apply: button, or closing the sheet when instant). Wider, nothing changes; without JavaScript the filters stay on the page. Listings placed part by part and the editor's blocks keep their filters in the page.
• UI kit, finishing touches: fields sized in rem (they followed a large theme font), a sort as wide as its longest choice, a magnifier in the search field, lighter active-filter chips on one line with the reset link, framed cards, the block's core pagination dressed like the kit's. A listing takes the theme's wide size instead of the reading column (--meiliscout-max-width to change it). The block's template groups the total and the sort on one line; listings already placed keep their blocks.