mi13

<p>Mi13 Cache is a simple and effective plugin for caching WordPress pages. It saves HTML pages as files and serves them on subsequent requests, significantly speeding up site loading.</p>
<p><strong>Key features:</strong></p>
<ul>
<li>Line-by-line caching of HTML pages.</li>
<li>Flexible settings: select which page types to cache.</li>
<li>Automatic cache clearing when content is updated.</li>
<li>Cache status displayed as an HTML comment at the beginning of the file.</li>
<li>Cache statistics: file size and number of files.</li>
<li>Security: access permission checks and filtering of system pages.</li>
<li>Compatibility with custom post types.</li>
</ul>
<h3>Usage</h3>
<p>After activation:</p>
<pre><code>Go to Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Mi13 Cache.

Configure the settings:

    Select page types to cache (home page, posts, pages, categories, archives, custom types).

    Set the cache lifetime (in seconds; default is 86 400 s / 24 hours).

    Clear the cache manually using the Clear Cache button (if needed).

Save the settings.
</code></pre>
<p>You can check the cache status in the page source code:</p>
<pre><code>Open the page source code (press Ctrl+U or right-click <span aria-hidden="true" class="wp-exclude-emoji">→</span> “View Page Source”).

Look for a comment at the very beginning of the HTML file, like this: <h3>Settings</h3>
Page types — select which content types to cache.

Cache lifetime — the interval in seconds after which the cache expires.

Clear cache — a button to manually clear all cached files.<h3>HTML comment format</h3>
</code></pre>
<p>The plugin adds an HTML comment with information to the beginning of each cached file: </p>
<h3>Limitations</h3>
<p>Caching does not apply to:</p>
<pre><code>authenticated users;

the admin panel;

404 pages;

search pages (?s=...);

RSS feeds (/feed/);

AJAX requests;

POST requests;

URLs with GET parameters (except paged for pagination).<h3>Troubleshooting</h3>
</code></pre>
<p>Issue: the cache is not created.<br />
Solution: make sure that:</p>
<pre><code>define('WP_CACHE', true) is present in wp-config.php;
WordPress has write permissions for /wp-content/cache/mi13-cache/.
</code></pre>
<p>Issue: pages do not update after editing.<br />
Solution: manually clear the cache on the settings page.</p>
<p>Issue: access permission error when clearing the cache.<br />
Solution: check file permissions in the cache directory.</p>
<h3>Security</h3>
<pre><code>Permission check (manage_options) before clearing the cache.

Caching disabled for authenticated users.

Exclusion of system pages (404, search, feed, etc.).

Use of the secure WordPress API for file system operations.<h3>Directory structure</h3>
Cached files are saved in: /wp-content/cache/mi13-cache/

Each file has the .html extension and a name corresponding to the page URL.
</code></pre>

mi13 сache

A lightweight plugin for line-by-line caching of WordPress pages. Speeds up site loading by saving static copies of pages.

Milan Dinić

<p><a href="http://blog.milandinic.com/wordpress/plugins/purge-cache-for-cloudflare/" rel="nofollow ugc">Plugin homepage</a> | <a href="http://blog.milandinic.com/" rel="nofollow ugc">Plugin author</a> | <strong><a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">Premium Version</a></strong> | <a href="http://blog.milandinic.com/donate/" rel="nofollow ugc">Donate</a></p>
<p>Purge Cache for CloudFlare is a simple plugin that uses CloudFlare® API to purge cache of full HTML pages when a new post is made.</p>
<p>This free version is only indended for basic usage. If you want to use it in full capacity, consider buying <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.</p>
<p>It works by purging front page, post’s page, and main RSS feed. This should work for most sites. However, there are of filters, actions, and methods that provide full customizability and extensibility.</p>
<p>Note that this plugin also sets cache to 30 minutes for all frontend pages. This means that if you use default option in CloudFlare, it tells them to revalidate page cache after that time, so it means that cache for any page expires on CloudFlare servers after that time.</p>
<p>You can change this limits by using filters from you code. If you want user interface in your admin, use <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.</p>
<p>You should create new CloudFlare page rules to set proper caching. It is your responsibility to set this properly.</p>
<p>First page rule should exclude certain paths from caching. Recommended value for this is <code>wp-</code>. This excludes admin pages and default <code>.php</code> pages. Example of URL pattern: <code>*example.com/*wp-*</code> This value can also set via filter or via admin in <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.</p>
<p>Second page rule should sets caching. You need to set “Custom caching” to “Cache everything”. Recommended value for “Edge cache expire TTL” is default, “Respect all existing headers” which means that CloudFlare revalidates after 30 minutes, while for “Browser cache expire TTL” is also 30 minutes. Example of URL pattern: <code>*example.com/*</code></p>
<p>This plugin is on <a href="https://github.com/dimadin/purge-cache-for-cloudflare" rel="nofollow ugc">GitHub</a> too.</p>
<p>Purge Cache for CloudFlare is in no way affiliated with CloudFlare. It is only using CloudFlare API to purge page cache of certain URLs.<br />
CloudFlare is registered trademark of CloudFlare, Inc.</p>


Purge Cache for CloudFlare

Simple full HTML page cache purger for CloudFlare.

mi13 сache vs Purge Cache for CloudFlare