Ionut Neagu
Forum Replies Created
-
Hey,
I am not sure what functionality are you using from Flying Press, we are still missing some optimisation features, like unused css, but if you aren’t relying on those, for caching and some basic optimisation features, you’re covered only with Super Page Cache PRO.Thanks for reporting, would look into it.
It was supposed to be like that, in the new version we improved the rule.
Hey,
We don’t recommend that you edit the main rule the plugin creates directly, for e.g in this new plugin version we updated the rule to do what you tried + disabled remove cache buster by default.
If you want to apply custom settings in CF, we recommend you create a new rule and set the right order, instead of editing the rule the plugin creates which would be overwritten.Hey,
You’re right, email is not needed for the token, we’ll hide the field for it.
This is an error caused to the permissions that you gave to that api token, here are more details : https://developers.cloudflare.com/fundamentals/api/reference/permissions/
We’re working on a documentation to clarify the required permissions, but for now you can try to start from the WordPress template provided and add ability to edit Cache Rules + transform rules.Hey,
Please make sure you’re using the latest version and this week we’ll have a release fixing this and allowing you to add cookies in the dashboard.
Editing the rule is not a best practice since we keep improving it, the best approach is to create a new rule if you want to change anything.End of this week.
the guide is a different thing, is not about what you are asking.
We would add this in the next update, but it would be a pro feature. Not possible right now.
Hey,
This is not something you should worry about, nor manually updating the rule, we’re working to make sure we’re choosing the right setting and exclusions.
We adjusted this to make sure we handle both www and non-www, but don’t affect other subdomains that you might host under the same zone.Hello,
You might be right here, this should be fixed after the release we’ll be making this week where we’ll be excluding urls based on cookies/path as well.Hey,
Yes, for now, we reverted to the simpler rule, because the previous one was hardcoded, in the next version we would go back to the more detailed and more efficient one, but accounting for your settings in the dashboard.
Hey,
First, please do not modify that rule since we overwrite it, create a new one if needed.
Second, historically because the plugin was using Cache rules, that setting was not for Cloudflare, but for the fallback cache, in the past the plugin was using cache-control headers to tell CF to don’t cache different pages.
In the upcoming version we would add the functionality that you except, all the cookies added there would be added automatically to the CF Cache rule.Hey,
That should be helpful, at the moment this not something our plugin is doing, so there is no conflict.Hey Scott,
I can see that you didn’t gave Cache Rules edit rights to the token, so it won’t work. You can see more info in the logs.
Regarding the rule, I suggest you do not edit the rule that the plugin create, since for e.g in the next version we’ll update this automatically. If you want to make edits, I recommend creating a different cache rule yourself.