Anti-Cache Kit vs Delete Expired Transients

Anti-Cache Kit is a development tool for WordPress developers and designers who need to bypass all caching and optimization mechanisms during development, testing, or troubleshooting. Development tool only. Do not leave active on production sites. Key features Cache and optimization management Automatically detects, flushes, and deactivates 20+ cache plugins Removes cache drop-ins (object-cache.php) so caches that keep working through a drop-in actually stop Deactivates optimization plugins that interfere with debugging (Perfmatters, FlyingPress, WP Asset CleanUp, and more) Never deactivates Query Monitor, the debugging tool you need while troubleshooting Clears object cache (Redis, Memcached) and OPcache Clears hosting-specific caches (SiteGround, Cloudflare, Kinsta, and Varnish on demand) Prevents browser caching for administrators Server-level cache prevention Injects .htaccess rules via the WordPress markers API, no backup file needed Disables SiteGround cache via environment variables Sets no-cache, no-store headers at server level for all visitors Disables ETags and mod_expires to prevent conditional caching Sends CDN/proxy bypass headers (X-Accel-Expires, Surrogate-Control) Detects nginx and Caddy and skips rules that would not apply there, offering an equivalent nginx snippet to copy instead Cleanly removes only its own rules on deactivation, leaving the rest of .htaccess untouched Debug mode activation Enables WP_DEBUG, WP_DEBUG_LOG, and SCRIPT_DEBUG (errors go to wp-content/debug.log) Sets WP_DEBUG_DISPLAY to false so errors are logged, not shown on screen Disables WordPress cache (WP_CACHE = false) Comments out conflicting definitions with visible markers instead of deleting them Wraps its own definitions in markers and reverts them on deactivation, preserving any WP_DEBUG, WP_CACHE or SCRIPT_DEBUG you had set yourself Modifies wp-config.php with the WordPress Filesystem API, validates the result before writing, and never keeps a copy of your credentials on disk Maintenance mode Optional status page for non-logged visitors Quick toggle from admin bar Customizable via filter hook Self-contained output with aggressive cache prevention headers (503, no-store, Surrogate-Control) Safety and environment Detects production sites with wp_get_environment_type() and shows a dismissible warning, plus a red dot in the admin bar Status panel reflects the real state: debug constants, server rules, detected environment, and whether wp-config.php is writable Removes its options and any leftover backup directory from older versions on uninstall Supported cache plugins WP Rocket W3 Total Cache WP Super Cache WP Fastest Cache LiteSpeed Cache SiteGround Optimizer WP Optimize Hummingbird (WPMU DEV) Breeze (Cloudways) Autoptimize Cache Enabler Surge Redis Object Cache Powered Cache Comet Cache Swift Performance Nginx Helper NitroPack SpinupWP Docket Cache Object Cache Pro Supported optimization plugins Perfmatters FlyingPress WP Asset CleanUp Object Cache 4 Everyone DietPress (WPO Tweaks) Clearfy Cache EWWW Image Optimizer ShortPixel Image Optimizer Supported hosting caches SiteGround (via .htaccess environment variables and plugin API) Cloudflare (both new and legacy namespaces) Kinsta Varnish (opt-in, best-effort PURGE/BAN when detected) Generic hosting cache systems Developer Information Hooks and Filters ayudawp_anticache_maintenance_data – Filter to customize maintenance page data (heading, status, message, retry) ayudawp_anticache_cache_plugins – Filter to modify the list of supported cache and optimization plugins ayudawp_anticache_purge_varnish – Filter to force the opt-in Varnish purge on or off (return true or false) Constants AYUDAWP_ANTICACHE_VERSION – Plugin version AYUDAWP_ANTICACHE_PLUGIN_DIR – Plugin directory path AYUDAWP_ANTICACHE_PLUGIN_URL – Plugin directory URL AYUDAWP_ANTICACHE_PLUGIN_BASENAME – Plugin basename for hooks Code examples Customize maintenance page: add_filter( 'ayudawp_anticache_maintenance_data', function( $data ) { $data['heading'] = 'My Site Name'; $data['status'] = 'Updating...'; $data['message'] = 'We are deploying a new version. Back in a few minutes.'; return $data; } ); Add a custom cache plugin: add_filter( 'ayudawp_anticache_cache_plugins', function( $plugins ) { $plugins['my-cache/my-cache.php'] = array( 'name' => 'My Cache Plugin', 'type' => 'cache', ); return $plugins; } ); Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

Delete old, expired transients from the WordPress options table (wp_options), to prevent them from bloating your database and even slowing down your website. Unless you are using an object cache (like memcached), WordPress stores transient records in the options table. Many transients are given an expiration time, so in theory they should disappear after some time. In practise, because old transients are only deleted when requested again after they’ve expired, many transients stay in the database. After a while, there can be thousands or even millions of expired transients needlessly taking up space in your options table, depending on what your plugins are doing. Delete Expired Transients schedules a daily task to delete any expired transients from the options table. It performs this operation with a single SQL query, and then runs a second query to find any orphaned expiration records and deletes them too. There are a few other plugins around that clean up expired transients. This one is written for fast performance, set-and-forget scheduled housekeeping, and maximum compatibility. It uses the PHP time to determine whether transients are expired, not the database time (which can be different). It does only one job, and it does it well with the minimum of resources. Now optimised for WordPress Multisite. Translations Many thanks to the generous efforts of our translators: English (en_CA) — the English (Canadian) translation team English (en_GB) — the English (British) translation team English (en_ZA) — the English (South African) translation team French (fr_FR) — the French translation team Hungarian (hu_HU) — the Hungarian translation team Norwegian: Bokmål (nb_NO) — neonnero Norwegian: Nynorsk (nn_NO) — neonnero Russian (ru_RU) — the Russian translation team Spanish (es_ES) — the Spanish translation team If you’d like to help out by translating this plugin, please sign up for an account and dig in. Contributions Translate into your preferred language Fork me on GitHub Privacy Delete Expired Transients does not collect any personally identifying information, and does not set any cookies. It removes some old information from the database, potentially reducing a website’s exposure to leakage of personally identifying information.