Bug #28974
Sorting of content elements fails in workspaces
Status: | Resolved | Start date: | 2011-08-15 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | Workspaces | Spent time: | - | |
Target version: | 4.5.8 | |||
TYPO3 Version: | 4.5 | Is Regression: | ||
PHP Version: | 5.2 | Sprint Focus: | ||
Complexity: |
Description
This behaviour occurs in TYPO3 4.4.9 as well.
Reproduction steps:
1. Create a test workspace
2. Live space: Create a page
3. Live space: Create two content elements within the new page
e.g.:
- Test1
- Test2
4. Change to test workspace
5. Test workspace: Move down the first element (Test1) - this works
e.g.:
- Test2
- Test1
6. Test workspace: Move down the second element (Test2) - this fails, the order does not change
Just guessing why:
The bug might be within the method t3lib_TCEmain::getSortNumber. It seems like the sorting relies on the sorting value from the live versions. That would explain why moving around a single item works fine, but when moving a 2nd item it fails.
Related issues
History
#1 Updated by Tolleiv Nietsch almost 4 years ago
- Status changed from New to Accepted
#2 Updated by Stefan Neufeind over 3 years ago
- Status changed from Accepted to Needs Feedback
Could you please see if I'm right this is a "duplicate" of the issue described in 31663? There is a patch currently under review. It would be great if you could try that out (only a few lines actually) and see if that solves the problem for you.
#3 Updated by Oliver Hader over 3 years ago
- Status changed from Needs Feedback to Resolved
- Target version set to 4.5.8
Handled in issue #31663
#4 Updated by Michael Stucki over 1 year ago
- Category changed from Bugs to Workspaces
#5 Updated by Michael Stucki over 1 year ago
- Project changed from Workspaces & Versioning to Core
- Category changed from Workspaces to Workspaces