A little more progress - I can now predict when the problem will occur server side, before hitting submit. This is what I do:
1) clear all my web2py session files 2) open an incognito brower 3) go to the page with multiple ajax forms 4) take a look at the new session file. If it looks like this: (dp1 S'_formkey[formname2]' p2 S'e1983c3d-2695-4383-8ea4-f32d0687a0eb' p3 sS'_session_hash' p4 S'f36cc8f46f69c9d7b245d52c5630a427' p5 s. I know that the first submission for form 1 will fail. Once I submit it once, '_formkey[formname1]' is added to the session dictionary and it works from then on. Does this give any more clues? On Monday, 22 April 2013 15:44:21 UTC+1, Neil wrote: > > Good suggestion - I think we may be getting somewhere. When it fails, the > server is getting a '_formkey[formname2]' when submitting form 1. I'll try > to dig a little deeper. > > -- --- 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/groups/opt_out.
