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.

Vladimir Kolesnikov

<p>The plugin solves two problems:</p>
<ol>
<li>When WordPress detects that FastCGI PHP SAPI is in use, it<br />
<a href="http://blog.sjinks.pro/wordpress/510-wordpress-fastcgi-and-301-redirect/" rel="nofollow ugc">disregards the redirect status code</a><br />
passed to <code>wp_redirect</code>. Thus, all 301 redrects become 302 redirects<br />
which may not be good for SEO. The plugin overrides <code>wp_redirect</code> when it detects<br />
that nginx is used.</li>
<li>When WordPress detects that <code>mod_rewrite</code> is not loaded (which is the case for nginx as<br />
it does not load any Apache modules) it falls back to <a href="https://codex.wordpress.org/Using_Permalinks#PATHINFO:_.22Almost_Pretty.22" rel="nofollow ugc">PATHINFO permalinks</a><br />
in Permalink Settings page. nginx itself has built-in support for URL rewriting and does not need<br />
PATHINFO permalinks. Thus, when the plugin detects that nginx is used, it makes WordPress think<br />
that <code>mod_rewrite</code> is loaded and it is OK to use pretty permalinks.</li>
</ol>
<p>The plugin does not require any configuration. It just does its work.<br />
You won’t notice it — install and forget.</p>
<p><strong>WARNING:</strong> nginx must be configured properly to support permalinks.</p>
<h3>nginx Configuration</h3>
<p><strong>nginx 0.7.32 and higher:</strong></p>
<pre><code>server {
    server_name mysite.com;

    root /path/to/blog;

    index index.php;

    error_page 404 = @wordpress;
    log_not_found off;

    location ^~ /files/ {
        rewrite /files/(.+) /wp-includes/ms-files.php?file=$1 last;
    }

    location @wordpress {
        fastcgi_pass ...;
        fastcgi_param SCRIPT_FILENAME $document_root/index.php;
        include /etc/nginx/fastcgi_params;
        fastcgi_param SCRIPT_NAME /index.php;
    }

    location ~ \.php$ {
        try_files $uri @wordpress;
        fastcgi_index index.php;
        fastcgi_pass ...;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include /etc/nginx/fastcgi_params;
    }

    location ^~ /blogs.dir/ {
        internal;
        root /path/to/blog/wp-content;
    }
}
</code></pre>
<p><strong>Older versions:</strong></p>
<pre><code>server {
    server_name mysite.com;

    root /path/to/blog;

    index index.php;

    log_not_found off;
    error_page 404 = @wordpress;

    location ^~ /files/ {
        rewrite /files/(.+) /wp-includes/ms-files.php?file=$1 last;
    }

    location @wordpress {
        fastcgi_pass ...;
        fastcgi_param SCRIPT_FILENAME $document_root/index.php;
        include /etc/nginx/fastcgi_params;
        fastcgi_param SCRIPT_NAME /index.php;
    }

    location ~ \.php$ {
        if (!-e $request_filename) {
            rewrite ^(.+)$ /index.php break;
            break;
        }

        fastcgi_index index.php;
        fastcgi_pass ...;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include /etc/nginx/fastcgi_params;
    }

    location ^~ /blogs.dir/ {
        internal;
        root /path/to/blog/wp-content;
    }
}
</code></pre>
<p>Of course, do not forget to replace <code>...</code> in <code>fastcgi_pass</code> with the address/socket<br />
php-cgi is listening on and replace /path/to/blog with the actual path.</p>
<p>Also please note that the path in <code>SCRIPT_NAME</code> should be relative to the <code>DOCUMENT_ROOT</code> (<code>root</code> directive).<br />
Thus, if your WordPress blog resides in <code>http://example.com/blog/</code>, <code>root</code> is set to <code>/path.to/example.com</code>,<br />
    SCRIPT_NAME in <code>location @wordpress</code> will be <code>/blog/index.php</code>.</p>
<p><strong><a href="http://blog.sjinks.pro/wordpress/874-wpms-nginx-accel-redirect/" rel="nofollow ugc">Multi-Site Configuration</a>:</strong> the above configs work perfectly with WordPress MultiSite. To make downloads faster, consider adding this line to <code>wp-config.php</code>:</p>
<pre><code>define('WPMU_ACCEL_REDIRECT', true);
</code></pre>
<p><strong>Need help with configuring nginx?</strong> Contact me: vkolesnikov at odesk dot com, I will try to help you.</p>


nginx Compatibility

The plugin makes WordPress more friendly to nginx.

Docket Cache – Object Cache Accelerator vs nginx Compatibility