https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page Gravity Support Forums Topic: Multiple notifications sent when refreshing confirmation page en-US Mon, 20 Apr 2026 21:31:18 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82422 Sat, 20 Oct 2012 20:06:41 +0000 webaware 82422@https://legacy.forums.gravityhelp.com/ <p>@tcs: thanks for testing, and good idea about custom error messages. I'll see what I can do this week, before I release this fix. Regarding multipage forms, it should already work OK because I set the form page to return to the page with the credit card field when invalidating it. This fix will work with both one-off and recurring payments, because the check is done before determining which payment type is required.</p> <p>@Gravity Forms: Steve is correct, the AJAX form method should really fall back to regular form submissions when JavaScript is disabled. For stopping form submissions, the unique ID should be a sufficient test if the website is single-hosted. I don't know how/whether you would add this to Gravity Forms core, but I'll be maintaining this fix in my plugin in the meantime (to be releases this week).</p> <p>cheers,<br /> Ross </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82323 Fri, 19 Oct 2012 23:44:41 +0000 tcs 82323@https://legacy.forums.gravityhelp.com/ <p>Hi Ross@webaware.</p> <p>Thank you for getting this fix out within the hour. It seems in that hour you have found a way to detect and stop accidental form resubmissions on the server side. Maybe the gravity guys could check this out. </p> <p>Your updated eWay plugin is now stopping duplicate payments through accidental form resubmisisons. I did not find a problem when I tested using a single and multi page form. On the multi page the credit card field is on the last page so I see the error warning. I suspect if it isn't on the last page your error may not display. They would see your form has errors see below and not actually see the error if the credit card field isn't on that page. Please also note I only tested with single payments not recurring (not sure if that makes a difference).</p> <p>Using ajax seems to stop accidental form re-submissions also but this may not be desirable for all users, In fact I setup a simple payment form and disabled javascript to see what happens. If you have ajax on it seems you are stuck as it doesn't degrade to a regular submit. You click submit and stare at the screen for a while before you realise nothing is going to happen. Turn ajax off and it works fine - duplicate payments nicely protected by your handywork.</p> <p>My only suggestion would be to look at the error message text or make it customisable in the admin. A customer may get quite baffled on what to do next when confronted with their accidental resubmission message. Something like - "Payment already submitted and processed - please close your browser window" to stop them refreshing again, back, forward and such. If that message could also override the generic large 'There was a problem with your submission. Errors have been highlighted below' message that appears at the top of the form it would be even better as they would definitely notice it no matter if the credit card field was on the page or not.</p> <p>So at this point for the folks at gravity forms:<br /> Thanks for your help so far:<br /> 1) If your not using ajax - can the problem of accidental form resubmissions through browser refreshes when using confirmation text be addressed somehow ?<br /> 2) If you do use ajax and customer has disabled javascript - shouldn't it degrade to a regular submit ? It doesn't seem to do so in my testing. </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82161 Fri, 19 Oct 2012 03:57:20 +0000 webaware 82161@https://legacy.forums.gravityhelp.com/ <p>I have a working fix, I would like to get your help testing it please. You can download an alpha of v1.2.3 from this URL and test. </p> <p><a href="http://www.webaware.com.au/files/gravityforms-eway-1.2.3-alpha1.zip" rel="nofollow">http://www.webaware.com.au/files/gravityforms-eway-1.2.3-alpha1.zip</a></p> <p>What it does is save the entry's unique ID in a meta value for the form, gfeway_unique_id, and checks to see if that value is present when validating the credit card information. If it finds it there, it invalidates the form with the following error message on the credit card field:</p> <p><code>Attempt to submit form multiple times; already processed.</code></p> <p>Please let me know how you go.</p> <p>cheers,<br /> Ross </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82160 Fri, 19 Oct 2012 03:48:15 +0000 tcs 82160@https://legacy.forums.gravityhelp.com/ <p>@webaware: I have AJax off so thanks for the tip - I will check with Ajax enabled. Yes also to a caching plugin (quick cache) however this is disabled on all form pages and I don't use it in my sandbox test environment and the problem is apparent there. </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82158 Fri, 19 Oct 2012 03:18:34 +0000 webaware 82158@https://legacy.forums.gravityhelp.com/ <p>@tcs: I just noticed I had AJAX form submission turned on, which avoids this problem.</p> <p>So, quick fix for most users: use AJAX form submission and they can't accidentally resubmit the form. Of course, this doesn't resolve the problem for users with JavaScript disabled / broken / limited by policies. </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82157 Fri, 19 Oct 2012 03:10:40 +0000 webaware 82157@https://legacy.forums.gravityhelp.com/ <p>@tcs: are you using a caching plugin? </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82152 Fri, 19 Oct 2012 03:02:47 +0000 webaware 82152@https://legacy.forums.gravityhelp.com/ <p>Scratch that, although GF generates a unique ID for a form entry, it doesn't actually store the bugger! If it did, it would be a simple matter to grab the saved lead with that unique ID; finding it saved would indicate that the form has been processed, so don't do it again (in fact, GF ought to be doing that itself).</p> <p>@Chris Hajer: once an entry has been saved, is there a way to test for that if the page is refreshed? A cursory look here hasn't found such a way. Storing the unique ID of the entry would help.</p> <p>I could work around this by storing the unique ID in my plugin's field data (thus complicating storage / retrieval of that data) or storing it in a separate, meta field (probably better as easier to search on), but...</p> <p>I can't actually reproduce the problem here on my browsers. I've tried a few times, but can't seem to make it submit another payment attempt; refreshing either brings up the confirmation again, or brings up a blank form. Steve, maybe you could email me the XML export of your form so that I could have a play with it. Maybe I need to try it specifically on Safari, which I have an old (5.11) copy on Windows or the mobile version on iPad.</p> <p>cheers,<br /> Ross </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-82144 Fri, 19 Oct 2012 02:18:40 +0000 webaware 82144@https://legacy.forums.gravityhelp.com/ <p>@tcs: I reckon the simple answer for your specific problem is if I modify the payment gateway to always check for a successful transaction number recorded in the form data, before submitting to eWAY again. I'll have a play with that and the result should be a new release of the eWAY plugin soon.</p> <p>cheers,<br /> Ross </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-81978 Thu, 18 Oct 2012 06:52:59 +0000 tcs 81978@https://legacy.forums.gravityhelp.com/ <p>I think refreshing any browser when you have the confirmation option set to text on a confirmation page is resubmitting the form data. Definitely on ie9 as well.</p> <p>I am happy to test 303 redirect (for my text based confirmation) to see if it stops form data being resubmitted when users click the browser refresh but how can this be implemented ? Is there some filter or hook - could someone at gf post the code ? If I switch from the text confirmation to a page confirmation does that use a 303 redirect?</p> <p>Thanks for posting the reading. It seems there are a number of ways to stop accidental resubmission and that it can be done if you want to. Is it on the road map at gravity forms? </p> https://legacy.forums.gravityhelp.com/topic/multiple-notifications-sent-when-refreshing-confirmation-page#post-81966 Thu, 18 Oct 2012 06:15:27 +0000 Chris Hajer 81966@https://legacy.forums.gravityhelp.com/ <p>I wonder if this is a problem with any form submitted with a page refresh, in Safari, as you described, or if it is somehow related just to Gravity Forms? If the problem is unique to Gravity Forms, I wonder how it's prevented with other form solutions (or forms in general.)</p> <p>How about using a 303 redirect on the thank you page?<br /> <a href="http://tumblr.jonthornton.com/post/7902581999/preventing-form-re-submission-with-http-303-redirects" rel="nofollow">http://tumblr.jonthornton.com/post/7902581999/preventing-form-re-submission-with-http-303-redirects</a></p> <p>More reading:<br /> <a href="http://bjw.co.nz/developer/general/75-how-to-prevent-form-resubmission" rel="nofollow">http://bjw.co.nz/developer/general/75-how-to-prevent-form-resubmission</a><br /> <a href="http://stackoverflow.com/q/2136954" rel="nofollow">http://stackoverflow.com/q/2136954</a> </p>