> David Kaufman wrote: >> Lance A. Brown <[EMAIL PROTECTED]> wrote... >>> >>> Error executing run mode 'main': HTML::Template : Attempt to set >>> nonexistent parameter '</div>' - this parameter name doesn't match >>> any declarations in the template file : (die_on_bad_params => 1) at >>> SwitchManager.pm line 84 > >> ...can you post a bit of the relevant code ? > > Here you go: [snip] The call to $main_tmpl->param(...) is line 84. > > I'm attaching the template file. Could I be running into some caching > issue with mod_perl?
well, nothing jumps out at me. i see you like to use CGI.pm's html-form construction methods, which i never use, so i may be missing something there... could your $q object be getting global somehow? if it's not properly scoped with my() properly it could certainly survive and keeps it's old values from request to request, though that seems unlikely using CGI::App, which cleans up it's $self->query() property... you are using CGI::App's ->query method, aren't you? or, if not, at least my()-ing your $scalar = new CGI? the easiest way to eliminate mod_perl as the culprit is to simply test the script in exec-cgi mode, and see if you can reproduce the behavior. a single .htaccess directive: <Files *.cgi> # (or *.pl) SetHandler cgi-script </Files> can at least remove the mod_perl mystery from the equation. -dave --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
