[EMAIL PROTECTED] wrote: > > On Fri, 18 Jan 2002 00:57, you wrote: > > [EMAIL PROTECTED] wrote: > > > I use HTML::FillInForm as well, but have found that you need to be > > > careful with your run-modes when using HTML::FillInForm. Even if you > > > statically add your runmodes to your templates, HTML::FillInForm will > > > 'rewrite' your hidden fields, including the runmode if the runmode was > > > part of the CGI query object. This is only really a problem if you > have > > > multiple forms on your page that submit to different runmodes. > > > > This issue was addressed in one of the more recent releases of > > HTML::FillInForm. From the docs: > > > > Suppose you have multiple forms in a html and among > > them there is only one form you want to fill in, > > specify target. > > Yes, I noticed that, but since I always statically include my runmodes in > the templates, I don't ever want HTML::FillInForm to change a runmode > variable.
Hello Cees, If you define the run mode statically in the template, then HTML::FillinForm should always re-fill it with the same static value. Besides the multi-form issue addressed by HFiF's "target" attribute, I can't think of another case where HFiF could do the wrong thing with a static run mode. -mark . . . . . . . . . . . . . . . . . . . . . . . . . . Mark Stosberg Principal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 223 website development . . . . . http://www.summersault.com/ . . . . . . . --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
