← All changes | readme.txt +41 -68 1.3.1 → 1.3.4 View file →

		@@ -3,9 +3,9 @@
3	3	Tags: cache, performance, page speed, optimization, mcp
4	4	Requires at least: 6.0
5	5	Tested up to: 7.1
6	6	Requires PHP: 7.4
7		-Stable tag: 1.3.1
	7	+Stable tag: 1.3.4
8	8	License: GPLv2 or later
9	9	License URI: https://www.gnu.org/licenses/gpl-2.0.html
10	10
11	11	A complete WordPress caching plugin: page cache, object cache, CDN, database cleanup and Core Web Vitals optimization, plus a built-in MCP server.
		@@ -171,9 +171,9 @@
171	171	= Private By Default =
172	172
173	173	xSpeed Cache never collects personal data, stores IP addresses or uses tracking cookies. Every optimization runs locally on your server. By default it makes no calls to any third-party server. The only request is a quick check to your own site's home URL to confirm GZIP is active, rate-limited to once per hour.
174	174
175		-xSpeed Cache also includes **optional usage analytics**. The setup wizard shows a clearly labeled consent control for it (enabled by default, untick to opt out), and nothing is sent until you confirm your choices in the wizard. When enabled, xSpeed Cache shares anonymous, non-sensitive diagnostics: your WordPress and PHP version, active theme and plugins, server type, site language, and which xSpeed Cache features you have switched on, so we know what to keep fast and compatible. No personal data and no page content are ever sent, and you can turn it off again at any time from your dashboard. See the External services section below.
	175	+xSpeed Cache also includes **optional usage analytics**. You are asked in two places, both off by default: a clearly labeled consent control in the setup wizard, and the switch in xSpeed Cache → Settings → Privacy & usage data. Nothing is sent unless you opt in from one of them. When enabled, xSpeed Cache shares anonymous, non-sensitive diagnostics: your WordPress and PHP version, active theme and plugins, server type, site language, and which xSpeed Cache features you have switched on, so we know what to keep fast and compatible. No personal data and no page content are ever sent, and you can turn it off again at any time from xSpeed Cache → Settings → Privacy & usage data. See the External services section below.
176	176
177	177	= Backed By a Team You Trust =
178	178
179	179	xSpeed Cache is developed by the trusted team at WPDeveloper, a leading WordPress marketplace used and loved by millions of users.
		@@ -263,9 +263,9 @@
263	263	8. Migration — import settings from WP Rocket, W3 Total Cache, WP Super Cache, or LiteSpeed Cache.
264	264
265	265	== External services ==
266	266
267		-xSpeed Cache contacts your own site (the gzip probe below); when usage analytics is enabled, an analytics service; only if you choose to submit the optional deactivation survey, that same service; and — only when you run a speed test yourself — one external performance-score provider. The setup wizard shows a clearly-labeled consent control for analytics (enabled by default, untick to opt out), and nothing is sent until you confirm your choices there. The deactivation survey is separate and never sends anything unless you explicitly click Submit. External scores are off by default, turn on the first time you press Test, and never run on their own.
	267	+xSpeed Cache contacts your own site (the gzip probe below); when usage analytics is enabled, an analytics service; only if you choose to submit the optional deactivation survey, that same service; and — only when you run a speed test yourself — one external performance-score provider. Analytics consent is asked in two places, both off by default — a clearly-labeled control in the setup wizard, and the switch in xSpeed Cache → Settings → Privacy & usage data — and nothing is sent unless you opt in from one of them; turning the switch off stops all collection and clears the scheduled send. The deactivation survey is separate and never sends anything unless you explicitly click Submit. External scores are off by default, turn on the first time you press Test, and never run on their own.
268	268
269	269	= Self-hosted gzip probe =
270	270
271	271	* **What it does:** Issues a single `GET` request to your site's home URL (`home_url('/')`) with an `Accept-Encoding: gzip` header to detect whether your web server is already serving gzipped responses. The response body is discarded; only the `Content-Encoding` header is read.
		@@ -306,90 +306,63 @@
