Template Library Version 1.4.1

[eluser]Colin Williams[/eluser]

I don’t understand what you mean by “doesn’t exist”

Well, if the view file doesn't exist on the file system, Template tries the next one. Consider this use:

Code:

$post = $this->blog_model->get($id);
$this->template->write_view('content', 'blog/post-'. $id, compact($post), 'blog/post';

This means Template will fallback to the blog/post.php view. But, if you wanted to specially format a specific blog post, you could create a file called 'blog/post-23.php' and since that was your initial suggestion, it will automagically be used.

Just to clarify, are you saying I can use it with CI’s caching just as I would with a typical View?

Right. CI's caching is tied to the Output class. Template only interfaces with Views via the Loader class. So it does not interfere with CI's regular caching. If you were going to implement views-level partial caching, I would recommend overloading the Loader class. If you wanted to implement region-level partial caching (perhaps and interesting idea), then you would want to modify or overload the Template class.