Could you please try the development version http://wordpress.org/extend/plugins/w3-total-cache/download/ and submit a bug submission report if the problem persists?
I’m seeing a similar problem, I originally tried using xcache for page/minify/db, but nothing was showing as cached in debug. I then switched to disk (enahnced where applicable), and now I see queries being cached, but never the page.
<!– W3 Total Cache: Page cache debug info:
Engine: disk (enhanced)
Key: buyers/tip-2/_default_.html.gzip
Caching: enabled
Status: not cached
Creation Time: 0.081s
Header info:
X-Powered-By: W3 Total Cache/0.8.5.2
X-Pingback: *********************************
Content-Type: text/html; charset=UTF-8
Last-Modified: Tue, 04 May 2010 21:02:56 GMT
Vary: Accept-Encoding, Cookie
Pragma: public
Expires: Tue, 04 May 2010 22:02:56 GMT
Cache-Control: max-age=3600, public, must-revalidate, proxy-revalidate
Etag: 18913c8a27fb78c6f285009971fe67fd
Content-Encoding: gzip
–>
I downloaded the development version as advised, but the results above are the same.
I can confirm this behaviour for XCache based caching: According to the debug output nothing ever gets cached – Not the minifying, the page and no DB queries, even though it is set up to the exact opposite 😛
Is xcache properly caching scripts for you? Can you verify in the control panel? Are there errors in your apache error log? Are you using fastcgi?
XCache itself is working properly, i see lots of cache & variable hits in my monitoring (Munin). Webserver is NGINX and PHP is invoked as (fast)CGI using PHP-FPM.
I’ll try the development version tomorrow to see if that maybe fixes the problems.
Went back to xcache as well, as thats what I’d like to get working. Using apache (not fcgi), xcache is working, I see hits via its admin panel, but still nothing showing as cached via w3tc. DB queries and pages both return “Enabled” and “Not Cached”.
I’m using the most recent dev version.
<!– W3 Total Cache: Page cache debug info:
Engine: xcache
Key: w3tc_170cfab40c13563753d804f48b40a98a_page_6666cd76f96956469e7be39d750cc7d9_gzip
Caching: enabled
Status: not cached
Creation Time: 0.154s
Header info:
X-Powered-By: W3 Total Cache/0.8.5.2
Last-Modified: Wed, 05 May 2010 19:17:45 GMT
Vary: Accept-Encoding, Cookie
Pragma: public
Expires: Wed, 05 May 2010 20:17:45 GMT
Cache-Control: max-age=3600, public, must-revalidate, proxy-revalidate
Etag: 1be94fc39b210c9f28f8ff5715d43ade
Content-Encoding: gzip
X-Pingback: ***********************88
Content-Type: text/html; charset=UTF-8
–>
I can confirm this as well. Nginx here. XCache itself is working – I see variable hits being counted in the admin panel – but W3T says its not serving from the cache (edited SQL info out btw).
<!– W3 Total Cache: Db cache debug info:
Engine: xcache
Total queries: 30
Cached queries: 0
Total query time: 0.005
SQL info:
–>
<!– W3 Total Cache: Page cache debug info:
Engine: xcache
Key: w3tc_4dd0ca5fb9a6a625faeb659d6652078e_page_b8e4030c85fef30e424100adea385cad
Caching: enabled
Status: not cached
Creation Time: 0.662s
Header info:
X-Powered-By: PHP/5.3.0
Pragma: public
Expires: Thu, 06 May 2010 00:59:46 GMT
Last-Modified: Wed, 05 May 2010 23:59:46 GMT
Cache-Control: max-age=3600, public, must-revalidate, proxy-revalidate
Vary: Cookie
Etag: 730c4a2c8bad6ad30fe7f70edab06caf
Content-Type: text/html; charset=UTF-8
–>
don’t suppose either of you could share your nginx conf rewrite rules that work with w3tc? Looking to migrate to nginx, but not unless I can get w3tc working with it.
Null_: using XCache-based caching you don’t need the rewrite rules, besides for minifying – which are shared in one of the recent threads about it here.
Regarding disk-based caching, the rules would have to be adopted – i’ll look into those in the coming days but won’t make any promise if i’ll be able to translate them 🙂
oh excellent! Now if only we can get xcache-based caching working then 🙂
I can’t duplicate this issue. Please edit lib/W3/Cache/Xcache.php file:
on line 40: return xcache_set($key, serialize($var), $expire);
change to: return xcache_set($key, $var, $expire);
on line 51: return @unserialize(xcache_get($key));
change to: return xcache_get($key);
so in my case, I had xcache.var_size left at the default of 0. I changed that, and am now seeing the sql queries properly cached via xcache, though my page still isn’t.
When making the changes you specified, originally it gave me errors due to var_size being 0, once fixed, all of my pages then stop working completely with the changed lines.
<!– W3 Total Cache: Page cache debug info:
Engine: xcache
Key: w3tc_170cfab40c13563753d804f48b40a98a_page_ebf6ffc164b4d05f6df4c90ed0597ceb_gzip
Caching: enabled
Status: not cached
Creation Time: 0.077s
Header info:
X-Powered-By: W3 Total Cache/0.8.5.2
You no longer need to change those lines in light of the fact that xcache was improperly configured. See if the caching works after reverting the changes.
The caching of sql queries works after the change is reverted, however the page caching is still showing as not-cached, shown in my above post.
Does page caching work in basic mode?
