Re: [SMARTY] Cache groups problem
| From: | Andreas Kossmeier | Date: | Tue, 11 Mar 2003 18:32:05 +0000 |
| Subject: | Re: [SMARTY] Cache groups problem | ||
| References: | 1 2 3 4 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-8564@lists.php.net to get a copy of this message | ||
hi monte,
Monte Ohrt wrote:
I see the problem. It seems that the compile_id should be the first cache group, right?as mentioned before, the compile_id is a kind of group (it groups different compiled versions of a template), but it *isn't* a cache group. the changes in CVS V1.352 break the main advantages of different compile ids. all different compiled versions of a template have one thing in common: they depend on the same data, so if this data changes, you have to clear _all_ caches of this template for the given cache id. CVS Version < 1.352 /events/group1/124/en/ /events/group1/124/de/ /events/group1/124/fr/ /events/group1/125/en/ ... CVS Version >= 1.352 /en/events/group1/124/ /de/events/group1/124/ /fr/events/group1/124/ /en/events/group1/125/ now you can't clear the cache for "events|group1", because you don't know about different compiled versions. ps.: currently i can't think of clearing a special compile_id. any situation where someone would want to do this? in case this isn't needed, i wouldn't choose the class var compile_id automatically for clear_cache... Andreas -- andreas kossmeier bergfex.at - http://www.bergfex.at