Smarty

[nlenz]

Something I figured out... if you need a cache_id that you don't want to worry about in the future:

$cache_id = md5($_SERVER['REQUEST_URI']);

or

$cache_id = md5('mything'.$_SERVER['QUERY_STRING']);

This way when you add something to your page in the future, say a printer friendly version by appending &printer=1 to the query string then you don't have to worry about keeping track of every little id that changes your page.

Of course this doesn't work in every situation.

One question though,...why doesn't smarty automatically take the QUERY_STRING into account when displaying a cached template (when not given a cache_id).

So if this code was executed with the following url's,...shouldn't they automatically return different caches?

$s->caching = true;
$s->display('coolpage.tpl');

http://somesite/coolpage.php?cool_thing=2
http://somesite/coolpage.php?cool_thing=3

Just some thoughts....

[mohrt]

[datamile]

Never thought of that...

Normally build the cache id from the required parameters of the page , and then pass it to a translating routine which generates an ID in a mysql data if the cache id is over a certain lenght