Page Cache – Status = not cached?

Have you tried to re-enable the plugin? Re-save settings? Reset all caches?

Yes, yes and yes.

@robnalexpress,

this is the extent of my technical and troubleshooting skills. =(

Morning all,

Have you checked my finding about @ob_start("ob_gzhandler"); problem I had?

If you do not have exact same code, you can check for similar code for compression – just do a full search in your plugins or theme files.

Hope that you will find find your buggers, as I found mine.

Regards,

Hi,

Im having many problems… pages not caching, minify not working, etc… etc…. my first byte received takes more than 7 seconds!!!

While all this problems are fixed im using wp-super cache and now my site answers pretty fast again!.

It is normal that a mayor update has all this bugs???

Regards,
[sig moderated as per the Forum Rules]

Have you checked my finding about @ob_start(“ob_gzhandler”); problem I had?

If you do not have exact same code, you can check for similar code for compression – just do a full search in your plugins or theme files.

I have tryed to disable all plugins but W3TC and my theme doesn’t have any gz compression or other method.

This problem is on all my 5 blogs that use different theme and different plugin and 3 of them are on 3 different servers.

I can confirm that also developer version 0.9.2.5b doesn’t fix the problem.

This thread is starting to become diluted. OP has nothing to do with gzip, minify or other plugins. Let’s stay on track with the issue of page status: not cached in debug mode.

One plugin have this line ‘@ob_start(“ob_gzhandler”);’ and after commenting it the W3TC start to cache all pages.

When you say “W3TC start to cache all pages” how do you know this? Do you mean it’s creating the files in the page cache directory? For me, the page cache files are being created, but in debug mode, using various settings and cache cleared browsers, I’m still seeing “status: not cached”.

So the question is: Is W3TC serving cached pages or not?

When you say “W3TC start to cache all pages” how do you know this? Do you mean it’s creating the files in the page cache directory? For me, the page cache files are being created, but in debug mode, using various settings and cache cleared browsers, I’m still seeing “status: not cached”.

So the question is: Is W3TC serving cached pages or not?

Hi,

After commenting that line, W3TC started to create files and in debug mode all is fine too.

Bottom line – W3TC started to serve cached pages.

Regards,

@CyberOto- Lucky you! I searched my folders for variations on @ob_start("ob_gzhandler"); and found nothing.

@robnalexpress the problem is that cached pages that you can see in cache folder are only “non compressed pages”. This is the problem, the plugin sould create beside the uncompressed pages, also a compressed gz one! But this gzipped file isn’t there.

Look here for a complete explanation:
https://www.ads-software.com/support/topic/bug-disk-enhanced-cache-doesnt-work-in-0924

Check it out and the report to Frederick Townes

@galerio- I have the following files for every page & post:

_.index.html and _.index.html_gzip

Since the files are being created, in my case, I’d love to know if the “status: not cached” is a false indicator. Is there another tool, other than the W3TC debug, that I can use to determine this?

I spoke too soon =[

Just upgraded *all* my sites to 0.9.2.4 and got this:

<!-- W3 Total Cache: Page cache debug info:
Engine:             disk: enhanced
Cache key:          _index.html_gzip
Caching:            enabled
Status:             not cached
Creation Time:      1.088s
Header info:
X-Pingback:         https://somedomain.com/xmlrpc.php
Content-Type:       text/html; charset=UTF-8
Last-Modified:      Wed, 14 Sep 2011 12:11:44 GMT
Vary:               Accept-Encoding, Cookie
Expires:            Wed, 14 Sep 2011 20:11:44 GMT
Pragma:             public
Cache-Control:      max-age=28800, public, must-revalidate, proxy-revalidate
Etag:               196379ba76593e7c9bb9fb0d9cd96174
X-Powered-By:       W3 Total Cache/0.9.2.4
Content-Encoding:   gzip
-->

Have no fear, told to myself, 0.9.2.3 is working fine. Next step was to downgrade and enable the 0.9.2.3.

Tadaaa … NOT

Now 0.9.2.3 is not working too. ARGHH!

Back to square one.

Regards,

Ad another observation with 0.9.2.4

Each time visitor load a page, the cached file for this page is regenerated. So, it is creating the files, but not using them, as they are re-created on each visit. A side effect of that is server load…

Regards,

Welcome to the club! I’ve submitted a but report and hope you and everyone experiencing this will too. Hopefully Frederick can get it fixed soon in the development version. It’s troubling that he says it’s fixed when clearly it’s not.