Skip to content

v1.8.0

Choose a tag to compare

@millipress-bot millipress-bot released this 22 Aug 09:58
061e7d1

1.8.0 (2026-08-22)

1.8.0 brings a redesigned cache management experience centered on a command palette, new abilities for AI assistants, and several correctness fixes to the caching engine and rule system.

The admin bar's one-click flush button is replaced by a command palette that lets you clear or expire specific targets — pages, post types, taxonomies, or the full cache — with descriptive labels. A snackbar confirms the action and reports how many entries were actually removed. Add-ons can register their own palette commands and control their position in the list. The palette is wider to accommodate longer target names and no longer intrudes on every admin search field.

AI assistants can now check cache status and clear the cache. Two new abilities — available over REST and from MCP clients — answer the questions site owners most often ask through an assistant: "why is my page not cached" and "clear the cache for this post or URL". The status ability returns a curated health summary (connectivity, entry count, and the checks that need attention) without leaking the full plugin and theme inventory that the settings UI needs. MilliCache Pro extends this to every aspect of the plugin: caching, cache entries, rules, preloading, the edge cache, and the object cache can all be managed through abilities as well.

Cache responses now include the remaining lifetime of a served page. The engine has been corrected to never store redirect responses and to capture output from the outermost buffer, which prevents partial content from being cached when other plugins open buffers early. URL hashes now preserve non-default ports, so sites on non-standard ports get correct per-URL cache isolation. The invalidation queue runs even when the drop-in fails to load, so scheduled purges are not silently lost.

On the rules side, wp-cron.php is now excluded by a dedicated locked rule that cannot be overridden by site rules. Previously it was only covered by the generic dot-file rule, which a higher-priority site rule could outrank, potentially causing a stale cron lock response to be replayed and stalling scheduled events. The REST API exclusion now also matches the ?rest_route= query-string form used when pretty permalinks are off.

WP-CLI's clear flags are now scoped to the current site context on multisite. Redundant entries have been removed from the admin search results. Portuguese (Brazil), Italian, Spanish, and French translations are complete.

Features

  • abilities: let assistants read cache status and clear the cache (f80b057)
  • abilities: report network-wide problems in a site's cache status (4e2b9f1)
  • abilities: say whether the install is a multisite (4573485)
  • adminbar: replace one-click flush with command palette integration (382b10b)
  • adminbar: snackbar clear feedback and a wider palette (2c77206)
  • cache: state the lifetime a replayed page has left (8f699fd)
  • clear: report removed-entry counts instead of processed inputs (23ec58f)
  • cli: scope bare clear flags to the WP-CLI site context (d30d31e)
  • commands: let add-ons ride the palette's promote/demote cycle (1db3d3f)
  • commands: offer expire alongside clear with descriptive target labels (880c9eb)
  • engine: capture the page in the outermost output buffer (6c4d393)
  • engine: capture the page in the outermost output buffer (7606f04)
  • engine: capture the page in the outermost output buffer (6cee142)
  • engine: expose the request's effective TTL override (31e2555)
  • rules: build the rule registry when the drop-in has not (b6ef71b)

Bug Fixes

  • adminbar: keep the admin bar button size stable on page load (2c77206)
  • cache: report targets that belong to another site (6a7947a)
  • clear: anchor path-only URL targets onto the home URL (27bd7dc)
  • clear: skip non-viewable taxonomies in post-related flags (40cd884)
  • commands: drop the stray focus ring after palette clears (880c9eb)
  • commands: stop crowding every admin search, and drop the settings entry (87b52d1)
  • engine: execute the invalidation queue when the drop-in never loads (746bd0e)
  • engine: keep non-default ports in URL-based cache hashes (ed6f3d6)
  • engine: never store redirect responses (6c4d393)
  • engine: never store redirect responses (7606f04)
  • engine: never store redirect responses (6cee142)
  • rules: lock wp-cron.php out of the cache and cover the rest_route form (908ce04)
  • rules: skip an action whose placeholder resolved to nothing (a5e4894)
  • updates: keep update checks off every admin page load (1661d07)

Performance Results

Loading 6.9x faster with MilliCache!

Metric Without Cache With MilliCache Improvement
Server Response (TTFB) 53ms 8ms 85% faster
Page Load (LCP) 108ms 60ms 44% faster

Server Response is the primary metric for page caching. It measures how fast the server delivers the HTML. MilliCache focuses on serving cached pages instantly, eliminating database queries and PHP processing.

Page Load includes frontend rendering time, which depends on themes, scripts, and assets. Content optimization is outside MilliCache's current scope.

Technical Details

Cache Efficiency

  • Database queries: 27 → 29
  • Response time range: 7ms-70ms (cached) vs 52ms-66ms (uncached)

Cache Generation (First Request)

  • Total processing: 53.21ms
  • Before template: 25.78ms
  • Template rendering: 27.46ms

Test Configuration

  • Iterations: 50 (3 warm-up runs discarded)
  • Outliers removed: 3
  • Timestamp: 2026-08-22T09:57:17.032Z
  • Commit: 061e7d1

Regression Analysis

  • Status: PASS
  • Performance improved: 6.85x -> 6.86x (+0.3%)
  • Threshold: 10% slowdown triggers failure