{"id":11984,"date":"2026-11-05T23:39:00","date_gmt":"2026-11-05T15:39:00","guid":{"rendered":"https:\/\/aeosub.com\/zinn-cache\/"},"modified":"2026-11-05T23:39:00","modified_gmt":"2026-11-05T15:39:00","slug":"zinn-cache","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/zinn-cache\/","title":{"rendered":"Zinn\u00ae Cache"},"content":{"rendered":"<div class=\"post-img\" style=\"margin-bottom: 25px\"><img decoding=\"async\" src=\"https:\/\/ps.w.org\/zinn-cache\/assets\/banner-1544x500.png?rev=3723630\" alt=\"Zinn\u00ae Cache\" loading=\"lazy\" style=\"width: 100%;height: auto;border-radius: 12px\"><\/div>\n<div class=\"plugin-info-card\" style=\"border: 1px solid #e2e8f0;border-radius: 10px;overflow: hidden;margin-bottom: 30px;font-family: -apple-system, system-ui, sans-serif;background: #fff\">\n<div style=\"padding: 20px;border-bottom: 1px solid #edf2f7;background: #fafafa;display: flex;align-items: flex-start\">\n                <img decoding=\"async\" src=\"https:\/\/ps.w.org\/zinn-cache\/assets\/icon.svg?rev=3723630\" alt=\"Zinn\u00ae Cache icon\" loading=\"lazy\" style=\"width: 45px;height: 45px;border-radius: 8px;margin-right: 15px\"> <\/p>\n<div style=\"flex: 1;line-height: 1.2\">\n<div style=\"font-weight: bold;font-size: 1.1em;color: #1a202c\">Plugin Specification<\/div>\n<p>                    <small style=\"color: #718096\">WordPress.org Official Data<\/small>\n                <\/div>\n<\/p><\/div>\n<table style=\"width: 100%;border-collapse: collapse;font-size: 14px\">\n<tr style=\"border-bottom: 1px solid #edf2f7\">\n<th style=\"padding: 12px 20px;text-align: left;width: 35%;color: #4a5568;background: #fcfcfc\">Developer<\/th>\n<td style=\"padding: 12px 20px;font-weight: 500\"><a href=\"https:\/\/profiles.wordpress.org\/zinndigital\/\" target=\"_blank\" rel=\"noopener\">Zinn Digital\u00ae<\/a><\/td>\n<\/tr>\n<tr style=\"border-bottom: 1px solid #edf2f7\">\n<th style=\"padding: 12px 20px;text-align: left;color: #4a5568;background: #fcfcfc\">Version<\/th>\n<td style=\"padding: 12px 20px\">v1.11.3<\/td>\n<\/tr>\n<tr style=\"border-bottom: 1px solid #edf2f7\">\n<th style=\"padding: 12px 20px;text-align: left;color: #4a5568;background: #fcfcfc\">Active Installs<\/th>\n<td style=\"padding: 12px 20px\">50 +<\/td>\n<\/tr>\n<tr style=\"border-bottom: 1px solid #edf2f7\">\n<th style=\"padding: 12px 20px;text-align: left;color: #4a5568;background: #fcfcfc\">Requires \/ Tested<\/th>\n<td style=\"padding: 12px 20px\">6.6 \/ 7.1.4<\/td>\n<\/tr>\n<tr style=\"border-bottom: 1px solid #edf2f7\">\n<th style=\"padding: 12px 20px;text-align: left;color: #4a5568;background: #fcfcfc\">Last Updated<\/th>\n<td style=\"padding: 12px 20px\">2026-11-05 3:38pm GMT<\/td>\n<\/tr>\n<tr>\n<th style=\"padding: 12px 20px;text-align: left;color: #4a5568;background: #fcfcfc\">Official Link<\/th>\n<td style=\"padding: 12px 20px\"><a href=\"https:\/\/wordpress.org\/plugins\/zinn-cache\/\" target=\"_blank\" rel=\"noopener noreferrer\" style=\"text-decoration: none;color: #4a3bca;font-weight: bold\">View Details -&gt;<\/a><\/td>\n<\/tr>\n<\/table><\/div>\n<div class=\"plugin-short-desc\" style=\"margin: 20px 0;padding: 12px 15px;background: #f9fafb;border-left: 4px solid #4a3bca;border-radius: 6px;font-style: italic;color: #4a5568\">Page cache, Redis object cache and purging for nginx, Varnish, Apache, LiteSpeed and Cloudflare \u2014 updates refresh pages gradually, never all at once.<\/div>\n<p>Zinn\u00ae Cache makes a WordPress site faster wherever it is hosted. On a LiteSpeed server it drives the server&#8217;s own page cache. When nginx, Varnish or Apache already caches pages in front of WordPress, it does not add a second page cache behind them: it tells them which pages changed. On any other server it stores each page as a file and serves it before WordPress loads. It also installs a Redis object cache that proves it is working, and purges only the pages a change affects.<\/p>\n<p>It is installed for you on sites hosted with Zinn Digital\u00ae, and it works the same way on any other host. There is one Zinn\u00ae cache plugin; Zinn\u00ae Cache Pro is an optional add-on that installs on top of it (see Pro features below).<\/p>\n<p><strong>What it does<\/strong><\/p>\n<ul>\n<li><strong>Page cache on any server.<\/strong> On a LiteSpeed server it stamps <code>X-LiteSpeed-Cache-Control<\/code> and <code>X-LiteSpeed-Tag<\/code> headers so the web server serves full pages without hitting PHP or MySQL. On any other server it stores each complete page as a file under <code>wp-content\/cache\/zinn-cache\/<\/code> and serves it from <code>advanced-cache.php<\/code> before WordPress loads (it adds <code>define( 'WP_CACHE', true );<\/code> to <code>wp-config.php<\/code> for that, and removes it again when the page cache is turned off). Only visitors who are not signed in are served stored pages, and only addresses with no query string (tracking parameters such as <code>utm_source<\/code> are ignored). If the third-party LiteSpeed Cache plugin is present, page caching is deferred to it instead.<\/li>\n<li><strong>Smart auto-purge.<\/strong> When content changes \u2014 a post or page is saved, trashed or deleted, a comment is added or moderated, a taxonomy term is edited \u2014 only the affected pages (and the listings they appear on: its home page, archive, categories, tags and author page) are purged, on every cache layer: LiteSpeed by cache tag, the disk cache, nginx, Varnish, Apache and Cloudflare by address. A change that touches every page (the theme, a plugin, an update, a menu, the site title) starts the paced refresh described below. The plugin can also mirror each purge to a control panel over a signed webhook, but only when <code>ZINN_CACHE_PANEL_URL<\/code> is defined \u2014 and the Zinn Digital\u00ae platform does not set it today, so on a Zinn-hosted site purges happen on the server and are not mirrored anywhere.<\/li>\n<li><strong>Redis object cache.<\/strong> A one-click toggle installs a self-contained Redis object-cache drop-in (requires the phpredis extension), offloading repeated database reads. It signs in with a plain password or a Redis 6+ ACL username and password, honours the usual <code>WP_REDIS_*<\/code> constants (including <code>WP_REDIS_PASSWORD<\/code> given as <code>array( 'user', 'password' )<\/code>, <code>WP_REDIS_PATH<\/code> and <code>WP_REDIS_MAXTTL<\/code>), and proves itself with a write-and-read round trip: if Redis refuses the login or the data, the settings screen says why. It never overwrites another caching plugin&#8217;s drop-in, refreshes its own after an update, and falls back to an in-memory cache if Redis is unreachable. Choose the igbinary serializer (smaller and faster, when installed) or PHP&#8217;s own; each value is read in the format it was written in, so switching is safe.<\/li>\n<li><strong>Host-managed object cache.<\/strong> A host that installs this drop-in for its customers (as Zinn Digital\u00ae hosting does) defines <code>ZINN_CACHE_MANAGED_OBJECT_CACHE<\/code>; the plugin then never removes that drop-in and shows the cache as managed. A host whose Redis users may not run <code>SCAN<\/code> can define <code>ZINN_CACHE_FLUSH_SOCKET<\/code>, the path of a local helper that deletes only the calling site&#8217;s keys, so &#8220;Flush cache&#8221; keeps working.<\/li>\n<li><strong>Server caches in front of WordPress: nginx, Varnish, Apache.<\/strong> Zinn\u00ae Cache detects an nginx <code>proxy_cache<\/code>\/<code>fastcgi_cache<\/code>, Varnish, Apache <code>mod_cache<\/code> or LiteSpeed in front of the site from the response headers, and then keeps its own disk cache out of the way. Tell it how to reach the cache and it purges changed pages there: nginx by a purge request (the <code>ngx_cache_purge<\/code> module), by deleting the cache files when WordPress can read the cache folder, or by writing the changed addresses to a folder your host&#8217;s purger reads; Varnish by <code>PURGE<\/code> or <code>BAN<\/code>; Apache&#8217;s disk cache by deleting the entry files. Signed-in visitors, excluded addresses and form posts are sent <code>Cache-Control: private, no-store<\/code>, so a server cache never keeps one person&#8217;s page for the next.<\/li>\n<li><strong>Cloudflare purge.<\/strong> With a zone ID and an API token limited to Cache Purge, changed pages are purged from Cloudflare&#8217;s edge by address, in batches, from WP-Cron so editors never wait on it. Emptying the whole zone is off unless you allow it.<\/li>\n<li><strong>Paced refresh instead of &#8220;purge everything&#8221;.<\/strong> An update, a plugin activation, a theme or menu change or a site-wide setting no longer empties the cache at once, sending every visitor to WordPress in the same minute. Zinn\u00ae Cache refreshes a batch a minute instead (100 pages by default), newest first, to the end, and pauses while the server is busy. &#8220;Empty all now&#8221; is still there when you want it.<\/li>\n<li><strong>Status screen and per-address purge.<\/strong> One screen shows what serves your pages (LiteSpeed, nginx, Varnish, Apache, Cloudflare or the disk cache), what the last check saw in front of the site, each cache&#8217;s size where WordPress can read it, the purge queue, the paced refresh and recent purges with each layer&#8217;s answer. Purge any address, sample the hit ratio, or start and stop a refresh.<\/li>\n<li><strong>Autosave and an activity log.<\/strong> Settings save a moment after each change (the Save changes button stays). The Status screen lists the last 100 changes: who changed which setting (by name, never its value), who emptied the whole cache and when a paced refresh started.<\/li>\n<li><strong>Lighter pages.<\/strong> Control the WordPress Heartbeat, show text at once while Google Fonts load (<code>display=swap<\/code>), connect early to the servers your pages use, and serve images, CSS, JavaScript and fonts from a pull CDN address.<\/li>\n<li><strong>Safe cache exclusions.<\/strong> Ships with sensible WordPress and WooCommerce\/Easy Digital Downloads defaults \u2014 cart, checkout, my-account, REST\/AJAX, preview, search, and any logged-in or session-cookie request are never cached. Extra path, query-key, and cookie-prefix rules can be added per site.<\/li>\n<\/ul>\n<p><strong>Remote purging<\/strong><\/p>\n<p>A REST endpoint, <code>POST \/wp-json\/zinn-cache\/v1\/purge<\/code>, purges everything, specific URLs, or specific tags. It accepts a logged-in administrator, or any caller holding the site&#8217;s <code>ZINN_CACHE_PANEL_SECRET<\/code> who signs the request body with it (HMAC-SHA256) \u2014 so a deploy script or your own tooling can clear the cache. Your Zinn\u00ae dashboard does not call it today; there is no dashboard purge button for this plugin yet.<\/p>\n<h4>Pro features<\/h4>\n<p>Everything above is free and stays free. <a href=\"https:\/\/zinndigital.com\/wordpress-plugins\/zinn-cache-pro\" rel=\"nofollow ugc noopener\" target=\"_blank\">Zinn\u00ae Cache Pro<\/a> is an add-on that installs on top of this plugin and adds:<\/p>\n<ul>\n<li>A cache analytics screen: hit ratio, memory, keys and the slowest cache commands.<\/li>\n<li>A slow-query and uncached-call finder that names the plugin or theme responsible.<\/li>\n<li>An in-memory APCu tier in front of Redis for the hottest keys, plus prefetching and compression (zstd, lzf or gzip).<\/li>\n<li>Tag-based purging for posts, terms and WooCommerce products, so only what changed is cleared, with the page and object caches purged together.<\/li>\n<li>Automatic cache warm-up after a purge and when a paced refresh finishes, WebP and AVIF images, missing image width and height added from the file, unused-CSS removal and delayed JavaScript.<\/li>\n<li>Cloudflare&#8217;s own cache-hit ratio for the last 24 hours on the status screen.<\/li>\n<li>Scheduled database clean-up with a preview, and per-page cache rules.<\/li>\n<li>Cache health alerts in your Zinn Digital\u00ae dashboard when the hit ratio drops or memory fills.<\/li>\n<\/ul>\n<p>Pro costs $49 a year for one site, $99 for five sites and $199 for unlimited sites, and every plan starts with a 14-day free trial, no card needed. Start it from the Pro tab of the Zinn\u00ae Cache screen.<\/p>\n<h3>External services<\/h3>\n<h4>Cloudflare (only if you switch on Cloudflare purge)<\/h4>\n<p>When <strong>Cloudflare purge<\/strong> is on and a zone ID and API token are saved (or <code>ZINN_CACHE_CLOUDFLARE_ZONE<\/code> and <code>ZINN_CACHE_CLOUDFLARE_TOKEN<\/code> are defined), the plugin sends the addresses of changed pages on this site to <code>https:\/\/api.cloudflare.com\/client\/v4\/zones\/&lt;zone&gt;\/purge_cache<\/code> so Cloudflare stops serving the old copies. Nothing else about the site or its visitors is sent. Cloudflare: terms https:\/\/www.cloudflare.com\/terms\/, privacy policy https:\/\/www.cloudflare.com\/privacypolicy\/<\/p>\n<h4>Your own site (cache detection)<\/h4>\n<p>The Status tab&#8217;s <strong>Check now<\/strong> button, and a daily check, request a few of this site&#8217;s own pages as a visitor would, to read which caches answered. These requests go only to this site&#8217;s own address.<\/p>\n<h4>AI apps you connect (MCP sign-in)<\/h4>\n<p>Only when an AI app such as Claude or ChatGPT starts connecting to the site&#8217;s MCP server does the site fetch that app&#8217;s public OAuth client metadata from the address the app gives, for example <code>https:\/\/claude.ai\/oauth\/mcp-oauth-client-metadata<\/code> or <code>https:\/\/chatgpt.com\/oauth\/client.json<\/code>. No site content is sent.<\/p>\n<ul>\n<li>Claude: terms https:\/\/www.anthropic.com\/legal\/consumer-terms, privacy policy https:\/\/www.anthropic.com\/legal\/privacy<\/li>\n<li>ChatGPT: terms https:\/\/openai.com\/policies\/terms-of-use\/, privacy policy https:\/\/openai.com\/policies\/privacy-policy\/<\/li>\n<\/ul>\n<p>This plugin can connect your site to Zinn Digital\u00ae (the hosting platform it is built for) so that<br \/>\ncache purges can be mirrored to it and the Zinn\u00ae dashboard can show what changed on the site.<\/p>\n<p><strong>What is sent, and when<\/strong><\/p>\n<ul>\n<li><strong>Cache purges (only if <code>ZINN_CACHE_PANEL_URL<\/code> and <code>ZINN_CACHE_PANEL_SECRET<\/code> are defined).<\/strong><br \/>\nWhen content changes, the plugin posts the affected URLs and cache tags \u2014 no post content, no<br \/>\nvisitor data \u2014 to the address in <code>ZINN_CACHE_PANEL_URL<\/code>. The request is signed with an HMAC-SHA256<br \/>\nof the body using your site&#8217;s own secret. Note: the Zinn Digital\u00ae platform does not define<br \/>\n  ZINN_CACHE_PANEL_URL on the sites it hosts today, so on those sites nothing is sent.<\/li>\n<li>\n<p><strong>Outbound link index (only if <code>ZINN_SITE_LINKS_URL<\/code> and <code>ZINN_CACHE_PANEL_SECRET<\/code> are defined).<\/strong><br \/>\nWhen a post is saved or removed, and on a daily pass, the plugin sends that post&#8217;s <strong>title<\/strong>, its<br \/>\n<strong>permalink<\/strong>, and the <strong>links found in its content<\/strong> so link placements can be tracked from your<br \/>\nZinn\u00ae dashboard. This is post-derived data: titles and the URLs a post links to. The post body<br \/>\nitself is never sent, and no visitor data is included.<\/p>\n<\/li>\n<li>\n<p><strong>Hosting-customer Pro discount (only on sites Zinn Digital\u00ae hosts).<\/strong> The settings screen shows<br \/>\nadministrators a card offering hosting customers a personal discount code for Zinn\u00ae Cache Pro.<br \/>\nNothing is sent when the page loads. Only when an administrator presses the card&#8217;s button does the<br \/>\nsite send one request to Zinn Digital\u00ae at <code>https:\/\/api.zinndigital.com\/v1\/wp\/pro-discount\/&lt;site id&gt;<\/code>,<br \/>\ncontaining the plugin&#8217;s slug, the word <code>issue<\/code> and the administrator&#8217;s WordPress language, signed<br \/>\nwith the site&#8217;s own key. The site&#8217;s address and key come from constants the platform<br \/>\nwrites into wp-config.php on the sites it hosts; the card reuses only the host and site id of the<br \/>\naddress, which ends in <code>\/v1\/wp\/plugin-update\/&lt;site id&gt;<\/code>, and never sends anything to that address<br \/>\nitself. On any other site they do not exist and the card is never shown. The answer is the<br \/>\ncustomer&#8217;s code and a Freemius checkout link, to which the browser is then sent. The card is not<br \/>\nshown once Zinn\u00ae Cache Pro is active.<\/p>\n<\/li>\n<\/ul>\n<p><strong>When nothing is sent.<\/strong> The constants above are set by the Zinn\u00ae platform when it provisions<br \/>\na site \u2014 except <code>ZINN_CACHE_PANEL_URL<\/code>, which it does not set today. On a site that is not hosted with Zinn Digital\u00ae none of them exist, and the plugin makes <strong>no<br \/>\noutbound requests whatsoever<\/strong> unless you opt in to Freemius \u2014 caching, exclusions and the object cache all work locally.<\/p>\n<p>Service terms: https:\/\/zinndigital.com\/legal\/terms<br \/>\nPrivacy policy: https:\/\/zinndigital.com\/legal\/privacy<\/p>\n<ul>\n<li><strong>Support diagnostics (only when you press send).<\/strong> If you ask us for help, the plugin can send<br \/>\na support report to <code>https:\/\/api.zinndigital.com\/v1\/connector\/diagnostics<\/code>. <strong>You are shown the<br \/>\nexact payload first, already redacted, and nothing leaves your site until you press send.<\/strong><br \/>\nCredentials are excluded by declaration rather than by matching key names, and render as<br \/>\n  [not sent \u2014 credential]. The plugin never sends this on its own initiative.<\/li>\n<\/ul>\n<h3>Translations<\/h3>\n<p><strong>Every string this plugin adds to your admin is translated into 57 languages<\/strong> \u2014 labels, notices,<br \/>\nerrors and settings, not a subset. The catalogues are bundled in the plugin, so they work as soon<br \/>\nas you set your site language; there is no separate language pack to install.<\/p>\n<p>Every user-visible string is complete in every one of the 53 languages WordPress can serve<br \/>\ntoday:<\/p>\n<p>Amharic (am), Arabic (ar), Azerbaijani (az), Bulgarian (bg_BG), Bengali (Bangladesh)<br \/>\n(bn_BD), Czech (cs_CZ), German (de_DE), Greek (el), Spanish (Spain) (es_ES), Persian<br \/>\n(fa_IR), French (France) (fr_FR), Gujarati (gu), Hebrew (he_IL), Hindi (hi_IN), Croatian<br \/>\n(hr), Hungarian (hu_HU), Armenian (hy), Indonesian (id_ID), Italian (it_IT), Japanese<br \/>\n(ja), Georgian (ka_GE), Kazakh (kk), Khmer (km), Kannada (kn), Korean (ko_KR), Lao (lo),<br \/>\nMalayalam (ml_IN), Mongolian (mn), Marathi (mr), Malay (ms_MY), Myanmar (Burmese)<br \/>\n(my_MM), Nepali (ne_NP), Dutch (nl_NL), Panjabi (India) (pa_IN), Polish (pl_PL), Pashto<br \/>\n(ps), Portuguese (Brazil) (pt_BR), Romanian (ro_RO), Russian (ru_RU), Sinhala (si_LK),<br \/>\nAlbanian (sq), Serbian (sr_RS), Swahili (sw), Tamil (ta_IN), Telugu (te), Thai (th),<br \/>\nTagalog (tl), Turkish (tr_TR), Ukrainian (uk), Urdu (ur), Uzbek (uz_UZ), Vietnamese<br \/>\n(vi), Chinese (China) (zh_CN)<\/p>\n<p>A further 4 ship complete in the plugin \u2014 Hausa (ha), Somali (so_SO), Tajik (tg), Yoruba (yo) \u2014 but<br \/>\nWordPress core does not currently provide a locale for them, so WordPress cannot load them.<\/p>\n<p>The catalogues are bundled rather than left to translate.wordpress.org because that site can only<br \/>\noffer what volunteers have contributed, and a site administrator working in Amharic or Khmer would<br \/>\notherwise read English indefinitely. They do not compete with community translations: where a<br \/>\nWordPress language pack exists for this plugin, WordPress loads it ahead of the bundled catalogue,<br \/>\nso a community translation always wins.<\/p>\n<h4>Right-to-left<\/h4>\n<p>Arabic, Persian, Hebrew, Pashto and Urdu are right-to-left. Every screen this plugin adds was<br \/>\nrendered in a real WordPress install in each of those languages and checked, not assumed.<\/p>\n<h4>For translators<\/h4>\n<pre><code>languages\/ holds the `.pot` template plus a `.po`, `.mo` and `.l10n.php` for every language, so\n<\/code><\/pre>\n<p>corrections and new languages can be contributed directly.<\/p>\n<div class=\"plugin-editorial-note\" style=\"margin-top: 25px;padding: 12px 15px;background: #f8fafc;border-radius: 6px;color: #64748b;font-size: 13px;line-height: 1.5\">Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Page cache, Redis object cache and purging for nginx, Varnish, Apache, LiteSpeed and Cloudflare \u2014 updates refresh pages gradually, never all at once.<\/p>","protected":false},"author":1,"featured_media":11985,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[789,3178,2163,3179,3180,555],"class_list":["post-11984","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-cache","tag-nginx","tag-page-cache","tag-redis","tag-varnish","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11984","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11984"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11984\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/11985"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11984"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11984"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11984"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}