wao.io

<p>wao.io Cache Control is a free plugin to clear your WordPress site’s cache at <a href="https://wao.io/en/?utm_source=wordpressMarketplace&utm_medium=description&utm_campaign=CachePlugin" rel="nofollow ugc">wao.io</a>.</p>
<h3>Cache Control</h3>
<p>Use this plugin to control your site’s cache at wao.io.</p>
<p>Click on the <strong>Invalidate Origin Content</strong> button to clear your optimized WordPress website’s cache at wao.io<br />
to make sure that you and your customers will see the latest version of your content.</p>
<p>Cache invalidation will automatically be triggered after publishing or updating a post or a page, and after switching a theme.</p>
<p>Cache invalidation treats all content in the cache as if it was outdated.<br />
This means that wao.io will check on the next request if the content changed on the origin server.<br />
If so, it will be requested. Otherwise wao.io will continue to use the cached resource.<br />
This is especially useful if you changed only a few images and the majority of content remained unmodified.</p>
<h3>Settings</h3>
<p>In the <strong>wao.io Cache Control Settings</strong> section of your general WordPress settings,<br />
please enter your Site ID, and the API key that you obtained from wao.io’s support team.</p>
<p>If you do not have an API key yet, please contact <a href="https://wao.io/en/account/support?utm_source=wordpressMarketplace&utm_medium=description&utm_campaign=CachePlugin" rel="nofollow ugc">wao.io support</a>.</p>
<p>In future versions of this plugin, you can disable or enable automatic cache invalidation here.</p>
<h3>Automatic Cache Invalidation</h3>
<p>Automatic cache invalidation will make WordPress try to invalidate your<br />
optimized WordPress website’s cache at wao.io automatically each time your content has changed,<br />
e.g. after publishing a page or uploading an image.</p>
<h3>Known Issues</h3>
<p>Some WordPress sites reported a bug that the publish / update post event did not fire when using the block editor (Gutenberg issue #17632).<br />
This may affect the plugin wao.io Cache Control which depends on the event for automatic cache invalidation.</p>
<h3>Development and Contribution</h3>
<p>wao.io Cache Control plugin for WordPress was developed for wao.io by Ingo Steinke, Senior Software Developer at Avenga Germany GmbH.</p>
<p>If you want to contribute to this plugin, please contact wao.io product development via our <a href="https://wao.io/en/?utm_source=wordpressMarketplace&utm_medium=description&utm_campaign=CachePlugin" rel="nofollow ugc">website wao.io</a>.</p>


wao.io Cache Control

This plugin comes in handy if your WordPress site is optimized by wao.io and you update your site content frequently. The automatic trigger invalidates your site cache automatically after posting, editing or uploading new images, to make sure the updated content is visible immediately while still enjoying the benefit or an additional cache and image optimizer. To be sure, you can use the manual cache invalidation buttons, so you're always in total control of your content. 

Useful automatic cache invalidation

wao.io Cache Control is a free plugin to clear your WordPress site's cache at wao.io.

Mwale Kalenga

<p>Can’t see the changes supposedly made by your developer? Or maybe you’re just tired of your site’s annoying cache? Use this plugin to cache a break!</p>
<p>With a compressed size of under 30KB, this simple plugin adds random version numbers to CSS & JS assets to prevent browser caching getting in the way of your happiness.</p>
<p>Super Light Cache Buster also prevents page caching by using Cache-Control directives.</p>
<p>You can completely disable the plugin from the settings page when you are not using it or keep it enabled if the site is under development. 😀</p>
<h3>Available Hooks</h3>
<p>Cache Buster is becoming more developer friendly. Below you can find the plugin’s first hooks and details about them.</p>
<pre><code>slcb_allow_in_backend
</code></pre>
<ul>
<li>Filters whether Cache Buster should run (randomize asset version numbers) in the back end.</li>
<li>
<p>Return <code>true</code> to enable Cache Buster. <code>false</code> is the default.</p>
<p>slcb_version_name</p>
</li>
<li>
<p>Filters the version name for assets to allow using a custom version name (or number).</p>
</li>
<li>Return the version name e.g. you can use the value <code>2.0.1</code>.</li>
<li>When this filter is in use, version numbers will not be randomized. Instead, you will have to change the version name manually to rename assets.</li>
<li>This filter overrides the “Version Name” setting in the dashboard.</li>
<li>The provided version name must be a valid query parameter. As a safety, if the provided string breaks any URLs, it will not be used.</li>
</ul>
<h3>Feedback</h3>
<ul>
<li>I am open for your suggestions and feedback – Thank you for using or trying out one of my plugins!</li>
<li>Drop me a line <a href="https://twitter.com/mwale_and_sons" rel="nofollow ugc">@mwale_and_sons</a> on Twitter</li>
<li>Follow me on <a href="https://www.linkedin.com/in/mwale-kalenga" rel="nofollow ugc">my LinkedIn page</a></li>
<li>Or visit me at <a href="https://mwale.me/" rel="nofollow ugc">my website</a>.</li>
</ul>
<h3>Do I have to clear my cache for the plugin to work?</h3>
<p>Yes, you should clear your cache(s)! This plugin doesn’t clear pages that have already been cached (coming soon, shhh).</p>
<p>If you are still being served cached pages after activating the plugin, clear the cache at least once.</p>
<p>This will delete all pages/posts from the cache, and Cache Buster will prevent them from being cached again while the plugin is enabled :-).</p>
<h3>Does this plugin work on Multisite?</h3>
<p>No, Cache Buster hasn’t been tested on Multisite Networks.</p>


Super Light Cache Buster

works great, would be nice in the future to see for all assets (incl. images), not just css/js.

works as intended

Helpful!

Lightweight and excellent support

Stop page & browser caching with random version numbers and Cache-Control directives.

wao.io Cache Control vs Super Light Cache Buster