v1.3.2

Fixed static site generation: now clears /static folder to avoid same-name caching

v1.3.1

Bugfix: Scheduled (WP-Cron) generation no longer fails Cloudflare Access authentication.

v1.3.0

Added

• Automatic generation & deployment scheduling. New "Automatic Generation & Deployment" section beneath the existing deploy buttons, powered by WP-Cron. You can now schedule generate, deploy, or generate-and-deploy to run automatically without manual clicks.
• Choose the action: Generate only, Deploy only, or Generate and deploy.
• Choose the schedule: run every N hours + M minutes, or daily at a specific time (using the WordPress site timezone).
• Toggle the schedule ON/OFF with a single button — toggling also saves the current settings. A separate "Save Schedule Settings" button persists changes without changing the on/off state.
• Status display shows whether scheduling is enabled, the next scheduled run time, and the last automatic run time with its result.
• Scheduled runs reuse your saved CF Access credentials, plugin JS selection, 404 settings, and Cloudflare Pages credentials. Scheduled deploys require "Remember Account ID and API Token" to be enabled.
• Cron events are automatically cleared on plugin deactivation.

Fixed

• Assets with query strings now download correctly. Asset URLs containing cache-busters (e.g. image.png?t=1779934563 or style.css?ver=6.4) previously failed because the query string was included in the destination filename, producing invalid/mismatched files. Query strings and fragments are now stripped before writing assets to disk.
• Stale assets and pages are no longer served from cache. All crawling and asset fetching now bypasses every cache layer (origin, Cloudflare edge, intermediate proxies). Each request sends no-cache directives, uses a fresh connection, and appends a unique per-run cache-busting token to the request URL. The token only affects the request — saved filenames remain clean — so every generation pulls the freshest content.

v1.2.0

Added generate + deploy 2-in-1 button, and prettier post-deploy log

v1.1.0

Fixed static site generation: instead of looking at the theme's 404 template and generating from there (thereby including admin header on top), users can now define an invalid page to crawl. The crawl result will be saved as the 404.html page. If left blank, crawls */example-page by default.

v1.0.0

Add files via upload