WP Debugging vs Anti-Cache Kit

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.

This plugin sets the following debug constants in wp-config.php on plugin activation and removes them on plugin deactivation. Any errors will result in a PHP Exception being thrown. Debug constants per Debugging in WordPress. Default settings: define( 'WP_DEBUG_LOG', true ); define( 'SCRIPT_DEBUG', true ); define( 'SAVEQUERIES', true ); @ini_set( ‘display_errors’, 1 ); is set when the plugin is active. WP_DEBUG is set to true when the plugin is first run, thereafter it can be turned off in the Settings. The Settings page allows the user to set the following. define( 'WP_DEBUG', true ); // Default on initial plugin installation. define( 'WP_DEBUG_DISPLAY', false ); // Default when not declared is true. define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); // WordPress 5.2 WSOD Override. When the plugin is deactivated best efforts are made to re-add pre-existing constants to their former state. When the plugin is activated the default settings and any saved settings are restored. This plugin uses the wp-cli/wp-config-transformer command for writing constants to wp-config.php. Debug Quick Look from Andrew Norcross is included with this plugin to assist in reading the debug.log file. If you already have this plugin installed you should delete it when WP Debugging is not active. Query Monitor and Debug Bar plugins are optional dependencies to aid in debugging and troubleshooting. The notice for installation will recur 45 days after being dismissed. If you have a non-standard location for your wp-config.php file you can use the filter wp_debugging_config_path to return the file path for your installation. The filter wp_debugging_add_constants allows the user to add constants to wp-config.php. The filter returns an array where the key is the name of the constant and the value is an array of data containing the value as a string and a boolean to indicate whether or not the value should be passed without quotes. $my_constants = [ 'my_test_constant' => [ 'value' => 'abc123', 'raw' => false, ], 'another_test_constant' => [ 'value' => 'true' ], ]; The value option contains the constant’s value as a string. The raw option means that instead of placing the value inside the config as a string it will become unquoted. The default is true. Set as false for non-boolean values. Example: add_filter( 'wp_debugging_add_constants', function( $added_constants ) { $my_constants = [ 'my_test_constant' => [ 'value' => '124xyz', 'raw' => false, ], 'another_test_constant' => [ 'value' => 'true' ], ]; return array_merge( $added_constants, $my_constants ); }, 10, 1 ); This will create the following constants. define( 'MY_TEST_CONSTANT', '124xyz' ); define( 'ANOTHER_TEST_CONSTANT', true ); Development PRs are welcome against the develop branch on GitHub.