| Dennis Freise 2004-07-07, 4:00 am |
| On Tue, 6 Jul 2004 18:12:47 +0200
messju mohr <messju@lammfellpuschen.de> wrote:
Thanks for your answers. That gives a whole new perspective to {eval}...
> if performance is a concern you never ever should use {eval}. it may
> be acceptable when you have caching enabled but even then should be
> taken with a grain of salt.
Okay, I've taken out all {eval} commands and replaced them by {include} or
simple {$vars}.
> if you want to use template from a database, write a resource-plugin
> for that: http://smarty.php.net/manual/en/template.resources.php
Done that before :) I've written a caching-function for the timestamps
yesterday, so that smarty will, under ideal conditions (no templates modified),
only use one query per page from now on :)
Well and just to have said... I've seen that I even had the mentioned
{section}{eval}{/section} inside another {eval}, so that php-ops got generated
on the fly by an eval'ed function - doh! Should have managed to realize that
earlier :)
Thanks again.
--
Dennis Freise <cat@final-frontier.ath.cx>
GnuPG key: 2DE8 CCEF 6E20 11D4 3B27 21EC B0BA 1749 D2C8 38ED
Available at: http://www.final-frontier.ath.cx/?key-plain
|