Re: [SMARTY-DEV] smarty recompiling with op-code accelerators

--- Monte Ohrt <monte@ispi.net> wrote: > This isn't about dumping pre-compiled files from one server to > another, > that is certainly operational. The problem is when you clear the > templates_c directory, the files recompile but the op-code cache does > not pick up the changes (unless the original template timestamp > changed.) Ok. Still, clearing the templates_c dir is outside of the scope of Smarty--it doesn't have an API function for that, so again operational. Still, if it is easily supported... > IMHO, the compiled Smarty files should get a new timestamp, not the > same one as the originating template file. If you dump template files > from another server, it should be operational procedure to touch them > to be sure Smarty picks up the changes. I'd vote for this since it means less filesystem calls. This definately should be doc'd though--some people (precompiled file dumpers) will have to make sure they are doing the right things. xo boots