Nawawi Jamili

<p>Docket Cache is a persistent WordPress Object Cache that stores cached data as plain PHP code. It is designed as an alternative for sites that do not have access to Redis or Memcached.</p>
<p>Most file-based caching plugins use <a href="https://www.php.net/manual/en/function.serialize.php" rel="nofollow ugc">serializing</a> and <a href="https://www.php.net/manual/en/function.unserialize.php" rel="nofollow ugc">unserializing</a> to save PHP objects to flat files. Docket Cache takes a different approach by converting objects into plain PHP code. This makes data retrieval faster and improves overall performance, especially when Zend OPcache is enabled.</p>
<p>For more information, please refer to the documentation on <a href="https://docs.docketcache.com/resources/caching-in-wordpress" rel="nofollow ugc">Caching In WordPress</a>.</p>
<h3>Why use this plugin?</h3>
<p>For reliable persistent Object Cache in WordPress, <a href="https://redis.io/" rel="nofollow ugc">Redis</a> or <a href="https://memcached.org/" rel="nofollow ugc">Memcached</a> are the top choices. However, they require server knowledge and are rarely available on low-cost or shared hosting plans.</p>
<p>The alternative is to store object caches in files. In WordPress, exporting PHP objects is not straightforward. Most file-based caching plugins rely on serialising and unserialising objects to store and retrieve data.</p>
<p>Docket Cache takes a better approach by turning the object cache into plain PHP code. This is faster because WordPress can use the cache directly without additional processing.</p>
<h3>Features</h3>
<ul>
<li>Object caching + OPcache</li>
<li>Advanced Post Caching</li>
<li>Object Cache Precaching</li>
<li>WordPress Menu Caching</li>
<li>WordPress Translation Caching</li>
<li>WordPress Core Query Optimisation</li>
<li>Term Count Queries Optimisation</li>
<li>Post, Page, Comment Count Optimisation</li>
<li>Database Tables Optimisation</li>
<li>WooCommerce Optimisation</li>
<li>WP Options Autoload suspension</li>
<li>Post Missed Schedule Tweaks</li>
<li>Object Cache + OPcache Stats + OPcache Viewer</li>
<li>Cache Log</li>
<li>Cronbot Service</li>
<li>WP-CLI support</li>
<li>Multisite / Multi-Network support</li>
</ul>
<h3>Requirements</h3>
<p>To use Docket Cache requires minimum:</p>
<ul>
<li>PHP 7.2.5</li>
<li>WordPress 5.4</li>
<li>Zend OPcache</li>
</ul>
<h3>Documentation</h3>
<p>For configuration options, installation guides, and command-line usage, please refer to the <a href="https://docs.docketcache.com" rel="nofollow ugc">Documentation</a>.</p>
<h3>Development</h3>
<ul>
<li><a href="https://github.com/nawawi/docket-cache/" rel="nofollow ugc">GitHub Repository</a> — Source code and development hub for Docket Cache.</li>
<li><a href="https://raw.githubusercontent.com/nawawi/docket-cache/master/changelog.txt" rel="nofollow ugc">Changelog</a> — Full history of changes, fixes, and improvements.</li>
<li><a href="https://github.com/ghostbirdme/gapo" rel="nofollow ugc">Gapo Tunnel</a> — Expose local services to the internet through secure tunnels. Useful for testing Docket Cache on a local development environment.</li>
</ul>
<h3>Sponsor This Project</h3>
<p>Support the ongoing development of Docket Cache with a <a href="https://docketcache.com/sponsorship/?utm_source=wp-readme&utm_campaign=sponsor-uri&utm_medium=wporg" rel="nofollow ugc">one-off or recurring contribution</a>.</p>
<p><strong>Noteworthy Sponsors:</strong></p>
<p>A heartfelt thanks and appreciation.</p>
<ul>
<li><a href="https://jimathosting.com/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Jimat Hosting</a></li>
<li><a href="https://www.themecloud.io/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Themecloud</a></li>
<li><a href="https://websavers.ca/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Websavers Inc</a></li>
<li><a href="https://avu.nu/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Avunu LLC</a></li>
<li><a href="https://linqru.jp/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Linqru</a></li>
<li><a href="https://www.gentlemansguru.com/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Gentleman’s Guru</a></li>
<li><a href="https://www.securepay.my/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">SecurePay</a></li>
<li><a href="https://dnsvault.net/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">DNSVault</a></li>
<li><a href="https://exnano.io/?utm_source=docketcache&utm_campaign=plugin-uri&utm_medium=wporg" rel="nofollow ugc">Exnano Creative</a></li>
</ul>
<p>Other sponsors are mentioned in the <a href="https://github.com/nawawi/docket-cache/issues/5" rel="nofollow ugc">honourable list</a></p>


Docket Cache – Object Cache Accelerator

I have installed the plugin and enable Opcache. It just works and will always be my must installed plugins for every WordPress installation!

It just works!

It greatly reduces the RAM consumption of WordPress

The best solution to reduce RAM consumption and reduce WordPress resource consumption
Very efficient

BEST BEST BEST


Works flawless, really simple way to test object cache locally when developing, without needing to setup memchache or redis or similar.


Easy to use and setup

Speed up your WordPress site with a persistent object cache, powered by OPcache. An efficient alternative to Redis and Memcached.

Cacholong

Preliot

