CMS Made Simple Forums

Ted wrote: It's using smarty for caching.  Basically, it keeps a cached version of the compiled smarty template in tmp/templates_c and only goes out to the database to get another version of the template(s) if they're timestamps are older than the ones in the database.

(The word template in smarty is different from CMSMS's usage.  It's meaning any chunk of text that smarty needs to process.  A content block, global content block, template or any templates used by a module fall into this category.)

Ted wrote: Templates cache, but the actual content shouldn't.  In the case of modules, that would mean that anything like {$title} should be created everytime.  It's just that the compiled template would have an echo $title; instead of {$ititle} in it. 

Does that make any sense? (it's still early here.  )

Ted wrote: If module output cached, there would be no way for the smarty to know the content updated just by looking at templates.  You could then have it cache the output based on rules from the module knowing when content has changed or whatever, but it just makes it too difficult to code a simple module.

We do our best job to mix caching, dynamicism (probably not a real word) and ease of development.

And to be honest, real caching of the output doesn't speed it up that much (we've tried it).  Including files is slower than easy sql queries... at least in php.

The only way to get it REALLY fast is to output static html and skip the php stuff all together.  But then you really lose your dynamic abilities.

Ted wrote: If module output cached, there would be no way for the smarty to know the content updated just by looking at templates.  You could then have it cache the output based on rules from the module knowing when content has changed or whatever, but it just makes it too difficult to code a simple module.

We do our best job to mix caching, dynamicism (probably not a real word) and ease of development.

And to be honest, real caching of the output doesn't speed it up that much (we've tried it).  Including files is slower than easy sql queries... at least in php.

The only way to get it REALLY fast is to output static html and skip the php stuff all together.  But then you really lose your dynamic abilities.

Ted wrote: It's actually something different.  Smarty then has this extra ability to cache the actual html ouput of the templates.  However, it's just an extra step that really doesn't gain us much, given the nature of the system.  Because everything that's inside a {} doesn't technically cache (at least in smarty's way to seeing it), the tempaltes and the cached output would basically be exactly the same....just with more disk I/O time.

Maarten wrote: Isn't it an idea to render a HTML page after each safe. For example you edit some content and when the user press  save the system creates a static page which can be loaded until a new edit has been made. offcourse some element like time can be a problem.