[DigitalPoint] App for Cloudflare®

[DigitalPoint] App for Cloudflare® 1.9.1.1

No permission to download
Overview FAQ Updates (63) Reviews (22) History Discussion
digitalpoint said:
Is it when trying to change a specific setting, or is it anything? Also, are you on a free or paid plan for the zone?
Click to expand...

Seems to be any setting. I tried changing "Always use HTTPS", "Minimum TLS Version", and the "Brotli" settings and they all do the same thing.
 
digitalpoint said:
Is it when trying to change a specific setting, or is it anything? Also, are you on a free or paid plan for the zone?
Click to expand...

Just for fun, I just checked my other site, where this add-on has been working flawlessly for a month or so, and it's doing the same thing there.

Oh, and I'm on the free plan...sorry. 🤦‍♂️
 
mjda said:
Just for fun, I just checked my other site, where this add-on has been working flawlessly for a month or so, and it's doing the same thing there.

Oh, and I'm on the free plan...sorry. 🤦‍♂️
Click to expand...
Ya was able to replicate it on my end as well so shouldn't be too hard to track down. I suspect Cloudflare may have made an unexpected changed to one of the API calls. Digging now...
 
Id like to thank you for constantly updating this add on. I got this error message after turning on the bot fight mode option. Then out of curiosity I turned on and off a couple of other options in the cloudflare settings and got these server errors.

IMG_0578.webp​
 
Ya... there's still an issue with the new API call for bot management related to how it changes depending on your account type. It's really dumb that Cloudflare thought it was a good idea to change the API call results, but only for certain account types, so now we have a single API call that returns different results and takes a different payload when writing to it. The short term solution (until I can get something better in place) is to not toggle the Bot fight mode option for now.

Judging from the error you get, is it correct that you are on a paid tier for your zone?
 
digitalpoint said:
Ya... there's still an issue with the new API call for bot management related to how it changes depending on your account type. It's really dumb that Cloudflare thought it was a good idea to change the API call results, but only for certain account types, so now we have a single API call that returns different results and takes a different payload when writing to it. The short term solution (until I can get something better in place) is to not toggle the Bot fight mode option for now.

Judging from the error you get, is it correct that you are on a paid tier for your zone?
Click to expand...

Sounds good and you are correct. I’m on a paid plan.
 
Peterpapas76 said:
Sounds good and you are correct. I’m on a paid plan.
Click to expand...
So let me first just rant about how idiotic the change to Cloudflare's bot management API is. Reads 4 different things depending on if the account is Free, Pro, Business or Enterprise. Writes 4 different things based on the same. It's also the only API call that you can't write what is read because reading returns read-only values you can't write. They have effectively mashed bot fight mode options (only available on free plan) with super bot fight mode (only available on paid plans) into a single API endpoint. And then pro, business and enterprise all have different available options for super bot fight mode.

That being said... I've unwound all the stupidity internally so we can handle whatever the API throws at us in a more managed way. The end result is there are a lot more options (before the super bot mode stuff wasn't even something you could toggle with the addon), with the options you can actually use (based on your plan) the ones that are enabled.

A zone on a free plan looks like this:

1697997576198.webp


A zone on a Pro plan looks like this:

1697997515153.webp

The "Likely Automated" option should (in theory) only enable itself if you are on a Business plan, but I only have Free and Pro plans to test against. Weirdly, the Enterprise tier seems to have less options available to them, so in theory the options you can toggle should be reflective of that.

If there's any volunteer(s) that want to test toggling those options on various plan types, let me know and I'll send you a version with the new stuff.
 
digitalpoint said:
So let me first just rant about how idiotic the change to Cloudflare's bot management API is. Reads 4 different things depending on if the account is Free, Pro, Business or Enterprise. Writes 4 different things based on the same. It's also the only API call that you can't write what is read because reading returns read-only values you can't write. They have effectively mashed bot fight mode options (only available on free plan) with super bot fight mode (only available on paid plans) into a single API endpoint. And then pro, business and enterprise all have different available options for super bot fight mode.

That being said... I've unwound all the stupidity internally so we can handle whatever the API throws at us in a more managed way. The end result is there are a lot more options (before the super bot mode stuff wasn't even something you could toggle with the addon), with the options you can actually use (based on your plan) the ones that are enabled.

A zone on a free plan looks like this:

View attachment 292888


A zone on a Pro plan looks like this:

View attachment 292887

The "Likely Automated" option should (in theory) only enable itself if you are on a Business plan, but I only have Free and Pro plans to test against. Weirdly, the Enterprise tier seems to have less options available to them, so in theory the options you can toggle should be reflective of that.

