Command Palette
WordPress 7.0 ships a command palette, and MilliCache puts its verbs in it. Press ⌘K (Ctrl+K on Windows) anywhere in the admin, or click Cache in the admin bar.
The two entry points differ:
- The admin bar button opens the palette with the MilliCache commands already listed, so you can pick one without typing.
- ⌘K opens the palette empty, the way WordPress intends. MilliCache's commands are there, you just search for them.
What you can run#Copied!
| Command | What it does |
|---|---|
| Clear website cache | Empties the whole page cache for this site |
| Expire website cache | Marks every page stale instead of deleting it, so visitors keep getting an instant response while pages regenerate |
| Preload full cache | Queues every URL from your sitemaps for background preloading |
| Purge … edge cache | Empties the whole zone at your CDN. The label names your provider, e.g. Purge Cloudflare edge cache |
| Flush object cache | Empties the object cache |
| Entries | Opens the Entry Browser |
| Rules | Opens the Rules Builder |
When to purge the edge cache by hand#Copied!
You usually don't have to. Clearing or expiring anything already purges its copy at the CDN: MilliCache tags every edge response, and a site clear purges that site's tags along with the local cache.
Reach for Purge … edge cache when tagging can't do the job:
- bunny.net's zone-level Vary Cache disables tag and URL purges, so emptying the whole zone is the only option
- you changed the edge configuration and want a clean slate
- something is still stale at the CDN after a normal clear
It empties everything the zone holds, so the next visit to every page goes to your server again.
Commands only appear when their module is switched on and your license is active. On a multisite, Purge edge cache and Flush object cache live in the Network Admin, alongside the network-wide clear and expire.
Clearing a single page#Copied!
Type what you want to clear instead of picking a command, and MilliCache offers to clear or expire exactly that:
| You type | What gets cleared |
|---|---|
/blog/ |
That page |
https://example.com/blog/ |
The same, written out |
123 |
The post with that ID |
post:123 |
The same, as a cache flag |
flag:home |
The home flag |
home* |
Every flag starting with home |
Separate several targets with commas: /blog/, /shop/, post:12.
Bare words are treated as a search, not as a cache flag — otherwise every search anywhere in the admin would offer to clear it. To clear a flag whose name is a plain word, either write flag: in front of it or open the palette from the admin bar button, where a bare flag is unambiguous.
In the Network Admin every target is a flag pattern instead, so 5:* clears site 5 and *:posts clears the posts flag on every site.
Related#Copied!
- WP-CLI Commands — the same operations for scripts and deploys
- Cache Entries — the browser behind the Entries command
- Cache Preloading — what Preload full cache queues
- AI Access: the same operations for a REST client or an assistant
Last updated:
Release updates
Get notified when new versions and guides ship. No spam.
By subscribing you agree to our Privacy Policy. Double opt-in, no spam, unsubscribe anytime.