ergonet

<p>Ergonet Cache for WordPress is a free plugin developed by Ergonet srl, an Italian hosting company, to drastically improve the performance of a WordPress website by using a server-side page caching system (NGINX Cache or Varnish Cache).</p>
<h3>BENEFITS</h3>
<p>Using a server-side caching system increases your WordPress site’s performance by a minimum of 30% and up to 70%. Keep in mind that the actual improvement will also depend on your overall website optimization strategy.</p>
<h3>WHAT IS PAGE CACHE AND HOW DOES IT WORK?</h3>
<p>Page cache speeds up your website by storing the entire HTML of web pages directly on the web server, instantly serving them to visitors without needing to query the PHP server or the database again. Depending on your hosting plan, you can enable NGINX page cache (Equilibrio plan) or advanced RAM-based Varnish page cache (Progresso and Successo plans).</p>
<h3>COMPATIBILITY</h3>
<p>The Ergonet Cache plugin is compatible with all other website caching and optimization plugins, such as WP Rocket, W3 Total Cache, WO Optimize, etc.<br />
The Ergonet Cache plugin functions solely as a communication layer between WordPress and the cache system (Varnish or NGINX) installed on the WordPress hosting platform (any plan) and dedicated cloud hosting (Solo and Multidomain plans) offered by Ergonet, available for purchase at this link: https://www.ergonet.it/hosting/hosting-wordpress-valore<br />
A fundamental requirement for the plugin to work is enabling the caching system from the WebPanel (Ergonet client area available at https://webpanel.ergonet.it) by the user who purchased the shared or dedicated cloud hosting service.</p>
<h3>HOW THE PLUGIN WORKS</h3>
<p>Once the caching system is enabled from the Ergonet WebPanel and the Ergonet Cache plugin is installed and activated, it will work without any additional configuration.<br />
Cache resource updates<br />
Each time the webmaster updates a post or page, the plugin installed in WordPress will automatically delete the old cached version to prevent users from seeing outdated content.<br />
At the same time, the homepage cache will also be cleared to reflect any new articles available on it.<br />
Cache resource deletion<br />
Thanks to the automatic update and removal functionality, there is no need to manually clear the cache. Moreover, forcibly clearing the entire cache is discouraged, as it would remove all previously stored resources (pages, articles, etc.) that had been frequently accessed.<br />
On websites with a large amount of content, a full cache purge could also cause significant slowdowns due to WordPress needing to regenerate all requested pages or articles from scratch.</p>
<h3>WHAT IS NOT CACHED</h3>
<p>To ensure the plugin works efficiently, some resources and specific HTTP calls are never cached. These include:</p>
<ul>
<li>Any page, article/resource visited by a logged-in user.</li>
<li>Any page, article/resource where a no-cache header or similar is set.</li>
<li>All requests made to the WordPress backend.</li>
<li>All data submission requests (e.g., registration forms, contact forms, comments, etc.)</li>
</ul>
<h3>HOW TO CHECK IF CACHING IS WORKING</h3>
<p>The server-side cache system sets specific HTTP headers indicating whether the requested resource (link) is cached or not. To verify if your website is using the cache correctly, you must check for these HTTP headers.<br />
It’s essential to ensure you are logged out of the WordPress site you’re checking, as well as from any other WordPress site open in other browser tabs. The first step is therefore to log out from the WordPress admin area.<br />
Open the developer tools based on your browser:</p>
<p>For Firefox: Menu <span aria-hidden="true" class="wp-exclude-emoji">→</span> Browser Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Browser Console</p>
<p>For Chrome: View <span aria-hidden="true" class="wp-exclude-emoji">→</span> Developer Options <span aria-hidden="true" class="wp-exclude-emoji">→</span> Developer Tools</p>
<p>Once the developer tools are open:</p>
<p>Select the “Network” tab<br />
In Firefox, choose the “HTML” sub-tab, in Chrome, choose “Doc”<br />
Refresh the website page<br />
Click on the first row showing the domain name or visited link (with status 200)</p>
<p>In the right-hand column, you’ll see the response headers. The last header refers to the cache:</p>
<h3>VARNISH CACHE HEADER</h3>
<p>X-VC-Cache: HIT = the resource (page) is present in cache and was served from the Varnish cache system. This means the caching system is working properly.<br />
X-VC-Cache: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor.</p>
<h3>NGINX CACHE HEADER</h3>
<p>x-cache-status: HIT or STALE = the resource (page) is present in cache and was served from the NGINX cache system. This means the caching system is working properly.<br />
x-cache-status: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor.</p>
<h3>ENABLING THE CACHING SYSTEM FROM THE WEBPANEL</h3>
<p>The NGINX caching system is enabled by default and doesn’t require any specific settings.<br />
To enable the Varnish caching system, we recommend checking the dedicated guide: https://docs.ergonet.it/gestione-hosting/impostazioni-cache-server/cache-varnish</p>


Ergonet Cache

Ergonet Cache for WordPress is a free plugin developed by Ergonet srl, an Italian hosting company, to drastically improve the performance of a WordPre …

webheadcoder

<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Works with the following caching plugins:</p>
<ul>
<li>Autoptimize</li>
<li>Breeze Cache</li>
<li>Cache Enabler</li>
<li>GoDaddy Cache</li>
<li>Kinsta Cache</li>
<li>LiteSpeed Cache</li>
<li>Elementor (CSS cache)</li>
<li>Premium Addons for Elementor</li>
<li>SiteGround SuperCacher</li>
<li>Super Page Cache</li>
<li>WP Fastest Cache</li>
<li>WP Optimize Cache</li>
<li>WP Rocket</li>
<li>WP Super Cache</li>
<li>W3 Total Cache</li>
<li>WPEngine Cache</li>
</ul>
<p>Clears all cache for following actions (requires a caching system above to be active):</p>
<ul>
<li>When Widgets are saved.</li>
<li>When Customizer is saved.</li>
<li>When Menus are saved.</li>
<li>When a fields in Advanced Custom Fields are saved.</li>
<li>When a Contact Form 7 form is saved.</li>
<li>When a Formidable Form form is saved.</li>
<li>When WooThemes settings are saved.</li>
<li>When NextGen Gallery albums and galleries are updated (beta – may not clear cache on all actions).</li>
<li>When Qode options are saved this plugin forces browsers to reload the custom css and custom js.</li>
<li>When a WP Forms forms or settings are saved.</li>
<li>When WooCommerce settings are saved. (Cache should already be clearing when products are saved.)</li>
<li>When settings from the Insert Headers and Footers plugin by WPBeginner are saved.  </li>
<li>When Settings from a settings page is saved.  This includes settings from WordPress core, Yoast SEO, and most other plugins using the Settings API.</li>
<li>When WordPress is updated.</li>
<li>When plugins are updated, activated, and deactivated.</li>
<li>When WordPress, plugins, and themes are automaticallly updated.</li>
</ul>
<p><a href="https://webheadcoder.com/clear-cache-for-me/" rel="nofollow ugc">See the plugin’s homepage for more details</a>.</p>
<p>Note:  Since some caching systems run in the <code>shutdown</code> hook, this plugin also runs in that hook.  This means if PHP does not have enough time, some code including any hooks within the <code>ccfm_clear_cache_for_all()</code> function are not guaranteed to run.  If you need code to run, consider using the <code>ccfm_clear_cache_for_me_setup</code> hook.</p>
<h3>Developer Options</h3>
<h4>ccfm_supported_caching_exists</h4>
<p>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.<br />
Default: True if any of the supported caching systems is active.<br />
See Example 1 below.</p>
<h4>ccfm_admin_init or ccfm_init_actions</h4>
<p>Use this action to add hooks when cache is to be cleared.  Or do any other setup activity.</p>
<h4>ccfm_clear_cache_for_me_before</h4>
<p>Use this action to clear cache from an unsupported caching system before the default caching systems clear their cache.</p>
<h4>ccfm_clear_cache_for_me</h4>
<p>Use this action to clear cache from an unsupported caching system after the default caching systems clear their cache.</p>
<h4>Example</h4>
<p>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 <code>MyOtherCache::clear_all()</code> function, you would use the following code to get this plugin to clear the cache.</p>
<pre><code><?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');
</code></pre>


Clear Cache for Me

Purges cache on WPEngine, W3TC, WP Super Cache, WP Fastest Cache when widgets, menus, settings update.  Forces browsers to reload CSS and JS files.

Ergonet Cache vs Clear Cache for Me