On 3/15/07, David Christensen <[EMAIL PROTECTED]> wrote:
Jason Kohles wrote: > It looks like you've turned on debugging in Template, either > DEBUG_UNDEF or DEBUG_ALLYup: 2007-03-14 22:09:33 [EMAIL PROTECTED] ~/MyApp $ grep -i debug lib/MyApp/View/TT.pm DEBUG => 'undef', I put in there per the tutorial (http://search.cpan.org/~jrockway/Catalyst-Manual-5.700501/lib/Catalyst/Manual/Tu torial/CatalystBasics.pod): TIP: When troubleshooting TT it can be helpful to enable variable DEBUG options. You can do this in a Catalyst environment by adding a DEBUG line to the __PACKAGE__-config> declaration in lib/MyApp/View/TT.pm: __PACKAGE__->config({ CATALYST_VAR => 'Catalyst', ... DEBUG => 'undef', ... }); Taking it out fixes the problem. :-)
It was my hope that this warning would help people remember to turn it off: NOTE: Please be sure to disable TT debug options before continuing the tutorial (especially the 'undef' option -- leaving this enabled will conflict with several of the conventions used by this tutorial and TTSite to leave some variables undefined on purpose). Let me know if anyone has a suggestion on how to improve the wording. Maybe I will change "TIP: When troubleshooting TT it can be helpful to enable variable DEBUG options." to "TIP: When troubleshooting TT it can be helpful to enable variable DEBUG options (you can experiment now, but please remove these options before continuing the tutorial)." to essentially create a "warning sandwich" before and after the example. Thanks, Kennedy _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
