Re: [SMARTY-DEV] cache_serials and non-cacheable plugins

Are you using 2.6.10? That version contains fixes that affect the cache handling features you are refering to. Prior to that, there were long-standing issues with the non-cacheable plugins. I have yet to run into any since :) --- Nichlas Löfdahl <crotalus@acc.umu.se> wrote: > Hello! > > I'm having some problems, which seems to be (without deeper knowledge > of Smarty internals) originating from how cache_serials are generated > (md5(uniqid())). > > I have a couple of webservers. The compiled templates are stored > locally on the webservers. The smarty cache-files are stored on a > shared storage. > > The templates in question are componized, made of parts which are > cached seperatly (by using a second instance of smarty and doing > $cache_smarty->fetch() and then $smarty->assign() the result to the > main template). > > I also have a function plugin registered as non-cachable. When the > cached part of the template is shown it also shows a string like " > {nocache:d41d8cd98f00b204e9800998ecf8427e#0} ". Obviously it seems > like Smarty cannot replace the nocache-part with the appropiate > function. > > Any ideas how to solve this? It would be good if the serials wasn't > timebased (uniqid()) because the clock of the different webservers in > a cluster is never completely synched. > > /Nichlas __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com