<p>“Cache control by Cacholong” plugin automates purging of Nginx FastCGI cache on your Nginx server(s). It is a backend plugin that is able to:</p>
<ul>
<li>Purge Nginx FastCGI cache.</li>
<li>Purge cache automatically, manually, with WordPress cronjobs and WP-CLI.</li>
<li>Purge caches on one or more servers (See hosts.json section for more details).</li>
<li>Use commandline (WP-CLI) to purge caches or reset to factory settings.</li>
<li>Allow purging of other cached items (see Settings > Cache control).</li>
<li>Inform user of purge status.</li>
<li>Support for single site and network sites</li>
<li>Support for WP-CLI</li>
<li>Support for WPML (including language negotiation type domain)</li>
</ul>
<h4>When will it purge?</h4>
<p>This plugin will work with default and custom post types. It will purge on a save, regular update, quick edit update, slug change, delete and undelete. The user is informed with one or more messages.<br />
There are a few caveats:</p>
<ul>
<li>When a user is using the Gutenberg editor, purge messages will not be displayed.</li>
<li>When the user uses “Quick edit” and “Updates” the post, no messages will be displayed, because there’s no page refresh. Those messages will be shown on the next request. </li>
</ul>
<p>It is possible to purge with WordPress cronjobs. Adjust the ‘Cronjob settings’ to perform a daily purge of caches.</p>
<p>You can also purge items manually. Go to the WordPress dashboard and navigate to:</p>
<ul>
<li>Settings > Cache control > purge single item</li>
<li>Settings > Cache control > purge all caches</li>
<li>Admin Toolbar > purge all caches</li>
</ul>
<h4>Settings</h4>
<ul>
<li>File with hosts (JSON):                 File with information about one or more hosts for this WordPress installation. See hosts.json section for more details.</li>
<li>Purge settings default post types:      Select one or more options when purging a default post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.</li>
<li>Purge settings default custom type(s):  Select one or more options when purging a custom post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.</li>
</ul>
<h4>Cronjob Settings</h4>
<ul>
<li>Cronjob purging:                        Enable or disable cronjob purging. </li>
<li>Cronjob time of each day:               Enter HH:MM in 24 hour notation for cronjob time of day. Will fallback to 00:00 when wrong format is given.</li>
<li>Purge caches                            Select caches to purge on given cronjob time. </li>
</ul>
<h4>hosts.json</h4>
<p>Hosts.json is a JSON file with information about one or more servers for this WordPress installation. Remember that this file must contain information about all servers, including the<br />
one with this plugin. Default path is: wp-content/uploads/cacholong-cache-control/hosts.json.</p>
<p>Here is an example of a hosts.json file:</p>
<pre><code>{"servers":
    [
        {"name": "server1", "ip": "127.0.0.1", "fastcgi": false},
        {"name": "server2", "ip": "127.0.0.2", "fastcgi": true},
    ]
}
</code></pre>
<p>Each line contains information about one server. Parameters:</p>
<ul>
<li>
<p>name (string)<br />
Name of host, something to identify this server.</p>
</li>
<li>
<p>ip (string)<br />
IP address of server or full url. Format: scheme://host:port/path</p>
</li>
<li>
<p>fastcgi (bool)<br />
Server user Nginx FastCGI (true) or not (false)</p>
</li>
</ul>
<p>When there is no hosts.json or the path is invalid, this plugin assumes the following:</p>
<pre><code>{"servers":
    [
        {"name": "localhost", "ip": "127.0.0.1", "fastcgi": true}
    ]
}
</code></pre>
<h4>How does it work</h4>
<p>“Cache control by Cacholong” empties partial or full cache for Nginx FastCGI cache. WordPress HTTP API is used to make (post) request to<br />
specific urls to trigger purges. Based on the http header responses this plugin determines if a purge is successful or not. The user is informed with messages, which are loaded after a purge and page refresh.</p>
<p>There are several settings to tweak purging, see Settings > Cache control.</p>
<h4>WP-CLI</h4>
<p>There are several commands available for the commandline with wp-cli. Commands generate text output which can be suppressed with –quiet. When an error occurs, text will always be displayed.</p>
<h4>WP-CLI exit codes</h4>
<p>Exit codes are 0 (no errors) or 1 (generic error).</p>
<h4>WP-CLI examples</h4>
<p>Purge command with all arguments:</p>
<pre><code>wp cacholong_cc purge [--cache=<cache>] [--ips=<ips>]
</code></pre>
<p>Purge Nginx FastCGI:</p>
<pre><code>wp cacholong_cc purge --cache=fastcgi
</code></pre>
<p>Purge all caches:</p>
<pre><code>wp cacholong_cc purge --cache=all
wp cacholong_cc purge
</code></pre>
<p>Purge all caches for ip address 127.0.0.1 and 127.0.0.2:</p>
<pre><code>wp cacholong_cc purge --ips=127.0.0.1,127.0.0.2
</code></pre>
<p>Factory reset options for given site_id or current blog if no site_id is given:</p>
<pre><code>wp cacholong_cc factory_reset [--site_id=site_id]
</code></pre>
<h4>Debug</h4>
<p>Plugin will log basic purge information when WP_DEBUG is true (can be set in wp-config.php). Logs information in file wp-content/cacholong-cache-control.log.<br />
Plugin will log wp_remote_request details when CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST is true (can be set in wp-config.php). Logs information in file wp-content/cacholong-cache-control.log.</p>


Cache control by Cacholong

“Cache control by Cacholong” is a cache control plugin for one or more Nginx servers.

Docket Cache – Object Cache Accelerator vs Cache control by Cacholong