306	306	* License: ISC
307	307
308	308	== Changelog ==
309	309
310		-= [1.3.1] – 2026-09-14 =
	310	+= [1.3.4] – 2026-09-20 =
311	311
312		-**Purge all now says what it actually cleared, on the button and in the toast, instead of claiming success when a store refused. Pro features are marked with one lock everywhere rather than amber squares and crowns, which also lifts the dimmed labels back to readable contrast. The Cloudflare panel is staged by connection state, so setup comes before the actions that depend on it — and the auto-purge switch is visible while disconnected instead of hidden.**
	312	+**Consent-manager scripts marked late are now always left alone, below-fold sections skip rendering work until they are needed, and xSpeed's MCP server shares a site cleanly with other MCP plugins.**
313	313
	314	+Optimization:
	315	+- New: Below-fold sections are rendered lazily with content-visibility: auto, so the browser skips their layout and paint work until they scroll into view.
	316	+- New: Block-editor stylesheets are stripped from anonymous frontend pages that do not use any blocks.
	317	+- Fixed: Scripts that another plugin marks data-no-optimize or data-no-minify late — as consent managers such as Borlabs Cookie do — are restored to their original URL and left alone by minify, defer and delay, however late the marker is stamped.
	318	+
	319	+AI / MCP:
	320	+- Improved: The AI & agents screen now leads with the MCP server and says what each of its tools does, with descriptions shown in full.
	321	+- Improved: An assistant already connected over OAuth may ask for approval once more after updating — nothing needs re-entering, and read-only connections stay read-only.
	322	+- Fixed: An AI assistant can now connect to xSpeed and to another MCP plugin on the same site. xSpeed's OAuth details moved to an address of their own under /xspeed/mcp, and the site-wide address is handed over as soon as another plugin asks for it — where nothing else wants it, xSpeed keeps answering there.
	323	+
314	324	Dashboard & Admin UX:
315		-- New: Purge all reports its outcome — Cleared, Already empty, Partly cleared or Purge failed — and the toast names the files and size cleared plus any other store, or the reason a store refused.
316		-- Fixed: Pro features are marked with a single lock in the teal tint. Locked tabs are no longer dimmed to 70%, which had dropped their labels below readable contrast, and the amber squares, crowns and sparkles are gone from the tabs, badges and the sidebar tier slot.
317		-- Fixed: Turning caching on no longer flashes "Another plugin owns the page cache on this site" while the toggle is in flight. A genuine foreign drop-in still shows the banner.
318		-- Fixed: The Purge all button keeps its natural width at rest instead of reserving room for the outcome label.
	325	+- Fixed: Buttons can carry a border and always show keyboard focus, and the Cloudflare Dev-mode controls use proper button styling.
319	326
320		-Cloudflare:
321		-- New: The panel is staged by connection state — Connection, then Actions — so credentials and Verify come before the buttons that need them, and an action that cannot work is disabled with a hint rather than failing silently.
322		-- Fixed: The auto-purge-on-purge switch is always visible, dimmed while disconnected, instead of being hidden until connected. Hiding it is how the edge-sync switch went unnoticed.
	327	+= [1.3.3] – 2026-09-16 =
323	328
324		-Documentation:
325		-- Fixed: The full changelog moved to changelog.txt, shipped with the plugin and linked from the plugin page. wordpress.org truncates a changelog over 5,000 words on import, so the history past the cut had been dropped.
	329	+**Consent gets a dashboard home, the cache engine learns to leave non-HTML alone, and uncacheable pages now tell the CDN so.**
326	330
327		-= [1.3.0] – 2026-09-13 =
	331	+Privacy & Analytics:
	332	+- New: A "Privacy & usage data" panel to view and withdraw usage-analytics consent any time, with a matching wp xspeed privacy command.
	333	+- Improved: The setup wizard's analytics consent now defaults to off and is only ever an explicit opt-in.
