How to use this plugin with CloudFlares own Caching Configuration?

When running this plugin, make sure you do not have any page rule or workers set up that modifies the caching behavior as this should be the only plugin handling your cache behavior. You can have page rules related to security or redirect but not caching.

When you set the plugin for the first time by adding the API key, the plugin will set everything up on it’s own and you don’t have to do anything.

You can enable the minify, rocket loader or railgun if you want as railgun only handles non cached content. But I personally didn’t used it with railgun as in my experience it doesn’t provide much benefit compared to the complexities.

Hi there, thanks for your feed back. I read your documentation wrong then.

The free Cloudflare plan allows you to enable a page cache by entering the Cache Everything page rule, greatly improving response times. However for dynamic websites such as WordPress, it is not possible to use this page rule without running into problems as it is not possible to exclude critical web pages from the cache, the sessions for logged in users, ajax requests and much more. Thanks to this plugin all of this becomes possible.

To my misunderstanding, I read from this, that it becomes possible using page rules without problems thanks to this plugin ;-).

What about the CF Caching Configuration > Caching Level, should it be set to

No query string, Ignore query string or Standard

I’m using BuddyPress and I think I can see som load speed improvements on the dynamic content using Railrun.

Thanks

What about the CF Caching Configuration > Caching Level, should it be set to

– The default is standard and keep it to Standard only. Don’t thinker with that and also the settings for Browser Cache TTL. Make sure it is set to respect Header.

I’m using BuddyPress and I think I can see som load speed improvements on the dynamic content using Railrun.

– OK. If you are using buddypress where most of the user sessions are logged-in session, I am not sure how much improvement you will see with a page caching system. As in case of sites like these all contents needs to be dynamically generated by the origin server.

Page caching is mostly effectly where the general user will see a static content, e.g. blog post, page, content page, portfolio page, product page etc. where the content is basically static unless someone logs in.

Also I will suggest you to try the worker mode as you are using a buddypress site.

Thanks for your clarification, and your objective advise. So the conclusion must be that I will not benefit from using the plugin together with BuddyPress?

In general, can’t dynamic caching not work together with page caching? Even if your site is mostly dynamic content, the frontpage is normally always static?

Regards
Carsten

Honestly, not really cause you have a forum site where in order to interact, people login to the site and then post and do other stuffs. Now these things are dynamic and a static cache page cannot be shown to the user. Cause if I am login in I would the site would show my name, details etc. But if you login it’s going to be different for you.

Rather, I would recommend checking your Google Analytics and see from where most of your users are coming from and get a good nginx server in that location so that dynamic content stays fast with lower latency.

Generally in a forum site there is almost no static content that are cachable.