Modify ↓
Opened 17 years ago
Closed 16 years ago
#2568 closed defect (fixed)
No warning upon exiting JOSM with unsaved data after failed upload
| Reported by: | framm | Owned by: | team |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | Gubaer |
Description
Ed Loach reported a problem on the dev list which was mainly about JOSM not noticing a concurrent deletion and thus not uploading (we have open tickets for that), but also said in
http://lists.openstreetmap.org/pipermail/dev/2009-May/015454.html
that even though is upload failed, he did not get a warning message on exiting JOSM and subsequently lost his edits.
A JOSM version number was not given.
Attachments (0)
Change History (2)
comment:1 by , 17 years ago
| Cc: | added |
|---|
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This is most likely solved in the meantime.
In r2025 a new approach for checking for unsaved modifications before exiting JOSM was introduced.
Note:
See TracTickets
for help on using tickets.
Probably related to #2437.
Error messages due to failed upload are easily overlooked because they are not displayed with an error icon and because they often don't include the word "Error". A typical message is
version mismatch provided 4, server had: 5 of way 123456789.There isn't clear warning either that the data wasn't saved on the server.