Donncha Ó Caoimh
Donncha Ó Caoimh
Are you still seeing this? The latest version of the plugin has some fixes to the mobile checks. I tested and I was served a cached page named index-https-mobile.html.gz
This doesn't fix the problem for all sitemap plugins as each plugin has to set the feed query var correctly. I'm not even sure if the plugin you mention above...
This was unintentional, but at least any change to a menu will be apparent immediately on the site as the cache is deleted. The plugin doesn't differentiate between post types...
Do you have mobile browser support enabled? Are you disabling caching for mobile users? Are the user agents listed in mobile browser support in the "rejected user agents" that you...
There's a "Cache HTTP headers with page content" setting now that you could use to add the headers when serving the page initially. The headers you want will be cached...
@javorszky - give the code here on master a spin. I'm running it on my blogs and I fixed and merged the issue with the front page in Automattic/wp-super-cache#175.
I added compression warnings. The notice will appear if either of these are true (or both true): 1. if WPSC_DISABLE_COMPRESSION is defined. 2. if the function gzencode() isn't defined. If...
I need to remove cache_gzencode. Use cache_compression instead to enable or disable it.
cache_rejected_user_agent is what you should use for the rejected user agents. cache_lock_down for lock_down status. You can set that now as well. I fixed the "boolification" of those array settings...
You can use cache_compression to tell if gzip encoding is enabled or not.