Bug #27181
Moving of nodes should not duplicate content
| Status: | Closed | Start date: | 2011-06-01 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Node handling | |||
| Target version: | Base Distribution - Sprint 7 |
Description
right now, the way moving of nodes is implemented has some drawbacks. If we have 5 nodes:
- Node1 (Sorting:1)
- Node2 (Sorting:2)
- Node3 (Sorting:3)
- Node4 (Sorting:4)
- Node5 (Sorting:5)
and then we move Node5 before Node1, this will lead to a complete re-numbering:
- Node5 (Sorting:1)
- Node1 (Sorting:2)
- Node2 (Sorting:3)
- Node3 (Sorting:4)
- Node4 (Sorting:5)
This will copy all nodes to personal workspace, although nothing changed.
- An idea would be to distinguish between content changes and further changes like moving or deleting nodes.
History
#1 Updated by Sebastian Kurfuerst about 4 years ago
- Category set to Node handling
- Priority changed from Should have to Must have
- Target version set to Sprint 7
#2 Updated by Sebastian Kurfuerst almost 4 years ago
- Status changed from New to Closed
Bulk-closing issues because they are
- not relevant anymore due to the sproutcore based backend
- or already implemented in the meantime.
Regards, Sebastian