[Templates-cvs] cvs commit: Template2/docsrc/src/Release Changes.tt2
cvs@template-toolkit.org
cvs@template-toolkit.org
cvs 06/08/01 17:35:42
Modified: docsrc/src/Release Changes.tt2
Log:
* Fixed bug in Template::Parser to ensure $self->{ DEFBLOCKS } is cleared
each time a parse() begins.
* Fixed bug in Template::Provider to immediately invalidate the cache entry
of any template that fails to compile.
Revision Changes Path
1.143 +23 -1 Template2/docsrc/src/Release/Changes.tt2
Index: Changes.tt2
===================================================================
RCS file: /template-toolkit/Template2/docsrc/src/Release/Changes.tt2,v
retrieving revision 1.142
retrieving revision 1.143
diff -u -r1.142 -r1.143
--- Changes.tt2 2006/05/30 17:14:17 1.142
+++ Changes.tt2 2006/08/01 17:35:42 1.143
@@ -20,8 +20,30 @@
# Any changes you make here may be lost!
#
#------------------------------------------------------------------------
-# $Id: Changes.tt2,v 1.142 2006/05/30 17:14:17 abw Exp $
+# $Id: Changes.tt2,v 1.143 2006/08/01 17:35:42 abw Exp $
#========================================================================
+
+#------------------------------------------------------------------------
+# Version 2.15c - ## DEVELOPER RELEASE ##
+#------------------------------------------------------------------------
+
+* Fixed a bug in Template::Parser which caused it to get confused about
+ block names if it encountered a syntax error inside a BLOCK. Thanks
+ to Bill Moseley for reporting the problem.
+
+ http://tt2.org/pipermail/templates/2006-July/008815.html
+
+* Fixed a minor buglet in Template::Provider which came to light while
+ investigating the above problem. If a previously cached template is changed
+ on disk and then fails to compile, the provider now invalidates the cache
+ entry immediately. Without this fix, the provider would report the error
+ once, then reuse the cached good version of the template until $STAT_TTL
+ ticked over when it would try to load and compile the disk version again.
+ The problem was that error messages were only reported once every $STAT_TTL
+ second(s) and any requests for the same template in the interim time would
+ mysteriously work. This way errors get reported consistently and immediately
+ and no-one has to waste an afternoon trying to figure out where the errors
+ went!
#------------------------------------------------------------------------
# Version 2.15b - 30th May 2006 ## DEVELOPER RELEASE ##