If there's any volunteer(s) that want to test toggling those options on various plan types, let me know and I'll send you a version with the new stuff.
Click to expand...

Gotcha. The options are chose were on that cloudflare page recommended settings page that you have on here. Today was the only time that I attempted to change an option. Also a couple of weeks ago with R2 lol.
 
digitalpoint updated [DigitalPoint] App for Cloudflare® with a new update entry:

More bot management API updates

  • Completely revamped how the bot management API is handled
  • Added Super Bot Fight mode settings as controllable options (options enabled/available to be toggled will ultimately depend on what your Cloudflare plan allows):
    • Likely Automated
    • Definitely Automated
    • Verified Bots
    • Static Resource Protection
    • Optimize For WordPress
    • JavaScript Detections
Click to expand...

Read the rest of this update entry...
 
After uploading the files of this recent update, prior to the next step of upgrading, I got this error:
Could not find class DigitalPoint\Cloudflare\XF\Template\Templater when attempting to extend XF\Template\Templater

2 minutes ago src/XF/Extension.php:200
Click to expand...
The details were:
Request state
array(4) {
["url"] => string(48) "/forums/forum-name1/?prefix_id=4"
["referrer"] => bool(false)
["_GET"] => array(2) {
["/forums/forum-name1/"] => string(0) ""
["prefix_id"] => string(1) "4"
}
["_POST"] => array(0) {
}
}
Click to expand...

It hasn't happened again so far (after I updated the addon).
 
That error implies the file wasn’t there. Did you delete the old files before uploading the new ones maybe (instead of overwriting)?
 
Not sure what Filezilla is, but maybe it deletes first internally? 🤷🏻‍♂️

But ya, as long as the file is there, it should be fine. And if you aren’t getting the error anymore, it’s there.
 
Everything is new, and I try to understand. Cloudflare tells me

2. To prevent admin functions from being affected by caching or performance features, create a Page Rule
to exclude the admin section of your site.
Click to expand...

Your app tells me:
Browser Cache TTL => Respect existing headers. In a good world the headers of the admin area are set to 0?
 
I try to set caching level to "no query string" and get

Code: 
ErrorException: [E_WARNING] Trying to access array offset on value of type null in src/addons/DigitalPoint/Cloudflare/Admin/Controller/Cloudflare.php at line 142

    XF::handlePhpError() in src/addons/DigitalPoint/Cloudflare/Admin/Controller/Cloudflare.php at line 142
    DigitalPoint\Cloudflare\Admin\Controller\Cloudflare->actionToggle() in src/XF/Mvc/Dispatcher.php at line 352
    XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
    XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
    XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
    XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2487
    XF\App->run() in src/XF.php at line 524
    XF::runApp() in admin.php at line 13
 
Robert9 said:
Everything is new, and I try to understand. Cloudflare tells me


Your app tells me:
Browser Cache TTL => Respect existing headers. In a good world the headers of the admin area are set to 0?
Click to expand...
A good rule of thumb is to change things as necessary for your site. If there was a universal setting for all sites, it wouldn't be something you can change.

I specifically put a note on the top of the settings page that more or less says that:

This is not a substitute for understanding Cloudflare, how it works and what each setting actually does. Don't go changing your Cloudflare settings just for sake of flicking switches.
Click to expand...

If you are having problems with how something is already set up, sure... but blindly changing things that might not have any relevance to your site is never a good idea.

Robert9 said:
I try to set caching level to "no query string" and get

Code: 
ErrorException: [E_WARNING] Trying to access array offset on value of type null in src/addons/DigitalPoint/Cloudflare/Admin/Controller/Cloudflare.php at line 142

    XF::handlePhpError() in src/addons/DigitalPoint/Cloudflare/Admin/Controller/Cloudflare.php at line 142
    DigitalPoint\Cloudflare\Admin\Controller\Cloudflare->actionToggle() in src/XF/Mvc/Dispatcher.php at line 352
    XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
    XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
    XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
    XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2487
    XF\App->run() in src/XF.php at line 524
    XF::runApp() in admin.php at line 13
Click to expand...
The error is due to Cloudflare changing one of the new API endpoints (specifically the one for Fonts). There will be a new version today to address that (that's what I get for putting in things tagged as "beta"... they might change).

Changing the Caching Level to anything other than "Standard" for a XenForo site will most definitely break your site (see above about not changing things unless you know why you are changing them specifically for your site).
 
You must log in or register to reply here.

Similar threads

D
[DigitalPoint] App for Cloudflare® - FRENCH translation [Deleted]
Replies
9
Views
877
Ozzy47
Ozzy47
digitalpoint
App for Cloudflare (appforcf.com)
Replies
12
Views
1K
securedme
securedme
Back
Top Bottom