Task #84658
closedDo not change sorting when record gets deleted
100%
Description
There seems no actual advantage of updating the field defined in sortby TCA ctrl section when a record gets deleted.
Updating the field leads to problems when restoring a whole page with recycler.
Steps to reproduce:
- Install recycler extension
- Create a new page
- Add two content elements to it
- Delete the whole page (the content elements get also deleted)
- Restore that page with sub-records using recycler
The result is, that the content elements both has sorting set to 1000000000. So the original sorting is completely lost. When removing a page with some more content elements, then the to re-arrangement can take some time.
Updated by Tim Schreiner over 6 years ago
I have created a patch for this. Unit and functional tests are all running, after changing the expected sorting.
Will now check acceptance and do some manual testing. When everything is fine, I will push the patch to review.
Updated by Gerrit Code Review over 6 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56609
Updated by Tim Schreiner over 6 years ago
- Tracker changed from Feature to Task
- TYPO3 Version set to 9
Updated by Gerrit Code Review over 6 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56609
Updated by Tim Schreiner over 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 9bdbb3665934a5bbd46d557fa0560cefaf3d16b1.