Static Publisher 1.0.25 – Site-wide change detection and safe page-cache purging

Highlights

Static Publisher 1.0.25 adds configurable site-wide change detection and a safe, cache-provider-independent page-cache purge workflow.

These additions allow incremental publishing to detect changes outside normal WordPress posts and pages, while ensuring delegated crawls do not accidentally export stale cached HTML.

Site-wide change detection

• Add configurable WordPress option dependencies to the global change-token signature.
• Add configurable, stable WordPress action hooks that invalidate all page tokens when site-wide content changes.
• Add a guarded manual action for invalidating all page change tokens.
• Hash watched option values and custom dependency payloads inside WordPress.
• Never expose raw watched option values through the token API or crawl logs.
• Reject frequently executed request-lifecycle hooks that could continuously invalidate incremental exports.
• Document how site-specific systems such as Code Snippets, global theme CSS, and other configuration providers can participate without adding vendor-specific logic to Static Publisher.

Page-cache integration

• Add an authenticated endpoint for purging the source site's page cache before crawl discovery.
• Keep Static Publisher independent of WP Super Cache, Cache Enabler, Redis, hosting-provider caches, and other concrete cache implementations.
• Introduce the versioned smartcloud_static_publisher_purge_page_cache_v1 provider contract for server-side adapters.
• Require a configured provider to explicitly confirm a complete purge.
• Stop the crawl before changing export output if cache purging is enabled but unavailable or unsuccessful.
• Leave existing installations unchanged when page-cache purging is disabled.
• Do not pre-warm the cache: the crawl naturally repopulates pages as they are requested.

Administration and documentation

• Add admin controls for watched WordPress options and action hooks.
• Add a dedicated “Purge page cache before crawl” setting.
• Add a confirmation-protected manual all-page invalidation action.
• Extend the documentation sidebar and developer guide with dependency, privacy, adapter, job-coverage, and cache-miss guidance.

Requirements

Page-cache purging requires @smart-cloud/publisher-exporter 1.1.74 or newer on the external queue runner.

A compatible server-side adapter must implement the generic purge-provider contract before the purge setting is enabled. Static Publisher does not bundle or require a specific page-cache plugin.

No exporter upgrade is required while page-cache purging remains disabled.

Upgrade notes

1. Install @smart-cloud/publisher-exporter 1.1.74 and restart the external queue runner.
2. Install and verify a compatible page-cache adapter.
3. Confirm that anonymous source requests produce a valid cache MISS-to-HIT sequence without caching authentication redirects or logged-in HTML.
4. Enable “Purge page cache before crawl” only after that verification.

The first incremental crawl after upgrading may render all supported pages once because the global token schema now includes the site revision and configured dependency hashes.