Anti-Cache Kit vs SQLite Object Cache

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.

A persistent object cache helps your site perform well. This one uses the widely available SQLite3 extension, and optionally the igbinary and APCu extensions to php. Many hosting services offer those extensions, and they are easy to install on a server you control. What is this about? It’s about making your site’s web server perform better. An object cache does that by reducing the workload on your MariaDB or MySQL database. This is not a page cache; these persistent objects go into a different kind of cache. These objects aren’t chunks of web pages ready for people to view in their browsers, they are data objects for use by the WordPress software. Caches are ubiquitous in computing, and WordPress has its own caching subsystem. Caches contain short-term copies of the results of expensive database lookups or computations, and allow software to use the copy rather than repeating the expensive operation. This plugin (like other object-caching plugins) extends WordPress’s caching subsystem to save those short-term copies from page view to page view. WordPress’s cache happens to be a memoization cache. Without a persistent object cache, every WordPress page view must use your MariaDB or MySQL database server to retrieve everything about your site. When a user requests a page, WordPress starts from scratch and loads everything it needs from your database server. Only then can it deliver content to your user. With a persistent object cache, WordPress immediately loads much of the information it needs. This lightens the load on your database server and delivers content to your users faster. Who should use this? If your site runs on a single web server machine, and that server provides the SQLite3 and igbinary extensions to php, this plugin will almost certainly make your site work faster. And if that server provides the APCu extension, this plugin uses it too. Some hosting providers offer redis cache servers. If your provider offers redis, it may be a good choice. You can use it via the Redis Object Cache plugin. Sites using redis have one SQL database and another non-SQL storage server: redis. Other hosting providers offer memcached, which has the Memcached Object Cache plugin. And some large multipurpose cache plugins, such as the LiteSpeed Cache, also offer object caching based on one of those cache server software packages. The cache-server approach to object caching comes into its own when you have multiple load-balanced web server machines handling your site. SQLite doesn’t work correctly in a multiple-web-server environment. But, for single-server site configurations, SQLite, possibly assisted by APCu, performs well. And the vast majority of sites are single-server. APCu APCu is an in-memory storage medium. It lets php programs, like WordPress, store data in shared memory so it’s very fast to retrieve when needed. If APCu is available on your host server, you can configure this plugin to use it. It reduces the typical cache lookup time to one-fifth or less of the SQLite lookup time, which is itself a few tens of microseconds. Performance counts, especially on busy web sites. Please look at Installation to learn how to configure this plugin to use APCu. The plugin works fast without it, and faster with it. WP-CLI: Even if APCu is in use, caching with SQLite is necessary when your web site uses WP-CLI, because WP-CLI programs do not have access to the APCu cache. This plugin writes all cached data both to APCu and to SQLite and makes sure the two are synchronized. WP-CLI You can control this plugin via WP-CLI once you activate it. Please type this command into your shell for details. wp help sqlite-object-cache Credits Thanks to Till Krüss. His Redis Object Cache plugin serves as a model for this one. And thanks to Ari Stathopoulos and Jonny Harris for reviewing this. Props to Matt Jones for finding and fixing a bug that appeared on a heavily loaded system. Thanks to Massimo Villa for testing help, and to nickchomey for a comprehensive code review. All defects are, of course, entirely the author’s responsibility. And thanks to Jetbrains for the use of their software development tools, especially PhpStorm. It’s hard to imagine how a plugin like this one could be developed without PhpStorm’s tools for exploring epic code bases like WordPress’s. How can I learn more about making my WordPress site more efficient? We offer several plugins to help with your site’s database efficiency. You can read about them here.