Posted by Matthew Weier O'Phinney on 07/14/05 16:20

* "Christopher J. Bottaro" <cjbottaro@alumni.cs.utexas.edu>:
> I tried the following:
>
> $smarty = new Smarty();
> $smarty->caching = false;
>
> but stuff is still being written to the compile_dir. It wouldn't be a
> problem, but I'm editing my templates via a Samba share and the times are
> synced between computers and thus Smarty isn't seeing my changes.

Compiling != caching. Here's how Smarty operates when caching is off:

* Checks to see if a compiled version of the template is available, and
that it is newer than the template
* Yes?
* Loads the compiled code
* Loads assigned variables, configurations
* evals the compiled code
* No?
* Loads the template file
* Compiles it into PHP code
* Stores the compiled PHP code in the compile_dir
* Loads assigned variables, configurations
* evals the compiled code

Template compiling is what makes Smarty fast on subsequent calls, and is
a necessary step in the process. Caching is considered optional.

If you're having problems with the timestamps, consider using NTP to set
the clocks on your systems so that they're synchronized.

--
Matthew Weier O'Phinney
Zend Certified Engineer
http://weierophinney.net/matthew/

[Back to original message]