Ko Takagi

qrac

<p>“WP IE Buster” is a popup display plug-in that urges Chrome to Internet Explorer (IE) users. I made it to save WordPress developers.</p>
<p>In many cases, IE users are not aware of browser type. Even if I strongly deny IE, a more natural approach is needed because a regrettable response comes back “What is that?”</p>
<p>So I developed “WP IE Buster”. Just by activating the plugin, users using IE 8 – 11 will see a popup prompting for Chrome download.</p>
<p>UI is Microsoft ‘s Fabric style. There is no close button. It is because you will not be able to continue browsing with browsers that are not recommended environment.</p>
<p>We will deliver the right proposal to the IE user as politely as possible.</p>
<p>Although it may not be as strong as the naming destructive power, I’d appreciate it if “WP IE Buster” becomes one that saves web makers.</p>


WP IE Buster

Save WordPress creators with Chrome link popup for IE.

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.

WP IE Buster vs Super Light Cache Buster