As suggested it is critical that multiple forms on the same name have different formname(s) and this is true even if the forms are LOADed because of the CSRF protection mechanism. Anyway, this one one case where you are looking for the wrong solution to the problem. You should use JS to generate those forms and submit them via ajax to different controller.
On Friday, 10 June 2016 16:54:51 UTC-5, Robert Pates wrote: > > Well, Thanks Anthony and Leonel for excellent suggestions -- > The issue went away when I ensure that each of the 16 forms generated had > a unique formname value. > However, I spent some time trying to combine this with Leonel's suggestion > to use ajax (with LOAD= ?). But didn't manage to figure that out in a > reasonable amount of time. If either of you could point me to the best > (mdipierro) web2py example appliance(s) to study to be able to examine a > complete application I'd be (even more) grateful -- > > > On Thursday, April 28, 2016 at 11:56:59 AM UTC-4, Anthony wrote: >> >> On Thursday, April 28, 2016 at 11:44:34 AM UTC-4, Leonel Câmara wrote: >>> >>> I would probably change the way the application works. There is >>> absolutely no need for you to have all the 16 forms in the HTML at the same >>> time and then try to process each one in the controller to see which was >>> submitted. Just load the form you need when you need it using ajax. >>> >> >> Note, if it's multiple copies of the same form, each form will still need >> a unique name in order to generate unique formkeys in the session. >> >> Anthony >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
