Everything is available from within XenForo (you do not need to go to Cloudflare for things) via the Cloudflare API. This allows you give admins permission to do certain things (for example block IP addresses within Cloudflare without giving them access to your Cloudflare account).
It simplifies/automates much of the configuration and usage of Cloudflare with XenForo.
- Manage all Cloudflare settings/options for your zone.
- Ability to purge Cloudflare cache...
Fixed issue where changed to Argo Tiered Cache setting wouldn't update via API.
- Fixed issue where generation of Cloudflare backup would try to use zone-level permissions for Access instead of account-level.
Fixed issue where changes to Argo Tiered Cache setting wouldn't update via API (for real this time).
- New option under Options -> External service providers -> Block IP addresses on spam clean from user approval queue (it's off by default, so you will need to enable it if you want to use it).
- Added additional info for cases where there's an exception making request to Cloudflare's API, but without an actual error received from the API.
- Compatibility with very old (end-of-lifed for years) versions of PHP
- Ability to use a Cloudflare Worker as a backend image proxy to hide the origin server's IP address when XenForo's image proxy fetches the image
- Some minor cosmetic tweaks to Cloudflare lists of things in admin area
The option to Force registration challenge added in version 1.1.1 has been extended to optionally apply to the contact form as well. If you already created the managed challenge for registrations you can click the option again to toggle on/off the contact form option (it will update the existing rule).
View attachment 27239
Using Cloudflare Workers as an image proxy was added in version 1.1.0. Now you can also use Cloudflare Workers as an unfurl proxy to further hide the...
- Removed stray variable in a tooltip
- Fixed issue where setting values considered "good" when disabled would show the opposite value for their setting (things like Development Mode and Rocket Loader which are considered "good" when disabled)
- Handling of Access policy creation when some admins have no email address.
- Better handling of favicons when using unfurl proxy and destination is using relative favicons.
- Give human-readable error when the domain/zone does not exist on Cloudflare account when trying to work with it.