abb78790

@marcosmyara:

Tough break. I have *zero* experience with wordpress, but I can make a few suggestions based on my experience with this caching problem:

It sounds to me like your site is being served from static pages by the apache/nginx webserver instead of php/wp scripts.

My setup is with nginx, and w3tc (asked me to) install rules in the nginx config file that specifies roughly the following: “when a static file exists in a certain directory, then rewrite the current request to that file and serve it instead of sending the request to php-fpm.”

It is conceivable that your setup has similar rules (with either apache or nginx). One thing that you might consider is to look into the

wp-content/cache/page_enhanced/

directory and poke around to determine if the home page that is being served is one of the static files in that directory. If so, I believe you can totally blow away that page_enhanced directory (or to be safe, move it to another name), and your webserver should then pass those requests on to your php/wp backend.

More generally, you want to get your webserver to stop serving these static files.

@marcosmyara,

Yeah, I think I have the same problem and have written some more details about it in this post:

http://ww.wp.xz.cn/support/topic/w3tc-disk_enhanced-page-caching-gzip-debugging?replies=1

I believe a number of us are having the same issue, because the post before this one seems to have the same symptoms.

Summary: it has something to do with page-caching support for gzip encoded responses. Try accessing your site with

curl -v <url>

to see if it works. Curl does not send the “Accept-encoding: gzip” header by default, so if it is the same issue as me, then it should work for you.