[DigitalPoint] App for Cloudflare® 1.9.8.1

[digitalpoint]

Don't know anything about the Redis addon. Maybe disable page caching in the Cloudflare addon and see if it's still going on? Could also be a an issue where you made bad caching or page rules in the Cloudflare dashboard. Like you could in theory force all page to be cached with a jacked cache rule... Not sure why you would want to. But you certainly COULD.

 

[Ivancas]

Don't know anything about the Redis addon. Maybe disable page caching in the Cloudflare addon and see if it's still going on? Could also be a an issue where you made bad caching or page rules in the Cloudflare dashboard. Like you could in theory force all page to be cached with a jacked cache rule... Not sure why you would want to. But you certainly COULD.

Nah, I only used your addon settings (Easy config). Thanks

 

[Ivancas]

@digitalpoint I still have problems with the flags, I still see them even when this option is off:

 

[digitalpoint]

@digitalpoint I still have problems with the flags, I still see them even when this option is off:
View attachment 332163

Are you part of the Moderating group?

 

[Ivancas]

Are you part of the Moderating group?

Yes, but it should be overwritten by Never

 

[digitalpoint]

digitalpoint updated [DigitalPoint] App for Cloudflare® with a new update entry:

Couple internal things

• Fixed an issue where IPv6 addresses wouldn't always be geotargeted correctly with XF 2.3+.
• Uploads to R2 will work if the source stream isn't seekable (things like uploading with the URL as a source)

Read the rest of this update entry...

 

[digitalpoint]

Yes, but it should be overwritten by Never

Maybe try rebuilding permissions? Honestly it's pretty cut and dry as far as the addon goes. This is the logic used to add the flag:

<xf:if is="{{ $xf.visitor.hasPermission('forum', 'viewCountryFlag') }}"><xf:macro template="geo_macros" name="flag" arg-countryIso="{$post.Ip.Geo.country_iso}" /></xf:if>

The $xf.visitor.hasPermission('forum', 'viewCountryFlag') function is the standard XenForo core function. For whatever reason, your setup thinks that the visitor has that permission... why that might be, I'm not sure... that's all internal XenForo stuff. Rebuilding master data/permissions for your site might be a good first step though.

 

[webbouk]

I'm not sure if this is coincidental but since upgrading this add-on to the latest version I get this error when accessing the addon through the ACP,


Oops! We ran into some problems.
9109: Invalid access token



And this error when trying to access my Cloudflare account directly on the CF website>

API Request Failed: GET /api/v4/memberships?no-permissions=1 (undefined)

I can log into Cloudflare directly but cannot get past the following page:



Any suggestions would be appreciated...

 

[digitalpoint]

Nothing to do with this addon. It couldn’t affect Cloudflare dashboard even if we wanted to.

 

[webbouk]

I'll get onto CF support, thanks for the prompt reply

 

[webbouk]

Fixed - I ended up creating a new API Token, reloading the add-on, and entering the Token ID in the add-on Options

 

[digitalpoint]

Fixed - I ended up creating a new API Token, reloading the add-on, and entering the Token ID in the add-on Options

Pretty sure it would have been coincidental though. Like I said, there’s nothing the addon could do (even in theory) to affect the dashboard on Cloudflare website. But great things are working.

 

[Mr Lucky]

I'm a bit confused about tokens, should I choose specific template or custom? Apologies if that has been answered

 

[digitalpoint]

I'm a bit confused about tokens, should I choose specific template or custom? Apologies if that has been answered

View attachment 332762

You are going to have a much easier time clicking the API Tokens button on the options page where you put the token. That special link is only there if you don’t already have an API token set. It will save you a ton of time and aggravation trying to find the permissions in the drop-down lists.

 

[Mr Lucky]

Is it OK to use one token across all domains/zone if I want the settings to be the same. I presume whatever I chane on one site will then affect the others. Is that correct or advisable to create a separate token for each site

 

[digitalpoint]

I use the same token across sites. Changing settings on one zone (site) does not change settings on another. Only the token is shared, not settings.