You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: malenki [Submitted to the original trac issue database at 4.18pm, Sunday, 27th February 2011]
Uploading a GPX-log with "bad" characters in the Tag field result in this error message:[[BR]]
Could not save track: an error[[BR]]
Please check following fields[[BR]]
*tags not valid[[BR]]
(translated from german)[[BR]]
After correcting the entry in the tag-field one has to upload the log anew.
Why can't the tags be checked before the upload starts? [[BR]]
Or why can the tags not be corrected without having to upload anew?
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 3.32am, Tuesday, 1st March 2011]
Well we can't "correct" a tag because we don't know what the user meant!
Validating them is equally hard because we don't get to see them until the form has been submitted. In theory you could pre-validate in javascript, but trying to do something that exactly matched the rails validations on the server side might be fiddly.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: malenki
[Submitted to the original trac issue database at 4.18pm, Sunday, 27th February 2011]
Uploading a GPX-log with "bad" characters in the Tag field result in this error message:[[BR]]
Why can't the tags be checked before the upload starts? [[BR]]
Or why can the tags not be corrected without having to upload anew?
The text was updated successfully, but these errors were encountered: