Bug #50310
closed
DataHandler fails to correctly re-sort (content) elements after moving one to top
0%
Description
Tested with v6.1.1, seems to affect 4.7.x too.
This occurs using drag&drop as well as calling the DataHandler itself.
While moving an element to top, its sorting will be set to 0 (the return value of getSortNumber called in line 3512), but the other elements' sorting is not updated. So if you move all elements to the top one after another, they all end up having sorting 0 and will be sorted by their uid instead.
Moving any one of those elements >down< will release the lock by reassigning valid sorting values to all affected content elements.
Best,
Bernhard
Updated by Philipp Gampe about 11 years ago
- Status changed from New to Accepted
- Target version set to next-patchlevel
- Complexity set to easy
Can you create a patch based on the code for moving an element down? http://wiki.typo3.org/Git
Updated by Mathias Schreiber over 9 years ago
- Target version changed from next-patchlevel to 7.4 (Backend)
- Complexity changed from easy to medium
- Is Regression set to No
Updated by Susanne Moog about 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Andreas Wolf almost 7 years ago
Is this probably a duplicate of/related to #68040?
Updated by Benni Mack almost 4 years ago
- Related to Bug #68040: Inline localize and/or synchronize does not respect sorting added
Updated by Benni Mack almost 4 years ago
- Status changed from Accepted to Needs Feedback
We've reworked the sorting in TYPO3 v10, can you re-check please with a more recent version if your issue still occurs? From reading the EXT:core code, other items are now resorted.
Updated by Christian Kuhn almost 3 years ago
- Status changed from Needs Feedback to Closed
Closing due to lack of feedback - it has probably been fixed meanwhile. If the issue persists, please re-open or create a new issue.