It seems that newly added endpoints cannot be sorted until the Edited entity is saved.
Expected behavior:
1.
Add endpoints, sort them amongst the others, and save. Relation Select fields handles add, sort, and save in one operation.
Actual behavior:
1.
Add endpoints, sort them amongst the others, and save. Relation Select field does not save new endpoints.
2.
Add endpoints, sort them amongst themselves or do not sort them, and save. Relation Select fields handles add, new sort, and save in one operation.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | relation_select-cannot-sort-endpoints-before-saving-1826538-4.patch | 2.93 KB | Canu667 |
| #2 | relation_select-cannot-sort-endpoints-before-saving-1826538-2.patch | 1.13 KB | steveoliver |
Comments
Comment #1
steveoliver commentedNew fields are unindexed array items, and when pushed in the mix with the integer indexed array, each new row gets overwritten by the existing numeric row.
Comment #2
steveoliver commentedThis seems to work for me.
Comment #3
reaperdk@boss commentedThis path does not work for me.
Comment #4
Canu667 commentedThe attached fix works for me. I partially used the previous patch. Had some problems with adding then removing an element, so I added an additional operation of reindexing the array in Javascript after an element is removed.
Comment #5
steveoliver commentedMarking this a duplicate of the now Fixed issue #2666006: Newly added relation, when being re-ordered from last position, does not get saved.