Quoting Ian Bicking <[EMAIL PROTECTED]>: > It hasn't been working for you? As long as you give both > the forms > different names, it should work okay. Well, there may be > bugs, but I > don't think any more interface should be required. > > Each form puts a _formID_ hidden variable in the form, so > only one > _formID_ should show up on a submit, which is what > processForm looks > for. So it will only ever process a single form... if > more than one > _formID_ shows up it should just barf, so there won't be > double submits. > > What's the problem you're having with this?
The problem is when you have two separate calls to processForm, with intent to print info out at that time. We find this to be a valid design decision, particularily when one of our calls happens to be sitewide (sidebar login box, etc) and we want another form on the page for orders or whatever. It's not whether there's a valid _formID_, it's whether it's the formID we care about *at that point* in the code. I've created a simple example that breaks with current behavior, and doesn't with the simple modification I suggested. http://www.exodusgroup.net/test/formTest.txt is the code and http://www.exodusgroup.net/test/formTest.py is it in action. Thanks, - Luke ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
