haddow777

The first thing to do is to find out what webserver you are using. Apache and Nginx have really different issues when it comes to rewrites. Try using the phpinfo() function to find more information about your setup.

I have not had an issue with gzip, but I have run into this problem several times. Here is what I have concluded from running into it several times.

If you have any debug output on, it will cancel the cache. Page caching is meant to circumvent PHP, but wanting debug info generated forces W3TC to skip the cached file and load PHP. I know it is counter-intuitive, but it makes sense. First step, turn off all debug output. If you want to check to see if your files are caching, check the pgcache directory for newly generated files and your load times using a tool like Chrome’s developer tools network tab.

Also, most default setups of W3TC prevent caching for logged in users. Make sure you are logged out. I have had trouble even logged out though. I’m not sure why, but even after I logged out in chrome, the files still wouldn’t cache. When I loaded Firefox, a browser I hadn’t logged in with before, the pages started caching.

Has W3TC given an error message saying that rewrites aren’t working? If not, do you have rewrites turned on? If so, do you have rewrite checking enabled? If you have both options enabled and you haven’t gotten an error message, you probably aren’t having an issue with rewrites.

Also to make sure mod_rewrite is in fact installed, create a file with phpinfo() in it. Never assume something is installed. Also, don’t leave this file around after using it.

One last thing. Do you have any of the debug info turned on. In my experience, disk enhanced caching doesn’t work with the debug info turned on as php has to be loaded to generate the output. Turn off all debug output and check the pgcache folder to see if cache files are being created as you surf your site.

