If you update your WordPress theme’s style.css, you may have noticed that you have to “force-reload” your site in your browser to see the changes. This is because your browser keeps a copy of the CSS cached on your hard drive. Depending on how your server is set up, it may not check for a … Read more
If this is about .css and .js changes, one way is to add “versions” of your files. For example: script_1.0.css // This is the URL for release 1.0 script_1.1.css // This is the URL for release 1.1 script_1.2.css // etc. Or alternatively do it after the file name: script.css?v=1.0 // This is the URL for … Read more
You may need to set nocache headers in your main template header. Include this near the top of the header.php after the opening tag: nocache_headers() From here: Function Reference/nocache headers Run some tests, I believe this should only affect the main page file, other files should still cache normally. More idealy, wordpress should be sending … Read more
Since, your site already uses W3 Total Cache plugin, let me provide a solution based on it. Please visit yoursite’s wp-admin/admin.php?page=w3tc_browsercache and look for the text “Set cache control header”. Check this option, if it is unchecked, and then choose “no-cache” for the “Cache control policy”. This needs to be done in three places… CSS … Read more
I’ve seen many more complaints about W3TC than WP Super Cache: WordPress › WP Super Cache « WordPress Plugins. W3TC loads the .htaccess file with many directives and tends to conflict with server side settings. With Super Cache, try PHP caching and follow the instructions to add an .htaccess file to the cache directory: http://wordpress.org/extend/plugins/wp-super-cache/installation/ … Read more
At the time of this writing, W3TC only recognizes the php5-memcache (vs. php5-memcached) PHP client for memcached memory object caching system/software. Hence the “Memcache extension: Installed” in W3TC compatibility test for memcached. Memcached being useful and efficient as a caching method for database and/or object user/data caching via W3TC, even on a single server setup, … Read more
I’m in the same boat, and I’m still figuring out what the best “approach” should be. It is not necessary to cache any of the WordPress core files (/wp-includes, /wp-admin, etc). You will have to cache some files that live in your theme. Stuff like the css, js, and any image resources you use in … Read more
I had a similar problem once with an aggressive database cache: the first check for an existing transient returned nothing – which was okay – but after I created the transient, I didn’t get it, because the empty cached result was always returned. So I built a dozen duplicated transients until I found the issue. … Read more
It may seem a bit of an odd question … but it does have a bit of an easy answer. I’ve been using W3 Total Cache on a multi-server setup for WordPress for 6+ months. For this project we decided to use memcached and not varnish. About WC Total Cache and CDN In W3 Total … Read more
The object cache is not reliable, in any case. For example, Memcached has its own system to purge items in cache: if it “thinks” that is too full it start purging items in way that is just not predictable. It is (or should be) known that when you have an external object cache system in … Read more