Cache Handling 2.5 RC1

hi, i posted this a week ago on smarty-general regarding the changed order of compile and cache ids used to create the cache path, nobody responded to that, so again: ;-) 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 kossmeier bergfex.at - http://www.bergfex.at