Don’t forget to surf your site while logged out of your site. I’m pretty sure the default setup won’t cache if you are logged in. I use a separate browser to do it. (ie I develop in chrome and generate my cache in firefox.

Sorry for so many messages. I have narrowed it down to the jQuery code loaded by the form plugin. My guess is that it is overriding the ui theme. Is there a way to prevent other themes form overriding the widget’s theme settings?

Okay, so I just deactivated the forms plugin, and magically my style setting is working again. Can you look into why this might be happening please. Thanks.

I’m not an expert, but I don’t think people using W3TC really want to have the functionality you mention. The whole point of a cache is to prevent PHP from being used in most page loads. If your plugin worked for every page load, having a cache would be pointless.

Putting that aside, if people would like to cache (even an inefficient cache) and use your plugin, W3TC does support cache fragmenting. If you could somehow use cache fragmenting to prevent your plugin from being added to the cache, that could work. But if it does, let people know up front that their caches will be interrupted.

Beyond that, there might be an option to cache seperate files for each user agent. I’m not sure my self as I haven’t had the need for it. Doing this also has drawbacks as well. The cache size will be a lot larger due to all the additional files required for duplicating pages for each user agent. This should also be mentioned up front if this is the direction you move in.

Other than that, you could just get people to disable page caching. They could still benefit from css/javascript minification and concatenation, object and database caching, and CDN’s. Although your plugin would really need to offer something great to give up page caching.

Have you purged all your caches and clicked through your links to rebuild them?

I find that updates can mess up the cache. I usually find it best to throw out all caches and rebuild them.

I can’t say for sure what your problem is. My experience has always been that everything has been written to the nginx.conf file in the root web directory.

I am using Debian 6, Nginx 1.2.0, WP 3.3.2, W3TC 0.9.2.4 among other things.

Are you using rewrites? It seems that when you copy from the install tab, that everything is working, caching wise. Is that the case?

I don’t see how W3TC not writing things into the nginx.conf file would be a bug in Nginx.

Sorry I can’t be more help.

Unfortunately, just deleting the plugin probably won’t be enough. I have found that it doesn’t clean up all traces of itself when removed. Instead, it would probably be better to deactivate every feature and purge every cache, deploy, then purge every cache again, then remove the plugin. Then start a sweep for files left behind like .htacces files if you are using Apache.

W3TC is not a great “use out of the box” type plugin. The more powerful something is, the more specific it has to be. Most likely, to get the shopping cart to work, there would probably need to be a number of customizations created. Specifically to keep the whole shopping cart system from being cached.

A more advanced developer might be able to use fragment caching to get even more of the shopping cart software to cache without disrupting service.

In any event, to fix it, you will most likely have to reinstall the plugin and go through the deactivation procedure I mentioned in the beginning.

Also try removing your other plugins and reinstalling them.

Sorry I can’t offer better advice, but without being able to get into the guts of your site, I just can’t be more specific. I have never used the plugin or theme you are using.

I’ve been in your shoes. Getting Nginx to work with W3TC is really frustrating. First, while a nginx.conf is generated for you, it doesn’t have everything. Also, there are tonnes of blog tutorials out there are offer poor configuration advice.

I can’t tell you how many different ways I configured my nginx.conf in ways that didn’t work. So frustrating.

I can see two issues with the post you are using. First, some things are more complicated than they need to be, and they don’t include the generated file. Actually, they also don’t link to php-fpm with a unix socket either, which is faster as it drops some overhead.

check out this post. It is mostly okay. A big difference here is yours is trying to use Nginx to cache while this one uses varnish to cache. (Poorly too, as it doesn’t configure varnish to strip cookies, therefore it wasn’t working out of the box).

This is the best line I have found, and I have tried many.

location / {
    try_files $uri $uri/ /index.php?q=$uri&$args;
}

I know it looks crazy, and I only have sort of know how it works, but the point is it works. Mine does.

Also, at the bottom of your server block, after the php-fpm section, include the generated conf file in your web root (whatever yours is).

include /var/www/nginx.conf;

Also, Minify rewrites are a finicky thing. There are a number of things that can kill them. I have even found certain firewall setups that kill all rewrites (and possibly more). If you have WP installed in a subdirectory of your webroot, check out this fix.

I hope that helps some.

Just as a note to anyone who feels like this. One thing I learned about W3TC, is to not to try and learn it on a production website. If you don’t have considerable experience with it and it’s quirks, definitely copy your whole site and create a test version of your production site. Make sure all plugins and everything else are included.

Then try to install W3TC on the test version and see how it reacts. Also, in reality, when dealing with W3TC, going slow and methodically is always best. It would be best to deactivate all the other plugins, then start it. Once, and if, you get it working, try to bring back your plugins one by one. Purge your caches and check that it works for every one.

Also, if you are impatient, it is best to go with another option. W3TC does offer a number of good performance options (enough that I stuck around), but if you are happy with straight static caching, use another plugin like Super Cache.

At least, that is my opinion.

Does anyone know how to update a past post? I would have rather updating my last post as I forgot to mention something.

Oh well. Don’t forget, if you are using a child theme, the functions.php in the child theme doesn’t override the functions.php in the parent theme. It appends it. So the functionality I mentioned most likely is in the the parent theme’s version of the file.

Okay, so this is a possible solution, but like I said, it is more difficult. Also, this is really a customization that you should have your own coding experience or pay a person with coding experience to do.

Each widget container in a theme, at least the one’s bothered looking at, like twentyeleven, is initialized in the functions.php file in the theme folder. If you search for “add_action( ‘widgets_init'”, you should find it. At the end of it, there is the name of a function where all the widget slots in your theme are initialized.

Each widget initialization includes spots where you could (possibly) include some form of cache fragment code.

'before_widget' => '<aside id="%1$s" class="widget %2$s">',
'after_widget' => "</aside>",

Again, due to the dynamic nature of it all, and the fact that I am basing this all on theory, this might not work. I’m not sure if what ends up between ‘before_widget’ and ‘after_widget’ will be a function and I’m pretty sure it isn’t a file.

I hope you the best, and remember, if what you try doesn’t work right away, re-evaluate doing the whole sidebar.

That would be a real issue. You can’t exclude the file because wordpress doesn’t load the widgets like that. The widgets are dynamic elements that are generated deep in the WordPress system. The whole side bar is the easiest solution. I will give a quick look at the code to see if I can find a way to narrow it down for you though.

If you believe it is an issue due to your using a child theme, try copying all the css files from the parent theme into the child theme. They won’t affect how the page works as they will override the parent’s files with the same values.

I’m sorry I don’t have much experience with the help wizard not working, mine has always worked. I am using a child theme too, but I customized much of it, so most of it is in the child theme folder anyways.

I hope that helps.