Bug #91679

Change sorting of records in list module / draft workspaces breaks workspace module

Added by This Mächler 26 days ago. Updated 26 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2020-06-19
Due date:
% Done:

0%

TYPO3 Version:
10
PHP Version:
7.2
Tags:
workkspace sorting
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

Same as #90073, but for TYPO3 10.4

This breaks the workspace-module functionality (doesn't load properly), up the whole tree, appears when I change the sorting of records in a sys-folder in list module. This sys-folder and all ancestors produce the bug when I open the list module.

The only way to overcome this redactionally is to edit something in a sibling page/folder and do a workspace mass action there. Else you are stuck.

Bildschirmfoto von 2020-06-19 05-32-36.png View - Language selection is dead / no items get loaded (19.9 KB) This Mächler, 2020-06-19 05:32


Related issues

Related to TYPO3 Core - Bug #90073: Change sorting of records in list module / draft workspaces breaks workspace module Closed 2020-01-09

History

#1 Updated by This Mächler 26 days ago

  • Related to Bug #90073: Change sorting of records in list module / draft workspaces breaks workspace module added

#2 Updated by This Mächler 26 days ago

The bug seems to have a different reason as the one in TYPO3 9 (no error report in the log).
I tried to fix it the same way as last time:

typo3/sysext/workspaces/Classes/Service/GridDataService.php, line 639:

/**
 * @param int*|null* $pageId
 *
 * @return array
 */
public function getSystemLanguages(*?*int $pageId){
...
}

But no luck (after clearing cache/op-cache/reloading browser). Still the language selection will not be loaded, no items and no chance to do a mass action (only solution: change something on a sibling page/folder and do the mass action there. All ancestor pages/folders will show the same issue).

See attached screenshot.

#3 Updated by This Mächler 26 days ago

  • Target version deleted (next-patchlevel)
  • Complexity deleted (no-brainer)

Also available in: Atom PDF