KISS Flush

Every cache layer, cleared in one step.

A WordPress site often sits behind four caches: the page builder, a caching plugin, the host and a CDN. KISS Flush clears all of them from one button in the admin bar, or one command in a deploy script.

Version
1.7.6
WordPress
6.0+
Tested up to
WordPress 7.1.4
PHP
7.4+
Releases
29
License
GPL 2.0 or later

What it solves

After an edit, the usual routine is to open three dashboards and clear each cache in turn before the change shows. Miss one and a visitor sees yesterday's page.

KISS Flush finds the caches on the site by itself, then clears them together. By default it clears only the page you are editing, plus the pages that list it, so the rest of the cache stays warm.

What it does

What it needs

See it running

KISS Flush runs on the WordPress sites we host and manage, and updates itself from our own update server.

Install

  1. Step 1

    Upload the kiss-flush folder to /wp-content/plugins/

  2. Step 2

    Activate the plugin through the Plugins menu

  3. Step 3

    Follow the onboarding wizard to detect and configure your cache providers

  4. Step 4

    Start flushing with a single click from the admin bar or floating button

New versions install the same way: upload the new ZIP over the old one. Settings are kept.

Changelog

29 releases so far. The newest:

  1. 1.7.6

    • Changed marked compatible with WordPress 7.1.4, so the update screen no longer says "Not tested".
    • Changed the icon on the update screen has rounded corners and, every few seconds, flips over to Imaginary Trout's power button.
    • Changed the banner in the plugin details leaves room for the plugin name WordPress writes over its lower left corner.
  2. 1.7.5

    • Changed new plugin icon, in the admin menu, on the settings page and in WordPress's update screen, with a matching banner in the plugin details.
    • Changed releases are now published to Imaginary Trout's new update server as well as the old one. Installed copies keep checking the same address, so nothing changes on your site.
  3. 1.7.4

    • Fixed do_action( 'kiss_flush_purge_all' ) now works regardless of the auto-flush settings.
    • Added kiss_flush_allow_purge_all_action filter — return false to ignore that action on a given site.
    • Note supersedes the 1.7.3 build. 1.7.3 changed code after its zip was uploaded, so it is retired rather than rebuilt, keeping one version number to one build.
  4. 1.7.3

    • Fixed wp kiss-flush all printed nine "invalid synopsis part" warnings before every run.
    • Added wp kiss-flush version reports the installed version without leaving the console. wp kiss-flush --version works too.
    • Note includes everything in 1.7.2, which was never released.
  5. 1.7.2

    • Added a public purge hook for other plugins: do_action( 'kiss_flush_purge_all' ) runs the same full-site flush as the update triggers, with the same capability check and debounce.
    • Added KISS Flickr Gallery integration. When "auto-flush on update" is on, saving KISS Flickr's settings (kiss_flickr_settings_saved) purges the site, since most of those settings change the gallery's markup and page caches would otherwise keep serving the old layout to visitors.
  6. 1.7.1

    • Added --provider on the WP-CLI flush commands now accepts several providers at once, comma-separated: wp kiss-flush all --provider=cloudflare,kinsta,avada.
    • Changed Naming a provider that is not detected on the site now warns and says which ones were skipped. Previously they were dropped silently, so a targeted flush could report success having done nothing.

KISS Flush questions

No. It works alongside the caches you already have and tells each one to clear. Keep your caching plugin, your host's cache and your CDN; KISS Flush gives them one off switch.

No. KISS Flush uses a local-first architecture — providers like Kinsta (via MU plugin), WP Engine, SiteGround, Pantheon, Elementor, WordPress native cache, LiteSpeed, Redis, Varnish, Breeze, Nginx Helper, and Wordfence are auto-configured and require zero credentials. Only Cloudflare (without the official CF plugin), Sucuri, and Fastly need API tokens.

KISS Flush encrypts all credentials with AES-256-CBC before storing them in the database. The encryption key is derived from your WordPress salts (AUTH_KEY and SECURE_AUTH_KEY), so credentials are never stored in plain text.

Yes. KISS Flush provides a full WP-CLI command suite. Add wp kiss-flush all to your deployment pipeline to flush all caches after deploys.

KISS Flush continues flushing the remaining providers and reports which succeeded and which failed in the toast notification and activity log.

Not usually. KISS Flush detects the Kinsta MU plugin (installed by default on all Kinsta sites) and uses its local HTTP endpoints for both full-site and per-URL cache purging. An API key is only needed as a fallback if the MU plugin endpoint is unavailable.

Other KISS plugins

Want KISS Flush on your site?

It is not on WordPress.org yet. It runs on the sites we build and manage. Tell us about yours, or about a plugin you need built.

Start a project