I just double posted in this thread.
I thought that was impossible these days.
Are we cloning the hamsters?
I just double posted in this thread.
I thought that was impossible these days.
Are we cloning the hamsters?
I’m not sure of the exact mechanism used by vB when a person submits the post, but the way we have it set up now is to avoid posts with different submit/post IDs writing to the database within a certain frame of time (all submitted by the same user). That should stop the majority of double-posts where the user has hit the ‘submit reply’ button multiple times.
That might not, however, defeat an error produced by other means, such as a mistake made by the database in processing a queue buildup. Your double-post was probably just an anomaly.
It was an accidental double-hit of submit reply. I’ve done that in the past with the “you can’t post more than once every 60 seconds” notice coming up. That didn’t happen so I assumed I was correct in that the first hit wasn’t recorded. Until I saw the thread. Just reporting it, if, in case, you know.
Oh, okay. I just assumed it wasn’t a double-hit. I’ll take a peek at the settings to make sure that 60 second timing is still in effect. Thanks for the heads-up.
Test
Well, the 60 second flood control setting is still active, but I re-saved the settings just in case. I tried submitting a double-post with auntie em’s account (mod accounts are free from the 60 second limitation), but got the usual “uh-uh, can’t do that” message. So, it seems to be working; if you notice it again, please let us know and we’ll see if there’s something we can do from our end to fix it.