Readme and listing text only \u2014 no code changed. Nothing to do.<\/p>","1.7.0":"
Adds AI assistant support: sixteen WordPress abilities so Claude, ChatGPT or any MCP client can check, diagnose and manage your cache without logging in. Same permissions as the settings screen. If you run the Pro add-on, update it to 1.7.0 at the same time.<\/p>","1.6.0":"
Rebuilt dashboard: a plain-English verdict, a dial showing how much of your site is ready, and a real measurement of how much faster cached pages are. If you run the Pro add-on, update it to 1.6.0 at the same time.<\/p>","1.5.1":"
Tidies up the section menu on the settings screen and adds an at-a-glance panel showing whether caching is on. Appearance only \u2014 nothing about caching changes.<\/p>","1.5.0":"
Adds a Support tab with plain-English fixes for the common problems and a one-line summary of your setup you can paste into a support request. Nothing about caching changes. If you run the Pro add-on, update it to 1.5.0 at the same time.<\/p>","1.3.0":"
Pro features have moved into a separate add-on plugin. If you have a license, download DadsFam Cache Pro from your account and install it alongside this one \u2014 your key and settings are kept and everything switches straight back on. This release also fixes several real caching bugs, including browsers holding on to stale pages after a purge.<\/p>","1.2.1":"
Security fix \u2014 removes an insecure wp-config backup from the web root. Update right away.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3676543,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3676543,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3676543,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3676543,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.4.1","1.5.1","1.6.0","1.7.0","1.7.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3676650,"resolution":"1","location":"assets","locale":"","width":1280,"height":1400},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3676650,"resolution":"2","location":"assets","locale":"","width":1280,"height":1213},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3676650,"resolution":"3","location":"assets","locale":"","width":1280,"height":1236},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3676650,"resolution":"4","location":"assets","locale":"","width":1280,"height":762},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3676650,"resolution":"5","location":"assets","locale":"","width":1280,"height":1119},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3676650,"resolution":"6","location":"assets","locale":"","width":1280,"height":1150},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3676612,"resolution":"7","location":"assets","locale":"","width":940,"height":652}},"screenshots":{"1":"Open it and you know where you stand. One plain sentence tells you whether your site is actually being served fast, a dial shows how much of it is saved and ready to go out instantly, and the measured difference sits underneath \u2014 your own home page built by WordPress versus served from cache, in milliseconds.","2":"Every setting in plain English. Each switch says what it does and when you would want it, not just what it is called.","3":"Exclusions: the pages that must never be saved. Carts, checkouts and logged-in visitors are handled for you already \u2014 add anything else that is personal to one visitor.","4":"Preloading: warm the cache yourself, so even the first visitor to a page gets a quick one.","5":"Tools: export and import your settings, reinstall the caching engine, and copy a debug summary for support.","6":"The Support tab: how to reach a real person, a one-line summary of your setup to paste into a message, and plain-English fixes for the four things people actually write in about.","7":"The rest of the DadsFam range, the guide sites and hosting, all in one place."}},"plugin_section":[],"plugin_tags":[146,144,3853,247,286],"plugin_category":[45,52,54],"plugin_contributors":[274194],"plugin_business_model":[],"class_list":["post-358483","plugin","type-plugin","status-publish","hentry","plugin_tags-cache","plugin_tags-caching","plugin_tags-page-cache","plugin_tags-performance","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-dadsfam","plugin_committers-dadsfam"],"banners":{"banner":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/banner-772x250.png?rev=3676543","banner_2x":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/banner-1544x500.png?rev=3676543","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/icon-128x128.png?rev=3676543","icon_2x":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/icon-256x256.png?rev=3676543","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-1.png?rev=3676650","caption":"Open it and you know where you stand. One plain sentence tells you whether your site is actually being served fast, a dial shows how much of it is saved and ready to go out instantly, and the measured difference sits underneath \u2014 your own home page built by WordPress versus served from cache, in milliseconds."},{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-2.png?rev=3676650","caption":"Every setting in plain English. Each switch says what it does and when you would want it, not just what it is called."},{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-3.png?rev=3676650","caption":"Exclusions: the pages that must never be saved. Carts, checkouts and logged-in visitors are handled for you already \u2014 add anything else that is personal to one visitor."},{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-4.png?rev=3676650","caption":"Preloading: warm the cache yourself, so even the first visitor to a page gets a quick one."},{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-5.png?rev=3676650","caption":"Tools: export and import your settings, reinstall the caching engine, and copy a debug summary for support."},{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-6.png?rev=3676650","caption":"The Support tab: how to reach a real person, a one-line summary of your setup to paste into a message, and plain-English fixes for the four things people actually write in about."},{"src":"https:\/\/ps.w.org\/dadsfam-cache\/assets\/screenshot-7.png?rev=3676612","caption":"The rest of the DadsFam range, the guide sites and hosting, all in one place."}],"raw_content":"\n
DadsFam Cache is a straightforward, no-nonsense performance plugin. It saves ready-made copies of your pages so repeat visitors skip PHP and the database entirely, and it ships with a one-click setup that applies safe, sensible defaults for you.<\/p>\n\n
It was built to be understandable by normal humans \u2014 every setting is written in plain English with a short explanation of what it actually does.<\/p>\n\n
The free plugin never phones home. There is no licensing code in it at all.<\/p>\n\n
DadsFam Cache Pro<\/strong> is a separate add-on plugin that installs alongside this one and adds its tabs to this same settings screen: minification, critical CSS, LCP and font optimisation, defer\/delay JavaScript, lazy-loading, WebP conversion, CDN rewriting, database cleanup, Heartbeat control and auto-preload. Grab it from https:\/\/www.dadsfam.co.za\/shop\/<\/p>\n\n This plugin is built to be extended. The add-on API:<\/p>\n\n Filters<\/strong><\/p>\n\n Actions<\/strong><\/p>\n\n Add-ons should boot on Also useful: add If you are on WordPress 6.9 or later and have an MCP plugin connected, this plugin tells your assistant what it can do. You can ask things like \"is caching actually working on my site?\", \"why is my change not showing up?\", \"how much faster is the cached version?\" or \"stop caching the members page\", and it will read the real state of your site and act on it.<\/p>\n\n Every action needs the same permission as the settings screen, so an assistant can never do more than you could. Reading is separated from changing, anything that edits a file or slows the site says so first, and removing the caching engine is not offered at all.<\/p>\n\n Right, let me be straight with you, because I hate being sold to as much as you do.<\/p>\n\n Everything above is free and it stays free. Caching your pages to disk, gzip, browser-cache rules, clearing the cache automatically when you change something, preloading and the one-click setup \u2014 none of those are premium features. Those are the things a cache plugin should just do, and if I put them behind a paywall I would be taking the mickey.<\/p>\n\n There is a PRO add-on. It exists because I am a dad in Cape Town, and this is one of the things that puts food on the table at my house. That is the honest reason. Not \"unlock your potential\", not \"supercharge your workflow\". Just: if this plugin made your site quicker and you can spare it, PRO helps me keep building.<\/p>\n\n What PRO adds is the heavier optimisation you reach for once the basics are in place \u2014 shrinking and combining your CSS and JavaScript, holding non-critical scripts back until they are needed, lazy-loading images, serving WebP, pushing static files to a CDN, and tidying up your database. That is extra speed and convenience. It is not the plugin working properly, because the plugin already works properly.<\/p>\n\n So if the free one does everything you need, brilliant. Genuinely. Use it, and I hope it takes a load off your server and your visitors' patience. If you get to the point where squeezing out the last few points would help, PRO is at plugins.dadsfam.co.za.<\/p>\n\n Either way, thanks for using something I built. \u2014 Zak, DadsFam<\/p>\n\n PRO adds:<\/p>\n\n Yes. The page cache works everywhere. Browser-cache rules are added to .htaccess only on Apache\/LiteSpeed; on NGINX the plugin gives you a snippet to paste into your server config.<\/p><\/dd>\n Yes. The cart, checkout and account pages are never cached, anyone holding a cart cookie always gets a live page, and shop\/product pages clear automatically when stock changes.<\/p><\/dd>\n From 1.3.0 the Pro features live in a separate add-on plugin, DadsFam Cache Pro. Download it from your account and install it alongside this one. Your license key and every one of your settings are still saved \u2014 Pro switches straight back on.<\/p><\/dd>\n Deactivate the other plugin first, then run One-Click Speed Setup. Running two page-cache plugins at once will cause problems.<\/p><\/dd>\n Turn the relevant feature (minify CSS, defer\/delay JS) back off, or add the problem file to its exclusion box. Then clear the cache.<\/p><\/dd>\n Yes \u2014 it adds No third-party services at all. The only HTTP requests it makes go to your own website: it visits your own pages to warm the cache (preloading), and it fetches one of your own URLs twice to run a quick self-test that confirms a page is being served from cache. Nothing is sent off-site, and no data leaves your server.<\/p><\/dd>\n\n<\/dl>\n\n\n The plugin is now free + Pro as two separate plugins.<\/strong> This one is the free page cache and never phones home. Pro features moved to the DadsFam Cache Pro add-on, which installs alongside it and adds its tabs to the same settings screen. Your settings and license key are untouched by the update \u2014 install Pro and everything switches back on exactly as it was.<\/p>\n\n Fixes and improvements in this release:<\/p>\n\nFor developers<\/h4>\n\n
\n
dadsfam_cache_is_pro<\/code> \u2014 answer true to unlock Pro-flagged fields<\/li>\ndadsfam_cache_has_addon<\/code> \u2014 answer true if an add-on is present<\/li>\ndadsfam_cache_page_html<\/code> ( $html, $context ) \u2014 transform a page before it is cached<\/li>\ndadsfam_cache_settings_defaults<\/code> ( $defaults ) \u2014 register extra settings<\/li>\ndadsfam_cache_sanitize_settings<\/code> ( $clean, $raw ) \u2014 sanitize them on save<\/li>\ndadsfam_cache_admin_tabs<\/code> ( $tabs ) \u2014 register settings panels<\/li>\ndadsfam_cache_ajax_tasks<\/code> ( $tasks ) \u2014 register AJAX handlers (cap + nonce checked for you)<\/li>\ndadsfam_cache_admin_localize<\/code> ( $data ) \u2014 add data for the admin JS<\/li>\ndadsfam_cache_htaccess_rules_before<\/code> \/ dadsfam_cache_htaccess_rules<\/code> \/ dadsfam_cache_nginx_snippet<\/code><\/li>\ndadsfam_cache_speed_setup<\/code> ( array( $settings, $notes ) ) \u2014 contribute to One-Click Speed Setup<\/li>\ndadsfam_cache_cache_this_request<\/code> ( bool ) \u2014 veto caching for the current request<\/li>\ndadsfam_cache_purge_post_paths<\/code> ( $paths, $post_id ) \u2014 extra paths to clear<\/li>\ndadsfam_cache_preload_urls<\/code> ( $urls ), dadsfam_cache_auto_preload<\/code> ( bool )<\/li>\ndadsfam_cache_footer_comment<\/code> ( $comment ) \u2014 return '' to leave cached pages unmarked<\/li>\ndadsfam_cache_debug_info<\/code> ( $rows ) \u2014 add rows to the support panel<\/li>\n<\/ul>\n\n\n
dadsfam_cache_loaded<\/code> ( $version ) \u2014 the plugin is wired and safe to extend<\/li>\ndadsfam_cache_purged_all<\/code>, dadsfam_cache_purged_everything<\/code>, dadsfam_cache_purged_post<\/code> ( $post_id, $paths )<\/li>\ndadsfam_cache_settings_saved<\/code> ( $settings ), dadsfam_cache_deactivated<\/code><\/li>\ndadsfam_cache_preload_settings<\/code> \u2014 print extra fields on the Preload tab<\/li>\n<\/ul>\n\nplugins_loaded<\/code> at priority 20 or later. WordPress sorts active plugins alphabetically, so an add-on's file may well be included<\/em> before this one's \u2014 never touch a DadsFam_Cache_<\/code> class at include time.<\/p>\n\ndata-no-optimize<\/code> to any script or stylesheet tag to have Pro leave it alone, data-no-lazy<\/code> on an image to keep it eager, and define( 'DONOTCACHEPAGE', true );<\/code> to skip caching a request.<\/p>\n\nWorks with AI assistants<\/h4>\n\n
A word about PRO<\/h4>\n\n
\n
\n
\n
Will it work on NGINX?<\/h3><\/dt>\n
Does it work with WooCommerce?<\/h3><\/dt>\n
I was on 1.2.x with a license and my Pro features disappeared.<\/h3><\/dt>\n
It says another caching plugin is active. What now?<\/h3><\/dt>\n
Something looks wrong after a Pro feature.<\/h3><\/dt>\n
Does it edit my wp-config.php?<\/h3><\/dt>\n
define( 'WP_CACHE', true );<\/code>, which WordPress requires for page caching to work at all. The line is marked with our name, written atomically, and removed cleanly when you deactivate.<\/p><\/dd>\nDoes this plugin contact any external services?<\/h3><\/dt>\n
1.7.1<\/h4>\n\n
\n
1.7.0<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
1.5.1<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
dadsfam_cache<\/code> name instead of the old short dfc<\/code> one, so it cannot collide with another plugin or theme on your site.<\/li>\ndfc_settings_saved<\/code> is now dadsfam_cache_settings_saved<\/code>), so DadsFam Cache Pro must be updated to 1.4.0 at the same time. If one is updated without the other, Pro simply shows a notice instead of loading \u2014 nothing breaks.<\/li>\n1.3.0<\/h4>\n\n
\n
Cache-Control: public, max-age=0, must-revalidate<\/code>. Without it browsers guessed a freshness lifetime from Last-Modified, so a returning visitor could sit on a stale page for hours after you cleared the cache.<\/li>\nzlib.output_compression<\/code> is on. PHP rewrites the body in that case, so the length described the wrong thing and browsers truncated the page.<\/li>\nVary: User-Agent<\/code> is now sent when the separate mobile cache is on. Without it a proxy in front of the site could hand the desktop page to a phone.<\/li>\nmax-age<\/code> explicitly. The old Header set Cache-Control \"public, immutable\"<\/code> overwrote the max-age that mod_expires had just set, leaving assets with no freshness lifetime at all \u2014 the opposite of what browser caching is for.<\/li>\nimmutable<\/code> is no longer applied to images. They carry no ?ver=<\/code> cache-buster, so re-uploading a photo under the same filename was invisible to returning visitors for six months.<\/li>\n[<\/code>, ]<\/code>, *<\/code> or ?<\/code>. The old code used glob(), which silently matched nothing for those slugs.<\/li>\ndadsfam_cache_footer_comment<\/code> filter, and the signature comment no longer advertises the plugin version.<\/li>\n1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n