Empty "upload GPX file" box on upload page does not give meaningful error #543
Comments
|
Author: tom[at]compton.nu Umm... how could it be populated on the error page? are we supposed to guess what the name of your trace file is? Obviously the 500 error is something that needs fixing - I suspect I know what the cause is and I'll try and look at it later on along with your other bug. |
|
Author: tom[at]compton.nu Oh - I see what you mean - you want it populated on the original error page when there was no description. That might be hard, because I'm not sure if the browser sends the full pathname when doing a file upload (to be honest, it probably shouldn't from a security point of view). |
|
Author: openstreetmap[at]phillipsuk.org I wasn't sure if the file name could be populated on the error page or not. I don't see that as a big issue, but I'd highlight the file box as well as the description box, so that it's obvious to the user that they have to re-enter the file name. Otherwise most people will just add a description and then get an error because there's no file name (that's what I did) |
Reporter: openstreetmap[at]phillipsuk.org
[Submitted to the original trac issue database at 12.34am, Friday, 21st September 2007]
On the GPX upload page (http://www.openstreetmap.org/traces/mine), if the "description" or "tags" box is empty, it returns an error. But, if the "Upload GPX File" box is empty (as it defaults to when this error appears), the following message appears:
Application error
Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html
This appears to be a default Ruby error message - would be better to give the user a meaningful error message.
Also, would be better if the "Upload GPX File" box on the error page was already populated, or it was highlighted to make it obvious that the file needed to be re-selected.
The text was updated successfully, but these errors were encountered: