> > If you set COMPILE_EXT or COMPILE_DIR then the Perl versions of the > > > compiled templates will be written to disk and re-used next time. > > > > in the 2.07 release, if you enable either of these directives then memory > > caching will be circumvented and the compiled template loaded from > disk each > > time (_store isn't called from load_compiled in > Template::Provider). I've given > > Andy a patch for this. > > I don't see a point for such a patch. Isn't setting CACHE_SIZE => 0 > enough to achieve this? What if I want compiling AND caching? How can > this be achieved with your patch? Or am I missing something?
My apologies, I was being unclear. What I meant was: in the template toolkit release 2.07 (and before) there is a bug in Template::Provider. This bug means that if you enable disk caching of compiled templates then the in-memory caching stops working for the templates cached on disk. The patch fixes this bug. -- regards, Simon Luff Sports.com
