Re: [SMARTY-DEV] Clear templates and cache
| From: | pete M | Date: | Fri, 09 Jul 2004 15:29:58 +0000 |
| Subject: | Re: [SMARTY-DEV] Clear templates and cache | ||
| References: | 1 2 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-2482@lists.php.net to get a copy of this message | ||
Boots wrote:
--- Mark Rogers <mark@quarella.co.uk> wrote:-------------------- It would bepete M writes:I dunno. This is very close to what I do (though I default to false), but I would rather keep it out of the base class. If an appropriate method gets documented in the manual that should be fine.Do you mean what boots mentioned >>>Yes.Like this idea ;-) $smarty->version_flush = true;
nice to eventually have a website with a repository of plugins/extended classes/etc but the wiki is suitable for now.There's a Tiki (tikiwiki.org) at http://smarty.sourceforge.net/tiki-index.php the idea was that users could register and upload files/modifiers et all tiki can also import the original wiki and I also think the forums
The reason I don't want it in the base is that it will be hard to agree on the minimal number of housekeeping chores that should be included in the base. Because my apps can live on alternate machines and alternate environments, I do more than just version checking--I also do safe mode checking and also do is_writable/etc hadnling when creating the temp directories and version files. Splitting that up into multiple functions/options is just getting a little silly to me though I'm sure others might like to do so. Thus, I vote to leave this as a user option. xo boots