Comments on: Andy Skelton Introduces Batcache

By: Jeremy Clarke

Jeremy Clarke — Tue, 08 Jul 2008 17:15:21 +0000

Another reason you might want this is security. After I got hacked I had a hell of a time securing the cache directory so that it would still be writable by the server for caching but not by the hackers to run their evil scripts. Having tight permissions (chmod) on the cache directory stops all the options for wp-cache and wp-supercache from working, so I can’t flush the cache or edit the settings except by maually editing the wp-cache-config.php file, which is a real bitch (I hate telling users “wait 10 minutes and you’ll see your change”). Haven’t tried the plugin yet though.

Also, if people want to test the caching they can also just log in with a different browser (IE, FF, Flock, Opera) that doesn’t have a cookie for the site, way easier than editing a source file!

By: theWizard

theWizard — Mon, 23 Jun 2008 19:36:35 +0000

well If you want to know about these caching systems, this is what i can say. from the time i started blogging i was much interested in caching coz its a superb concept. I have tried wp-cache and it simply wrecks havoc in the blog, I really hate it. Supercache on the other hand is soooo wonderful and a superb companion. but if you have super-cache eneabled using apache mod re-write there will be some issues like, for example you can’t leech protect your images using htaccess. so I have the super-cache plugin in half-on status and it works like a charm. Its one of the most important plugins for me. (I believe that I’m right in saying, this should be built into WP in future editions coz caching is a basic need for high traffic blogs like mine).

By: Mark Ghosh

Mark Ghosh — Sun, 22 Jun 2008 21:05:14 +0000

FYI: If you are testing on your own blog, there is a massive chance that either you are logged on OR have left a comment on that blog, which will force batcache to serve live pages to your browser and you will not see the debug information before the <\head> as mentioned in the install. To get around this and test your install, you will have to comment out the part of the code that checks for cookie and comments in advanced-cache.php (lines 59-62).

By: Batcache for WordPress « Andy Skelton

Batcache for WordPress « Andy Skelton — Sun, 22 Jun 2008 18:47:51 +0000

[...] [I meant to publicize this after a period of quiet testing and feedback but the watchdogs at WLTC upended the kitten bag and forced my hand. Batcache comes with all the usual disclaimers. If you try it on a production [...]

By: Mosey

Mosey — Sun, 22 Jun 2008 10:45:15 +0000

Thanks for the recommendation, Jeff; but in addition, thanks to Gianluca for the information about memcache. Alas I belong to that category of users! Am still deciding on which to use out of Cache and Supercache since the former seems to have stopped working on me and I’m a little worried about jumping to the latter.

By: Gianluca

Gianluca — Sun, 22 Jun 2008 09:13:15 +0000

I am already using this plugin in production and I am quite confident it works fine where you cannot use wp-supercache (because it requires apache+mod_rewrite) or you do not want to use it for the increased i/o overhead.

Presenting the plugin you are anyway forgetting to report the most important thing about it: it’s “memcache” based. So this does not apply to 99% of wordpress self-hosted users, who are using a shared hosted environment or a low-end vps, and therefore cannot setup a memcached daemon to run bat-cache.

By: srinivas

srinivas — Sun, 22 Jun 2008 08:45:27 +0000

thanks to batcache,
i have been waiting for morethan a month for a new plugin for cache, as wpcache and super cache not working for me.
and yesterday iam one of the very first people who downloaded and using batcache, iam really thankful to him.

By: kim

kim — Sun, 22 Jun 2008 08:27:14 +0000

sounds very interesting, but how could you tell how fast your page is loading for a new user? if anyone knows