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: richardestallard[at]gmail.com [Submitted to the original trac issue database at 11.36am, Friday, 19th August 2011]
If the description of the save is more than about 2 lines, the save operation doesn't work and the edits can't be saved. It appears to be working but hangs for 20-30 seconds. Instead of the changeset number, the dialog indicate "Saving to changeset NaN" then "Failure when uploading data" and "HTTP request error".
Once the error has occured, trying to save again results in same error, but no abnormal delay.
Workaround is to keep descriptions short but this results in less information being provided for other users about edits being done.
I have classed this as major bug as it results in edits being lost.
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 1.02pm, Monday, 3rd October 2011]
Fixed in systemed/potlatch2@10b55b5 . The 255-character limit is standard with all tags in OSM (which include changeset comments), so you need to get used to keeping your descriptions short. :)
Reporter: richardestallard[at]gmail.com
[Submitted to the original trac issue database at 11.36am, Friday, 19th August 2011]
If the description of the save is more than about 2 lines, the save operation doesn't work and the edits can't be saved. It appears to be working but hangs for 20-30 seconds. Instead of the changeset number, the dialog indicate "Saving to changeset NaN" then "Failure when uploading data" and "HTTP request error".
Once the error has occured, trying to save again results in same error, but no abnormal delay.
Workaround is to keep descriptions short but this results in less information being provided for other users about edits being done.
I have classed this as major bug as it results in edits being lost.
The text was updated successfully, but these errors were encountered: