On Mon, May 02, 2005 at 01:39:40PM -0500, Paul Jimenez wrote: > Existing cheetah code now causes a traceback: > ... > Looking at the code, it looks as if *ErrorCatcher methods might have > been moved from Parser.py to Compiler.py without the calls to them > in eatErrorCatcher getting fixed.
Did you recompile your templates? If not, please do so. There were
changes to the compiled python code that are not portable from 0.9.15.
Check the README.Debian and NEWS files for details. Additionally,
here is a recent post on the cheetahtemplate-discuss about
ErrorCatcher::
From: Tavis Rudd <[EMAIL PROTECTED]>
Re: Security hole in Cheetah?
2005-04-26 14:10
ErrorCatcher is a debugging tool and was never meant for use in
production systems. What would lead you to have NotFound errors in
production?
On Tuesday 26 April 2005 02:20, Brian Bird wrote:
> If nobody uses errorCatcher, perhaps there"s a better way to
> achieve what I"m trying to do?
>
> I want any $placeholder variable to be replaced by a blank string
> if it cannot be found in the namespaces, instead of raising a
> NotFound exception. I"ve done some digging and the best
> suggestion seems to be to put something like th
...snip...
http://sourceforge.net/mailarchive/message.php?msg_id=11589131
--
Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
signature.asc
Description: Digital signature
