Bug #10391

Submitting archival description with Safari results in 500 error

Added by David Juhasz over 5 years ago. Updated over 5 years ago.

Status:NewStart date:10/04/2016
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Information object
Target version:-
Google Code Legacy ID: Tested version:2.3
Sponsored:No Requires documentation:

Description

To reproduce:
------------
1) Login in to AtoM
2) Edit an archival description
3) Add a new place access point
4) Submit the form

Error:
-----
AtoM returns a 500 error

Expected result:
---------------
New place access point created and linked to archival description

History

#1 Updated by David Juhasz over 5 years ago

A check of the web server logs shows the user client (Safari) is submitting the form "POST" request to the server two times within a few seconds. A Google search returns several results for Safari double-submitting forms. http://stackoverflow.com/questions/3186304/form-submitted-twice-in-chrome-safari in particular suggests that Safari my require slightly different Javascript code than other browsers in order to prevent the default form submit() action, as we are doing in AtoM.

Also available in: Atom PDF