RA Jones writes: > George Hartzell wrote: > > RA Jones writes: > > > OK, thanks. So the behaviour is caused by FillInForm, and nothing to do > > > with CAP::Forward. I did see something about ignore_fields but missed > > > its significance. Makes me wonder if FiF is optimally suited for use > > > with multi-form web-pages using hidden fields called rm. > > > > > > And can already confirm initial trial using ignore_fields seems to be > > > doing the right thing. Many thanks. > > > > I tripped over this a couple of weeks ago and Cees replied with the > > hint that one can have FillInForm only fill in a particular form, > > which should solve the problem. > > > > I'd already stumbled over the ignore_fields solution and it "worked" > > well enough for me, so I haven't checked out his suggestion. I've > > attached his message in case it's an interesting alternative for you. > > > > g. > > Hi, yes I saw that exchange and made a hard-copy of it for future > reference, and that is what I was referring to when I mentioned missing > the significance of ignore_fields. I haven't tried using the named forms > option yet (target => 'form_name') as I imagine I would still get caught > by all the other rm's being re-named to the current rm, or is that what > the named forms option is designed to prevent?
My understanding is that it will do exactly that: prevent any of the fields (hidden or otherwise) in any form except that one that was specifed from being changed. In other words, it should leave everthing alone except that fields in form which you specify. I'm don't have access to my dev system at the moment, so I can't give it a try.... g. --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
