Compatibility with Bigscoots
Is your feature request related to a problem? Please describe.
Bigscoots is working towards compatibility with WP Rocket. I am opening this feature request so we can cooperate with their devs to achieve this.
More details here: https://secure.helpscout.net/conversation/1766407024/321141?folderId=2683093
Describe the solution you'd like
-
Deactivate WP Rocket's page caching in favor of their caching
-
Deactivate our expire rules and maybe htaccess usage: When WP Rocket page caching is enabled it changes the cache-control response header why it is needed for WP Rocket Page cache to work while we use cache-control header to set with different values.
-
Deactivate advanced-cache.php usage by WP Rocket
-
WP_CACHE constant should be untouched by WP Rocket.
Describe alternatives you've considered Since it is a similar situation maybe we need to work on building a 3rd party compatibility? like the one we have with WP Engine, or Flywheel.
Additional context More details are shared by their devs in the ticket: https://secure.helpscout.net/conversation/1766407024/321141?folderId=2683093
@alfonso100 We'll need an account to test things on their hosting, do you happen to have one?
@piotrbak Can you invite me to a channel on slack or reach me via [email protected]
Related ticket: https://secure.helpscout.net/conversation/1836096847/335502?folderId=2683093
In this case, the website has a mu-plugin that disables page caching, and preloading, using our pre_get_rocket_option_ filters, which prevents our options from being enabled: https://snippi.com/s/61llnu2
The plugin is located at: /wp-content/mu-plugins/wp-rocket-no-cache.php
They are using the following filters:
add_filter( 'do_rocket_generate_caching_files', '__return_false' );
add_filter( 'rocket_generate_advanced_cache_file', '__return_false' );
add_filter( 'rocket_disable_htaccess', '__return_false' );
add_filter( 'pre_get_rocket_option_sitemap_preload', '__return_zero' );
add_filter( 'pre_get_rocket_option_sitemap_preload_url_crawl', '__return_zero' );
add_filter( 'pre_get_rocket_option_sitemaps', '__return_zero' );
add_filter( 'pre_get_rocket_option_manual_preload', '__return_zero' );
This approach is confusing for our customers, because they think the Preload option is not working. We will need a better approach here
We need to disable preloading, we've seen too many cases where WP Rocket basically DOS's the server and brings the site down. What approach are you suggesting?
cc/ @piotrbak here
I think a possible approach, instead of disabling the preload, would be to increase the Preload crawl interval: https://docs.wp-rocket.me/article/8-how-the-cache-is-preloaded#crawl-interval
With a bigger interval, the CPU usage will be smaller.
We have a helper plugin you can use as a base if you're interested in testing this approach: https://github.com/wp-media/wp-rocket-helpers/blob/master/preload/wp-rocket-custom-preload-intervals/wp-rocket-custom-preload-intervals.php
New ticket: https://secure.helpscout.net/conversation/2915935352/555781?viewId=2675957