checkers
Forum Replies Created
-
Got it! The problem was related to my nginx configuration, specifically my pretty-url rewrite.
I used to do this:
if (!-e $request_filename) { rewrite ^/blog(.+)$ /blog/index.php?q=$1 last; }
That triggered this check in WP-Super-Cache:Supercache caching disabled. Non empty GET request.
[…]
Supercache disabled: GET or feed detected or disabled by config.I changed the rewrite rule to this:
if (!-e $request_filename) { rewrite ^/blog(.+)$ /blog/index.php last; }And everything works fine. My thanks to the new(?) debug feature of wp-super-cache :-).
More info, and some strange behaviour:
Starting from an empty cache:
When I hit my frontpagewww.bluebottle.net.au/blog/from a cookieless browser, the supercache file is created. When I hit it from a browser I’ve logged into my blog from, the supercache and standard cache files are created. When I hit any other page that should be cached, I get a standard cache file being created.I’ve noticed this though in the settings:
Cache Contents
WP-Cache (40.45KB)
* 3 Cached Pages
* 0 Expired PagesWP-Super-Cache (25.92KB)
* 0 Cached Pages
* 0 Expired PagesSo it seems that it’s generating one super cache file, but not finding it again later?