This only happens when the order you submit has the same counter number as your previous command. The counter field is a hidden form element on every order submitted; It exists purely to prevent people accidentally submitting a form twice, or hitting refresh, and executing a command twice unintentionally.
The other thing which causes it is Cirdan's Battle Mines widget, which causes your stored counter to increment beyond the next order you submit, triggering that response. There's currently no workaround.
Oh. I thought it was telling you to repeat the order to be certain that's what you want to do. It normally warns me the first time and then when I click again, it submits it without a problem - which seems to be the opposite of what you've said
Post by vilhazarog on Jan 30, 2006 13:47:00 GMT -5
No one has the widget but Rast and me, so don't worry about that.
You might be getting this behavior if you are playing battle mines in multiple windows.
So if you do something in one window, then open up another browser to check on something, then go back to the original window... that original window is now out of date. So when you submit it gets rejected. Then the window is up to date again, so when you submit again you are ok. This would also apply if you were using something like firefox and playing battlemines inside multiple tabs.
Rast, the common design pattern to solve this kind of problem is to create a unique session cookie on each login. Then associate the counter with the session cookie. This way people can have multiple sessions without them interfering with each other. This kind of thing is usually built into applications servers, and it looks like it's built into php, see: us3.php.net/session
But its not that big a deal, so probably not a high priority.