Bug #43158
closed
Sorting of parent records also moves inline childs
0%
Description
If the sorting of a parent record is changed the move method in TCEMain is also called for all its child records (inline elements) recursivly. But for the child records the destination pid is the current page id, so the sorting of the childs is changed to be the first item on page. This is not the expected behaviour and also results in very bad performance. This can be disabled in TCA by the behaviour flag disableMovingChildrenWithParent but this also disables real moving to other pages.
On sorting the moving of childs should be disabled, since it does not make sense here.
Updated by Mathias Schreiber over 9 years ago
- Target version set to 7.5
- Is Regression set to No
Updated by Jo Hasenau almost 9 years ago
Sorting elements in the background this way also leads to a weird behaviour of the l10nmgr export, which is currently purely based on the sorting field regardless of any nesting levels.
So you will get lots of child elements way before their respective parents in the XML file, which leads to serious context problem for the translators.
Updated by Mathias Schreiber over 8 years ago
- Category set to DataHandler aka TCEmain
- Target version changed from 7 LTS to 8 LTS
Updated by Benni Mack almost 7 years ago
- Target version changed from 8 LTS to next-patchlevel
Updated by Oliver Hader over 6 years ago
- Status changed from New to Accepted
- Complexity set to medium
Updated by Tymoteusz Motylewski almost 6 years ago
- Status changed from Accepted to Closed
I believe this was fixed together with https://forge.typo3.org/issues/85304 in v9 and v8 (backport is waiting)
https://review.typo3.org/#/c/57259/