I did not try reproduce this but I can see a race condition caused by the browser. I make a guess.
When the page is loaded there is no session. Depending on the browser it performs two ajax loads. There are three concurrent requests, the outer page, and the two ajax requests. There is noway to tell in which order the complete not if one of them completes before the other two. Each of them gets issued a session. None of those requests knows there is another request going on handled in parallel by another thread. The last session returned is stored in the cookies and the other ones are forgotten. My guess is that if you have a landing page without ajax and then redirect to the page in question, there is no problem. If my guess it right this cannot be fixed unless there is a js way to make sure ajax requests are executed after the outer page has stored the session cookie. Massimo On Sep 19, 10:17 am, DenesL <[email protected]> wrote: > When the initial LOADs execute, two session files are created and each > holds the appropriate formkey for each form. > > But on submit one of the session files is never read or updated again, > hence the corresponding form does not accept. > > Almost sure this is bug, I just don't know where. > > Denes.