328	334
329		-**A single page can now be purged straight from the admin bar, the post list or the editor, and known third-party scripts — analytics, chat widgets, tracking pixels — are delayed automatically without asking you to list them. A host or agency can pin any setting from wp-config.php with a constant: the dashboard shows the pin, names the constant, and lets an admin take the setting back. xSpeed can also take over an abandoned page-cache drop-in, with your consent, instead of being blocked by it forever.**
	335	+Caching:
	336	+- Fixed: WordPress's virtual robots.txt (and favicon) is no longer cached or minified, so every directive and newline reaches crawlers intact.
	337	+- Improved: /robots.txt joined the default cache exclusions, and the sitemap pattern now matches sitemaps.xml too — existing installs keep their working exclusion through the rename.
330	338
331		-Caching:
332		-- New: Purge a single page from the admin bar, the post list's row actions, or the editor — and the purge confirms what it actually removed instead of assuming.
333		-- New: `wp xspeed purge` clears every cache in one call, and a purge is scoped to exactly what the caller asked for.
334		-- New: Publishing or updating a post also purges the pages that list it, not just the post itself.
335		-- New: An abandoned page-cache drop-in left by another plugin can be taken over with one consenting click, and a leftover husk of a drop-in no longer blocks caching forever.
336		-- Fixed: A migration handover now completes instead of stopping halfway, from the dashboard and the CLI alike.
337		-- Fixed: xSpeed no longer mistakes itself for a competing cache plugin.
	339	+Cloudflare & CDN:
	340	+- New: A page xSpeed refuses to cache now sends no-store edge headers, so a CDN never freezes a half-optimized or excluded page.
	341	+- Fixed: The deferred Cloudflare purge batch is bounded, cleared on deactivation, and says so when a purge is refused.
338	342
339	343	Optimization:
340		-- New: Known third-party scripts are delayed until interaction automatically, including the inline install snippets vendors ask you to paste into the header.
341		-- New: Font stylesheets are deferred out of the render path, and a Google Fonts request that blocks rendering is rewritten to swap.
342		-- New: A manual preload list covers the images no detector can see.
343		-- Fixed: The LCP preload no longer picks a brand logo over the page's real hero image.
344		-- Fixed: Deferring no longer breaks inline scripts that depend on another handle, combining no longer swallows scripts that delaying protects, and handle exclusions are honoured in the delay pass.
345		-- Fixed: Valid minified JavaScript is no longer rejected, asset URLs are matched across schemes, an uploads folder at the domain root is recognised, and `?ver` is kept on files plugins rewrite in place.
346		-- Fixed: Lazy loading reads an image's size from whichever attribute holds its URL, and no longer mistakes a real image for a placeholder because of a word inside its filename.
	344	+- Fixed: Scripts marked data-no-optimize or data-no-minify are left completely alone by minify, defer and delay — consent-manager configurations always ship current.
	345	+- Fixed: xSpeed's own scripts are never deferred or delayed by its own optimizer.
	346	+- Fixed: The Conservative preset now switches LCP preload and preconnect off, matching its "page cache + GZIP only" promise.
347	347
348		-Settings:
349		-- New: Any module setting can be pinned from wp-config.php with a constant. The dashboard shows a pinned field as read-only and names the constant that holds it.
350		-- New: An admin can take a pinned setting back — the override displaces the host's constant and only that.
351		-- Fixed: A panel containing a pinned field saves again, and editing a pinned setting is a single inline edit.
	348	+Dashboard & Admin UX:
	349	+- Improved: Preload now reports what actually happened — how many pages are warming, and the server's reason when a crawl cannot start.
352	350
353		-Object Cache:
354		-- New: Redis credentials and Memcached servers are read from wp-config.php, and `WP_REDIS_PREFIX` is honoured as a key salt.
355		-- Fixed: Cache keys are always namespaced per site, so two sites sharing a Redis or Memcached database can no longer read or purge each other's entries.
356		-- Fixed: The dashboard panel gained every fix that had only reached the CLI, owns only what the plugin itself wrote, and no longer presents another plugin's object cache as xSpeed's.
357		-
358	351	Reliability:
359		-- Fixed: Translations now load for both PHP and the dashboard, and the settings screens are translatable.
360		-- Fixed: nginx sends one Cache-Control header per location instead of two, and the de-duplicated header no longer caches 404 responses.
361		-- Fixed: An audit contributor that throws no longer takes the whole audit down with it, and add-ons can report findings of their own.
	352	+- Improved: Uninstall now removes all usage-tracking state, the scheduled send, and every leftover option row.
