Opened 15 years ago

Closed 14 years ago

#2353 closed defect (fixed)

Wrong relation upload order results in 512 Precondition Failed

Reported by: Candid Dauth Owned by: team
Priority: minor Milestone:
Component: Core Version:
Keywords: Cc:


When I create two relations and add one of them as a member to the other, sometimes the upload order is wrong and the one that has the other as a member is uploaded first. This of course results in a 512 Precondition Failed, as the relation has a member that does not (yet) exist.

JOSM should either correct the upload order (but what if two relations have each other as a member?) or upload changed and created relations first without adding members that were created and then, after uploading all changes, re-upload those relations and add the newly-created members.

Attachments (0)

Change History (1)

comment:1 Changed 14 years ago by Gubaer

Resolution: fixed
Status: newclosed

(In [2168]) fixed #3304: Upload failed - Placeholder Relation not found
fixed #2353: Wrong relation upload order results in 512 Precondition Failed
Warning: this is going to break plugins which register Upload Hooks. These plugins will be fixed shortly.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.