Project

General

Profile

Actions
Copy link

Bug #91127

closed

"Starting module" is never resolved from first available module

Added by Claus Due about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-04-19
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When UC is empty, the first available module is not detected since \TYPO3\CMS\Backend\Controller\BackendController::determineFirstAvailableBackendModule is never called. This is because $beUser->uc['startModule'] is always filled but does not get filled with the first available module from the list - rather, it gets filled with the last available module.

Note that EXT:dashboard must be uninstalled since this extension forces itself to be the default starting module and therefore hides the misbehavior.

Actions
Copy link

Also available in: Atom PDF