Purgify – Clear Cache, Transients & Database

Description

Purgify – Clear Cache, Transients & Database gives you one place to clear every cache on your site, clear WordPress transients, and purge leftover database rows (temporary settings, plugin caches, test data) without opening phpMyAdmin.

It has three tools:

• Cache clear detects the cache layers on your site (page cache plugins, object cache, hosting cache, optimized CSS/JS, your browser) and clears them all with one click, or one at a time.
• Transient purge clears all transients or only expired ones, then lists every key it deleted.
• Database purge finds rows in any of your site’s tables whose key contains your search terms, shows them like phpMyAdmin, and lets you delete them one at a time or all at once. It’s ideal for resetting a plugin’s temporary settings or caches while you test a feature again and again.

Features

• Admin Toolbar menu — clear all caches, clear transients or open the database purge from any admin screen or front-end (if logged in as admin) with one click.
• Tools page (Tools → Purgify) — tabs for Cache (the default), Transients and Database Rows, with built-in guidance.
• Cache clear (Tools → Purgify → Cache) — shows every cache layer detected on your site with one “Clear all caches” button and a Clear button per layer. Purgify calls each plugin’s own clear function, so nothing is deleted behind the plugin’s back. Supported:
  • Page cache plugins: WP Super Cache, W3 Total Cache, WP Rocket, LiteSpeed Cache, WP Fastest Cache, Cache Enabler, Breeze, WP-Optimize, Hummingbird, Comet Cache, Swift Performance, FlyingPress.
  • Hosting, CDN and server caches: Varnish (detected automatically from the response headers), SiteGround Speed Optimizer, WP Engine, Pantheon, Cloudflare, Proxy Cache Purge (Varnish), Nginx Helper, PHP OPcache.
  • Object cache: Redis, Memcached or any persistent object-cache drop-in.
  • Optimized files: Autoptimize, Elementor generated CSS.
  • Your own browser’s cache for the site (via the Clear-Site-Data header).
  • Developers can add more with the purgify_cache_providers filter.
• Transient purge (Tools → Purgify → Transients) — after clearing, an admin notice tells you exactly how many transients were deleted, with an expandable list of every key that was removed. Two clear modes:
  • Clear All — removes every transient regardless of expiry.
  • Clear Expired — removes only transients whose expiry time has passed (safe, routine cleanup).
• Database purge (Tools → Purgify → Database Rows) — pick a table (defaults to the options table), enter comma-separated key fragments, and see every matching row with all its columns. Delete rows one at a time or all shown rows at once.
  • Searches match anywhere in the key (LIKE %term%) and show at most 100 rows. Deletes are limited to the rows shown, so there is no way to empty a table.
  • Transient rows are left out of searches unless you tick “Include transients”, and the results say how many were hidden.
  • Only this site’s tables (with the WordPress table prefix) are listed.
  • Core options that WordPress needs (site URL, active plugins, theme, user roles and similar) are protected and cannot be deleted.
  • Object caches are cleared for deleted options and post, user, term and comment meta, so WordPress stops using the old values straight away.
  • Your last search is remembered, so a repeat test cycle is one click from the toolbar.
• Nonce-protected actions — all actions are protected against CSRF, and every delete asks for confirmation.
• Translations ready — ships with translations for Spanish, French, German, Portuguese (Brazil), and Italian.
• Lightweight — no external dependencies, no database tables, no settings. The only saved data is each user’s last Database Rows search and a few short-lived transients, all removed on uninstall.

When should I clear transients?

• After updating plugins or themes whose caches are stale.
• When debugging unexpected cached content.
• As routine maintenance to keep the options table clean (use Clear Expired).
• After migrating or restoring a database.

When should I clear caches?

• After changing a theme, plugin settings or CSS, when visitors still see the old version.
• After deploying code changes (also clears PHP OPcache).
• When an optimization plugin serves stale combined CSS or JavaScript.

When should I purge database rows?

• To reset a plugin’s saved settings, onboarding flags or caches so you can test its first-run behaviour again.
• To remove leftover options or meta from plugins you have already deleted.
• To clear a stuck flag or lock that a plugin stored in the options table.

Privacy

This plugin does not collect, store, or transmit any personal data, and it does not contact any third-party service.

To detect and clear a Varnish cache, Purgify sends HTTP requests only to your own site: one request to your homepage (repeated at most every 12 hours) to read its cache headers, and a PURGE request when you clear the cache. When you clear caches, the cache plugins you have installed (for example Cloudflare) may contact their own services, exactly as they do when you use their own clear buttons.