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
Not tested, but if you need a quick and dirty way, you could put a script like this in your WordPress folder and call it each time: define( ‘WP_USE_THEMES’, false ); require(‘wp-blog-header.php’); global $wpdb; $wpdb->query( “DELETE FROM $wpdb->options WHERE option_name LIKE ‘%\_transient\_%'” ); Not to be used on a production server.
Assuming you have shell access, or access to any Linux/Unix box, you could use wget to download the entire site to static html files: wget –recursive –no-clobber –page-requisites –html-extension –domains domain.com http://domain.com Then either upload or move these files to your web root (after backing up and removing your WP installation). I imagine it’s also … Read more
You should not cache anything in the admin so your examples are correct. A typical nginx reverse proxy cache is set to ignore wp\-.*\.php|wp\-admin Another option is to not cache logged in users by checking the wp cookies, but you probably don’t have that level of control. ps. It is highly advisable you test this … Read more
You could delete an existing cache for your option before you call get_option(): $GLOBALS[‘wp_object_cache’]->delete( ‘your_option_name’, ‘options’ ); $value = get_option( ‘your_option_name’ );