I think you are running into a limitation of the design of the session access counter implementation (i.e. an assumption that only one window will be used). Mostly my users utilise a single browser window. I do have a page that opens in a new window, in the template for this page I do this:
#set($newCount = $data.User.AccessCounterForSession - 1) $data.User.setAccessCounterForSession($newCount)
so that the original window works fine. This will only work however in situations where you know exactly what the user going to do in the new window (in my case there is nothing else for the user to do in the new window).
In your case I think you need to implement some other means of tracking outstanding form submissions. Perhaps you could hide a random key in the form and keep track of the form name and key in User.Temp, allowing only one key to be stored for each form name - on submit you can use the stored key to determine that the correct form is being submitted and remove the key so that a resubmit won't be allowed.
Regards,
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
Louis Moore wrote:
I guess I'll be able to fix the problem by implementing an invalid state template which will present users with a choice when this happens, to go back and re-submit if they wish.
Before I wasn't setting any invalid state screen or template which made the whole process transparent to users, which I much preferred.
So if anyone has any ideas as to how I could address this issue while still disguising it from the users I'd appreciate any feedback. Perhaps there is some way to detect a new browser opening and prevent the SessionAccessCounter from incrementing?
thanks,
Lou
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
