Caching Error on Example Page Fixed
2006.02.15 19:25
Some time ago I broke the example site by updating Templation and leaving an old cached copy of some of the pages in place. At some point I decided that Templation should ship with caching turned on. Of course one of the weakness of the caching system is that it doesn't take into account changes to the Templation source code itself, so if a buggy cached page is created it could stick around for a long long time.
In the case of the example page, turning caching on causes the DEBUG link to break (because it gets cached in the first state it sees). So the Templation site shouldn't be using caching at all.
Come to think of it no one should be using caching until they decide to turn it on. It's too likely to cause confusion while you're still trying to get your head around the page building process. A lot of sites will run great with caching off--it really is only necessary for humongously deep and sprawling sites or extremely popular sites bumping up against hosting limits.
Caching is now defaults to false in the Templation class. Hmm, this gives me a reason to push beta 4 out as soon as I can...
