Bug #20654
closed
Field defined as "sortby" in TCA doesn't support versioning
Added by Sven Weiss over 15 years ago.
Updated about 4 years ago.
Description
The field which I define in $TCA[$table]['ctrl']['sortby'] doesn't support versioning because it is hard coded to not support versioning. So it is not possible to publish a new sort order of elements.
In my case I want to give my editors the possibility to sort images in their workspace and then I want to publish it. But this doesn't work.
class.t3lib_tcemain.php - Line 4503:
...
// Find fields to keep
$keepFields = $this->getUniqueFields($table);
if ($TCA[$table]['ctrl']['sortby']) {
$keepFields[] = $TCA[$table]['ctrl']['sortby'];
}
...
On line 4540 there is the very curious reason:
// sortby is a "keepFields" which is why this will work...
(issue imported from #M11384)
- Assignee set to Oliver Hader
- Target version deleted (
0)
Additional Task:
If you have translated elements and sort them (especially if they are connected to their default language versions) you'll get a lot of funny effects. Try it: Create three default elements, translate them, and sort them up and down a bit. After some weird circumstances the sort order of the default elements changes, the translated elements jump in the default column, and everything gets really strange...
- Status changed from New to Accepted
- Category set to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Would be great to have this solved. Sorting elements inside a workspace is quite a common task imho (maybe during preparing a site for relaunch or so).
- Target version set to 7.5
- Target version changed from 7.5 to 7 LTS
- Target version deleted (
7 LTS)
- Assignee deleted (
Oliver Hader)
- Status changed from Accepted to Closed
Since TYPO3 v8 moving placeholders (= moving + sorting of records within a workspace) is enabled for all workspace-related records. This was introduced in TYPO3 v4.2 and is stable enough that it works. Just verified and your mentioned workflow is working as expected. I will close this issue now. If you feel there is still something that is missing, let me know and I will re-open the ticket.
Also available in: Atom
PDF