Clear Cache for Me vs Varnish/Nginx Proxy Caching

W3 Total Cache and WP Super Cache are great caching plugins, but they do not know when a widget is updated. WPEngine is the best place to host your WordPress installation, but their caching system is no smarter when it comes to updating widgets and menus. I created this plugin because my website did not see any changes when saving widgets or menus using these caching systems. Clear Cache For Me will purge ALL your cache each time you do a save without having to press an additional button. It may be overkill, which may be why it’s not built in, but some people need simplicity. In addition to clearing those pesky caching engines, Clear Cache for Me can force your browser to reload your current theme’s CSS and JS files. I modify my theme’s CSS and JS files every so often and always have trouble with the browser not getting the latest version. So now after clicking on the “Clear Cache Now!” button on the dashboard the browser will be forced to reload the current theme’s CSS and JS files. If you do not click the “Clear Cache Now!” button, the browser will cache the CSS and JS files like it normally does. The popular Qode themes has a options to set your own custom CSS and JS. Sometimes you may not see your changes for a long while because your browser is trying to get the cached file. Whenever you save your Qode’s options, the CSS and JS files will be forced to reload in the browser on the public side. Works with the following caching plugins: Autoptimize Breeze Cache Cache Enabler Cloudflare GoDaddy Cache Kinsta Cache LiteSpeed Cache Elementor (CSS cache) Premium Addons for Elementor SiteGround SuperCacher Super Page Cache WP Fastest Cache WP Optimize Cache WP Rocket WP Super Cache W3 Total Cache WPEngine Cache Clears all cache for following actions (requires a caching system above to be active): When Widgets are saved. When Customizer is saved. When Menus are saved. When a fields in Advanced Custom Fields are saved. When a Contact Form 7 form is saved. When a Formidable Form form is saved. When WooThemes settings are saved. When NextGen Gallery albums and galleries are updated (beta – may not clear cache on all actions). When Qode options are saved this plugin forces browsers to reload the custom css and custom js. When a WP Forms forms or settings are saved. When WooCommerce settings are saved. (Cache should already be clearing when products are saved.) When settings from the Insert Headers and Footers plugin by WPBeginner are saved. When Settings from a settings page is saved. This includes settings from WordPress core, Yoast SEO, and most other plugins using the Settings API. When WordPress is updated. When plugins are updated, activated, and deactivated. When WordPress, plugins, and themes are automaticallly updated. See the plugin’s homepage for more details. Note: Since some caching systems run in the shutdown hook, this plugin also runs in that hook. This means if PHP does not have enough time, some code including any hooks within the ccfm_clear_cache_for_all() function are not guaranteed to run. If you need code to run, consider using the ccfm_clear_cache_for_me_setup hook. Some plugins may have “auto purge” (like Cloudflare), but it doesn’t cover all the items this plugin covers. Developer Options ccfm_supported_caching_exists Use this filter to determine if this plugin should do anything including showing the button on the dashboard. Return true if a caching system is supported. Default: True if any of the supported caching systems is active. See Example 1 below. ccfm_admin_init or ccfm_init_actions Use this action to add hooks when cache is to be cleared. Or do any other setup activity. ccfm_clear_cache_for_me_before Use this action to clear cache from an unsupported caching system before the default caching systems clear their cache. ccfm_clear_cache_for_me Use this action to clear cache from an unsupported caching system after the default caching systems clear their cache. Example If you were using an unsupported caching system you’ll need to identify the caching plugin’s class or function which clears the cache. As an example, if the unsupported caching system called the MyOtherCache::clear_all() function, you would use the following code to get this plugin to clear the cache. <?php function my_other_cache_enable( $return = false ) { if ( class_exists( 'MyOtherCache' ) ) return true; return $return; } add_filter('ccfm_supported_caching_exists', 'my_other_cache_enable'); function my_other_cache_clear() { if ( my_other_cache_enable() ) MyOtherCache::clear_all(); } add_action('ccfm_clear_cache_for_me', 'my_other_cache_clear');

Complete WordPress Varnish Cache 3.x/4.x/5.x and Nginx Proxy Cache integration. This plugin handles all integration with Varnish Cache and Nginx Proxy Cache. It was designed for high traffic websites. Main features admin interface, see screenshots console for manual purges, supports regular expressions so you can purge an entire folder or just a single file supports every type of Varnish Cache implementation, see screenshots for examples unlimited number of Varnish Cache servers use of custom headers when communicating with Varnish Cache does not interfere with other caching plugins, cloudflare, etc Varnish Cache configuration generator purge key method so you don’t need to setup ACLs debugging actively maintained You can control the following from the Varnish Caching admin panel : Enable/Disable caching Homepage cache TTL Cache TTL (for every other page) IPs/Hosts to clear cache to support every type of Varnish Cache implementation Override default TTL in posts/pages Purge key based PURGE Logged in cookie Debugging option console for precise manual purges This plugin also auto purges Varnish Cache / Nginx Proxy Cache when your site is modified. Varnish Caching sends a PURGE request to Varnish Cache / Nginx Proxy Cache when a page or post is modified. This occurs when editing, publishing, commenting or deleting an item, and when changing themes. Not all pages are purged every time, depending on your Varnish / Nginx Proxy Cache configuration. When a post, page, or custom post type is edited, or a new comment is added, only the following pages will purge: The front page The post/page edited Any categories or tags associated with the page Varnish Cache / Nginx Proxy Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. This plugin does not install Varnish/Nginx for you, nor does it configure Varnish/Nginx for WordPress. It’s expected you already did that on your own using the provided config files. Inspired from the following : https://wordpress.org/plugins/varnish-http-purge/ https://github.com/dreamhost/varnish-vcl-collection/