362	353
363		-AI tools:
364		-- Improved: The optimize assistant honours its cooldown, never measures without consent, keeps the score through a run of failures, and reports the newest score with its age.
	354	+= [1.3.2] – 2026-09-15 =
365	355
366		-= [1.2.4] – 2026-09-06 =
	356	+**Purging is now a contract other caches can join: clearing xSpeed's page cache also invalidates LiteSpeed Cache and the host's nginx FastCGI cache, and every purge is scoped to exactly the site and pages it was asked for — including on multisite.**
367	357
368		-**The Overview now reports what is actually switched on, counted from the server rather than guessed from the payload, and a new xSpeed Scan grades the site from inside the plugin. Pages carrying a security token can use the fast static path again instead of silently falling back, and nginx users can now fetch their server config from the command line.**
369		-
370		-Dashboard & Admin UX:
371		-- New: The master cache switch now sits in the top bar, reachable from every screen.
372		-- New: The sidebar collapses to a rail, and adapts on smaller screens.
373		-- New: An (i) beside a module's pill explains why it is reported as on, where the rule is not obvious.
374		-- Fixed: The Overview counts the features that are genuinely on. It previously counted entries in the payload, including ones that never rendered, so the number disagreed with the screen.
375		-- Fixed: On/off state refreshes after a save, so counts update without reloading the page.
376		-- Fixed: Collapsing the rail no longer shifts the content beside it, and rows keep their size.
377		-- Fixed: The collapsed rail shows real tooltips rather than the browser's own, and the drawer is now reachable by keyboard.
378		-
379	358	Caching:
380		-- Fixed: A page carrying a security token can use the fast static path again, expiring on the token's clock instead of being refused outright.
381		-- Fixed: A refusal that silently disabled static serving is now surfaced rather than left to guess at.
382		-- Improved: The cache signature records when it was generated.
	359	+- New: A purge-event contract lets other caching layers invalidate together with xSpeed, so a purge clears every cache that matters in one action.
	360	+- New: Purge All is forwarded to LiteSpeed Cache and the host's nginx FastCGI cache when they are present.
	361	+- Fixed: One post change triggers exactly one invalidation, deleting a media file purges again, and a purge still finds its post when the hook hands over none.
	362	+- Fixed: Purges are scoped per site on multisite — a purge no longer sends another site's URLs to this site's server cache, a default port is not treated as a different site, and full purges stay on the current site.
	363	+- Fixed: A purge listener that throws no longer aborts the purge, a query string of "0" is still treated as a query, and a partial purge reports itself as partial instead of claiming success.
383	364
384		-Speed Test & Scan:
385		-- New: An xSpeed Scan runs from inside the plugin and grades the site, with a score ring on the Overview.
386		-- Improved: The Speed Test page reports both Lighthouse scores, organised into tabs.
387		-- Fixed: A scan claims its slot atomically, so two runs cannot collide, and the card recovers when a poll fails.
388		-
389	365	Optimization:
390		-- Fixed: A CSS background hero is now preloaded as an LCP candidate.
391		-
392		-nginx:
393		-- New: `wp xspeed cache nginx-config` prints the server-block config, so an installer or provisioning script can fetch it without the dashboard. It assumes nginx on a site no request has reached yet, and `--server=` states the answer outright.
	366	+- Fixed: Delaying JavaScript no longer breaks inline scripts bound to a delayed handle, and replayed external scripts keep their original load order.
394	367
395	368	Older releases are listed in changelog.txt, included with the plugin, and at [xspeedcache.com/changelog](https://xspeedcache.com/changelog/).