POM Cache
Changelog
Changelog
All notable changes to POM Cache are documented in this file.
Changes pending release tag
- feat: Added targeted post-change HTML invalidation for the edited single across configured POM Translate languages while preserving the existing defaults and site-wide behavior.
- perf: Avoided rewriting the country-pricing web-server safety sentinel on every unchanged WordPress request.
- fix: Prevented WP-CLI, cron, administration, REST, and authenticated requests from promoting the persisted country-pricing cache gate without observing the public proxy path.
- fix: Kept shared HTML fail-closed while legacy country-pricing plugins are active and across explicit POM country-pricing rollout transitions.
- feat: Added a persisted early country-pricing safety gate and a web-server sentinel for universal shared WooCommerce HTML.
- perf: Enabled one neutral product-page cache entry across country zones when the complete integration gate is safe.
- fix: Excluded REST, Store API, Faceted Search, country-price resolution, Composite, and AJAX commerce traffic from static HTML delivery.
- fix: Added conservative site-wide invalidation for country-zone configuration, regional product prices, compatibility options, plugin state, and theme changes.
- docs: Documented universal country-pricing eligibility, dynamic route exclusions, Apache rules, and origin and CDN invalidation.
- feat: Add a request-scoped WP-CLI diagnostic that reports exact static HTML eligibility and filesystem write outcomes without requiring WordPress debug mode.
- docs: Document anonymous cache generation tracing, direct-origin requests, result interpretation, and security boundaries.
- build: Synchronize the recursive POM Knowledge Markdown tree to
wp-content/docs/pom-knowledgeduring local release builds while excluding hidden and non-Markdown files. - build: Update POM Framework so managed file reads are cached per request and OPcache remains an optional acceleration layer.
- docs: Add the documentation manifest that defines article order for POM Docs Sync.
- docs: Give every POM Cache documentation directory and article a globally unique product-scoped name and update all internal links.
- docs: Enforce numbered documentation topics with no root Markdown files and complete index pages for every topic directory.
- docs: Complete a cross-chapter review of the POM Cache manual, correcting first-hit verification, single-site guidance, navigation, CDN examples, and orphaned documentation assets.
- docs: Rewrite the tools, developer reference, and help chapters as distinct code-verified guides to diagnostics, public extension APIs, and safe troubleshooting.
- docs: Rewrite the progressive JSON and invalidation chapters as distinct runtime-verified guides to generation, layered delivery, freshness, clearing scope, multisite isolation, and CDN coordination.
- docs: Rewrite the Apache, WebP, compression, and CDN chapters as distinct guides with verified origin, edge, negotiation, and invalidation boundaries.
- docs: Rewrite the caching concepts and static HTML chapters as distinct, runtime-verified guides to request safety, generation, delivery, isolation, and diagnostics.
- docs: Rewrite the getting-started chapter as distinct, code-verified installation, licensing, interface, validation, and maintenance guides.
- docs: Add complete reader-focused cache documentation under numbered POM Docs Sync terms.
- docs: Clarify that public documentation must be reader-focused and exclude internal operational material.
- docs: Standardize numbered screenshot placeholders for public Markdown documentation.
- Changes included in version 1.0.2.
Internal
- Published a maintenance release to verify private update detection on WordPress multisite.
- Changes included in version 1.0.1.
New features
- Added the network-aware missing/invalid license admin notice and subscription cost info on the License tab.
- Added the License tab to the existing settings page (Settings > POM Cache > License); license checks are admin-only and never run in advanced-cache.php, cache delivery, writes, or invalidation paths.
Fixed
- Clarified that POM Cache uses a renewable zero-price subscription while retaining checkout, license, domain, and private-update enforcement.
- Added the signed v2 local fallback updater and an always-visible multisite subsite message explaining the main-site requirements for automatic updates.
Documentation
- Required complete production-facing documentation maintenance and the canonical access-denying
.htaccessin repository agent guidance. - Replaced unauthenticated v1 release verification with a signed v2 license, domain, one-time token, and SHA-256 package check.
- Standardized pending and historical release notes under the current categorized changelog format.
- Updated the release procedure to require dated changelog headings.
Build
- Centralized plugin documentation under
wp-content/docs/pom-cacheduring local release builds and excluded thedocstree from ZIP artifacts. - Sourced manifest release notes from versioned changelog sections and rejected invalid changelog structures during builds.
- Accepted mandatory ISO release dates in versioned changelog headings when generating manifests.
Internal
- Standardized incremental changelog maintenance and required
CHANGELOG.mdin release packages.
- Changes included in version 1.0.
Internal
- Established the existing release baseline before adoption of the incremental changelog workflow.
The entries below reconstruct unversioned or previously undocumented development before this repository adopted incremental release notes. Each active month consolidates its non-merge Git commits; merge-only, version-number-only, and internal tracking-only commits are omitted.
2026-06
New features
- Releases: added private release pipeline.
Security
- Security: POM Framework - Harden settings AJAX and dependency toolchain.
Changed
- Framework: POM Framework - Rename Pomatio Framework.
- Testing: removed test infrastructure.
2026-05
New features
- Cache: new plugin, initial commit.
- Cache: improved htaccess rules and added AGENTS.md file.
- Progressive archives: POM Theme and POM Cache - Add progressive JSON archive rendering.
Fixed
- Progressive Json: POM Theme and POM Cache - Harden archive JSON rollout.
- Progressive archives: POM Theme/POM Cache - Serve batched REST JSON payloads.
- Cache: made automatic purges opt-in.
- Progressive archives: POM Theme and POM Cache - Align progressive JSON rendering.
- Pom Cache: show delete cache admin bar button on mobile.
Documentation
- Updated AGENTS.md file.