I understand that duplicate posts have been a problem with forms forever.
I use the server side method to deal with this problem, but I believe that it does not work flawlessly. I have a system kit for creating a unique token for each form, and then writing this token to SESSION after its publication.
SESSION is an array of all forms that the user has ever posted (reset when SESSION expires), and each time the system submits, it checks in_array () to see if this form has already been submitted ... if so, it stops them .
It seems that in production, the system cannot write the completed token to SESSION fast enough to deal with double clicks on the submit button. Therefore, revising the old page handles fine, but immediately double clicking submit creates a problem.
Not sure what I can do to fix this problem.
swt83 source
share