CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Support #5236

Going back in browser after submit => form not reloaded

Added by Veronica over 3 years ago. Updated over 2 years ago.

Status:Resolved Start date:2009-11-05
Priority:Should have Due date:
Assignee:Reinhard Führicht % Done:

0%

Category:Controller
Target version:Beta 4 (v0.9.7)
Votes: 0

Description

Not sure if this is a bug or a problem of my setup:

When a user fills out the form and submits it, he sees the success page, where he's shown some info on his registration (e.g. his name). At the same time, an e-mail is sent to both the user and the admin, and the registration is saved in the database. All right so far.

However, when he then goes back using the browser history back function, he is presented with the filled out form from before once more. He can do some changes (e.g. enter a different name), submit the form again, and will see the success page again, with the changed registration info. The problem is, formhandler does not create a new registration for this second submit. It's as if it never happened (no e-mail sent out, no entry in the database). The user never realizes that he can't just go back like this because there's no reload error, and he even sees a correct success page, with the new information he entered.

Any idea what to do about this? This is a problem for me because I use formhandler for a registration form, and sometimes users will want to submit registrations for several people (e.g. one person registers all the participants from his company).

History

Updated by Reinhard Führicht over 3 years ago

  • Category set to Controller
  • Assignee set to Reinhard Führicht
  • Priority changed from -- undefined -- to Should have

It is on purpose that the second time no email gets sent and so on.
But it is not on purpose that the user can go back.

I would say that when the user goes back after successful submission the information page is shown or the initial view of the form without values filled in.
The reason for not sending the emails and so on the second time is, that the user can just reload the form. In this case, the finishers shouldn't be called again and agin.

I will have a look at this issue in the evening.

Updated by Reinhard Führicht over 3 years ago

  • Status changed from New to Accepted
  • Target version set to Beta 4 (v0.9.7)

I will rename Finisher_Confirmation to something less confusing.

Fact is:

  • A real confirmation page must be done by yourself using an additional step in your form.
  • Finisher_Confirmation actually shows a "The form got submitted successfully" page and therefore will be renamed.

PS:
The reloading issue is fixed by now.

Updated by Veronica over 3 years ago

Reinhard Führicht wrote:

I will rename Finisher_Confirmation to something less confusing.

Fact is:

  • A real confirmation page must be done by yourself using an additional step in your form.
  • Finisher_Confirmation actually shows a "The form got submitted successfully" page and therefore will be renamed.

PS: The reloading issue is fixed by now.

Yes, that makes sense. Thanks for the heads up!

Updated by Reinhard Führicht over 3 years ago

  • Status changed from Accepted to Resolved

Finisher_Confirmation was renamed to Finisher_SubmittedOK.
Changes committed to trunk

Also available in: Atom PDF