Changelog - WP Bunny Connector

Fixed Plugin settings (API key, pull zone) could be wiped during plugin updates, option imports, or multisite operations. Added a sanitize guard that aborts if the incoming data does not look like a real Settings form submission.

Security Added a pre_update_option filter as a second line of defence — if anything tries to overwrite a configured API key with an empty value, the write is silently blocked and the existing configuration is preserved.

Fixed Bunny edge cache now always purges when a cache plugin is updated, regardless of the "Plugin / theme updates" trigger setting. Previously the purge was skipped if that toggle was off.

New BerqWP — cache purge sync via berqwp_flush_all_cache and berqwp_purge_cdn (full purge) and berqwp_flush_page_cache (per-URL).

New SWIS Performance by EWWW Image Optimizer — cache purge sync via swis_complete_cache_cleared and swis_site_cache_cleared (full purge) and swis_cache_by_url_cleared (per-URL).

Internal Tested up to WordPress 7.0.1.

New Initial public release on WordPress.org.

New 74 Bunny.net pull zone edge rules across 9 categories: Core WordPress, HTML Caching, Ecommerce, Membership, LMS, Booking and Events, Static and Performance, Security Headers, and WAF / Trusted IPs.

New One-click deploy and redeploy via Bunny.net API. Rules are tracked by GUID and updated in place on redeploy, no duplicates created.

New Cache purge sync for 15 WordPress cache plugins including WP Rocket, LiteSpeed Cache, W3 Total Cache, FlyingPress, and more.

New Automatic bypass rule detection for 6 ecommerce platforms, 13 membership plugins, 9 LMS plugins, 4 booking and events plugins, 5 multilingual plugins, and 8 SEO plugins.

New Cache warmer with automatic sitemap detection across 8 supported SEO plugins and WordPress core sitemaps.

New Trusted IP / WAF whitelist support, auto-batched across up to 5 IPs or CIDRs per rule.

New Debug logging for purge trigger events, configurable in Settings.

Internal Plugin does not connect to any Nahnu Plugins server. All outbound connections go directly from the WordPress installation to the user's own Bunny.net API.