v0.2.13

Behavior

• Do not regenerate on cache flush
• Do regenerate when a published page/post is saved (queued, one at a time)

Update from Dashboard → Updates or Check for Updates.

v0.2.12

Fix: generation stampede / site stuck under load

Root cause

Cache-clear hooks (WP Rocket / Autoptimize) were force-regenerating up to 50 pages synchronously. Each success flushed all caches, which retriggered those hooks — a feedback loop that hammered WordPress and the VPS.

Changes

• Do not regenerate critical CSS on cache purge (it lives in post meta)
• Purge only the affected URL after generate (no full-site flush)
• Background queue: one generation at a time with a site-wide lock
• Publish/cron enqueue instead of blocking the request
• Rate limit always applies (default 5/hour/page); default delay 5s

Update the plugin, then optionally enable Disable Regular Intervals until the queue drains, and purge any stuck WP-Cron backlog if needed.

v0.2.11

Summary

• Stronger generation bypass (header + nocache) so regenerations stay stable
• Works with server update that ignores inlined styles and @font-face

Deploy the matching server update for smaller CSS and dashboard key copy/delete.

v0.2.10

Summary

• Stop critical CSS from compounding on regenerate (?ccss_bypass=1)
• Reject oversized CSS before storing (250KB cap)
• Rate-limit / request-delay / disable-cron settings

After updating

Clear or regenerate critical CSS on pages that already have multi-MB blobs (e.g. poisoned regenerations). Deploy the matching server update as well.

v0.2.9

Update plugin author to G Matta.

v0.2.8

Fix inline API: include 'url' field in payload (API requires it even for inline mode).

v0.2.7

Fix folder rename bug: WordPress no longer reverts our rename to versioned name.

v0.2.6

Add API response body logging to debug 400/500 errors during CSS generation.

v0.2.5

Restore folder rename filters. Plugin directory stays critical-css-wp/ after update.

0.2.4

Merge pull request #6 from gmatta01/dev

Bump version 0.2.2 → 0.2.4