Add option in "Cache-Method" checkbox to disable caching

[nimo23]

Please add a new select item NONE (or Disabled) in the "Cache-Method" checkbox to disable caching (i.e. by selecting NONE, the caching directory will be deleted from wp_content and caching will be disabled).

[stklcode]

What’s the benefit over disabling the Cachify plugin? 🤔

[nimo23]

What’s the benefit over disabling the Cachify plugin?

Yes, you are right, we can deactivate the plugin – no additional selection is required.

By the way, what is the main difference between Jetpack Boost caching features and Cachify's caching features? At first glance, it seems that Cachify needs some more customization (e.g. settings in .htaccess or nginx.conf. The problem is that when deactivating the plugin we need to be aware that such settings are made in these files. Perhaps Cachify can provide more automation (e.g. automatically (re)setting the corresponding config files when (de)activating the plugin). What I can see is that the Jetpack Boost caching feature does not require any additional manual configuration in such external files.

It would be nice to provide some pros and cons between the two plugins.

[stklcode]

Well, if you modify your server configuration, the effect is the same whether there is no Cachify at all or it just does not generate any data. The modified ruleset will not find any data on disk or memory cache and passthroigh the original page, so little unnecessary overhead, but no degraded user experience.

(you don’t have to do that, all caching methods will work fine without any additional changes, it’s just the last bit of performance improvement to serve from cache as early as possible)

But with 2.4 providing a NOOP caching backend which does - as the name implies - nothing (used as fallback internally on detected misconfiguration), adding an option to disable caching should be something like a 2-liner.