Re: [SMARTY-DEV] Possbile bug?

Would it be reasonable to base the cache naming on more than just the template filename? (ie. hash of filepath) I figured that using different cache dirs would avoid the problem but for sites where there are so many tiny modules it would be much easier if you were able to just use one. I guess it would go in the 'it would be nice if' category. That way you wouldn't have to worry about creating so many directories and maintaining all the permissions for all of them. Lachlan Monte Ohrt <monte@ispi.net> on 18 March, 2003 10:31:43 AM To: lmulcahy@pacbrands.com.au cc: Smarty Dev <smarty-dev@lists.php.net> Subject: Re: [SMARTY-DEV] Possbile bug? As long as you have a separate compile_dir and cache_dir for each template_dir, you should see no conflicts. Monte On Mon, 2003-03-17 at 17:44, lmulcahy@pacbrands.com.au wrote: > Hi, > > It appears that if you have a website that uses just one directory for each > of template cache and output cache and you have two templates with the same > name (ie. 2 'header.tpl's) that they battle it out in the template cache > and depending on how each of the pages are requested by users you can end > up having the wrong cached template compile called by scripts. Perhaps to > combat this the cache could be identified by something more unique than > just filename?. This problem was identified while running v2.3.1 and still > appears evident in 2.4.2. I'm only 95% sure this is the problem, but all > evidence seems to point in this direction. > > Could any of you developers confirm whether what I'm saying is likely to > occur and if so, is it still an issue in the current unstable? > > Thanks > Lachlan -- Monte Ohrt <monte@ispi.net> -- Smarty Development Mailing List (http://smarty.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php