Support » Plugins » [Plugin: W3 Total Cache] Caching: enabled Status: not cached

  • Resolved Cristian



    Does it mean the page was not cached? If so, what is the reason for that page not being cached?

    I tried to refresh the different pages a few times to give W3TC the chance to cache the pages but it did not make any difference.
    See below my debug info.

    Thank you for your help in advance.

    <!– W3 Total Cache: Page cache debug info:
    Engine: apc
    Key: w3tc_b9b190e90e262264345359434ba61dd5_page_535460f534322d34a4253c9e31c40269_gzip
    Caching: enabled
    Status: not cached
    Creation Time: 0.325s
    Header info:
    X-Powered-By: PHP/5.2.5
    Pragma: public
    Expires: Wed, 24 Mar 2010 02:50:49 GMT
    Last-Modified: Wed, 24 Mar 2010 02:47:49 GMT
    Cache-Control: max-age=180, public, must-revalidate, proxy-revalidate
    Vary: Accept-Encoding, Cookie
    Etag: 856a4e87edc4eb6dd0c29cea9604f50d
    Content-Encoding: gzip

Viewing 14 replies - 1 through 14 (of 14 total)
  • Yes, it means the page was not cached. Did you try to open the same page in various browsers? Did you empty your browser cache between tests?

    Hi Frederick,

    yes W3TC cached the page again after I emptied the browser cache which makes sense.

    Thank you

    You’re welcome.


    After some playing around I still am not able to get the status of pages to cached. It keeps saying Status: not cached.

    However, the timestamp of the debug info stays the same.

    I have installed memcached and APC on the server.

    What am I missing?

    Ah, sorry. Got it to work. Was looking at front page, and that page is not cached by default.

    Why is that?

    The home page is cached by default. Did you deselect the option?

    Nope. On the page cache settings page, index.php was included in the “Never cache the following pages” setting. I think that was the problem, because when I removed it, it cached the front page directly.

    So your problem is resolved jberculo?

    Probably, as it says that the page is cached now.

    On the other hand, the index.php was probably added to “Never cache the following pages” for a good reason.

    So I am wondering, should the page be there, and can my removal of it have unforseen consequences?

    You should keep the defaults unless you have a good reason.

    Yes well, that is what I am asking myself. Do I have a good reason to do so?

    Basically: does the index.php belong in the “Never cache the following pages” setting?


    Thanks. Then I will put it back there and look further into the problem 🙂


Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘[Plugin: W3 Total Cache] Caching: enabled Status: not cached’ is closed to new replies.