Consolidated buttons for new firewall rules into a menu
Consolidated buttons for new cache rules into a menu
Stop click propagation when clicking on link to Cloudflare in stats block header (prevents block from hiding/showing when you are just trying to go to Cloudflare dashboard)
Viewing statistics block on main admin page requires admin permission viewAnalytics (not the permission for managing cloudflare) and block is hidden if the user doesn't have the necessary permission
Added check to avoid division by zero errors in a case where Cloudflare reports an impossible scenario (cached traffic for a time period, but total traffic for that same time period is 0)
New option: Show Cloudflare statistics
Added DMARC management section. Ability to monitor emails being sent by third parties (includes week/month chart as well as table of unapproved sources sending emails)
Fixed some text not being phrased in the stats block
Selecting Global API keys are disabled (can't setup new ones going forward). Includes deprecation notice (going away completely in the future, so migrate to API tokens if you are still using Global API keys!).
Unify primary classes so they can be shared without changes with WordPress version of this addon
If you don't already have a Cloudflare API token, the link to create one will pre-define the required permissions for you (way less annoying for new users)
Updated deep links inside cloudflare.com for Firewall events to reflect the new endpoint
Look back 7 days instead of 1 day to find account-level usage records for buckets
unfurl and image proxy Workers will use default language for site when they are setup
Changed URL where you set Worker subdomain and made it a property for easier changes in the future (Cloudflare changed it in their dashboard)
Make external URL include protocol (https rather than relative URLs (R2 subdomains always have valid SSL certificates, so no reason to serve up content insecurely even if the site isn't using HTTPS)
Automatic retry (once) if API/R2 calls return HTTP 499 response (same way we handle server-side [5xx errors])
Change verbiage on R2 operation log to be more clear about billable events
Don't hardcode dash.cloudflare.com prefix in admin:cloudflare_r2 template
Fix Zero round trip phrase being title case
Add direct link for setup of Zero Trust Access authentication method
Added new pre-set Cache Rule option to force caching of static content
When checking if a file exists on R2, only fall back to checking if it's a "directory" if there's no file extension in the path (less class A operations)
Fix for change to Crawler Hint API calls (needed to change Crawler Hints setting)
Updated parameters for Network error logging when doing "Easy config"
Normalize path when getting a list of multiple objects
Add support for getting listings of directories inside buckets in R2 adapter (a little tricky because R2 it not a file system in the traditional sense as there are no actual directories). Should make it so exporting styles with attached assets should work if those assets are stored in R2.
Hate pushing quick versions out (sorry)... but a necessary fix for media uploads which are handled slightly differently than other uploaded content (like avatars and attachments).
Don't assume R2 bucket still exists when getting usage stats for buckets (in case someone deleted the bucket they are currently using)
Fixed issue when trying to configure R2 for the first time, but Cloudflare account does not have R2 enabled yet
Added sanity check for external data URL option in case addon somehow got partially (but not fully) installed
If using guest page caching and purge cache API call fails when a new post is created, edited or deleted, fail silently
Automatically remove cached account ID if it's invalid (Cloudflare account changed for site)
Don't assume template method is callable (fixes issue where XenForo addon installation process would give a temporary error when template modifications were enabled but class extensions are not yet)
![[DigitalPoint] App for Cloudflare](/data/resource_icons/13/13174.jpg?1684217144){kind=icon}
rather than relative URLs (R2 subdomains always have valid SSL certificates, so no reason to serve up content insecurely even if the site isn't using HTTPS)
