Issue Bug Closed

#91127"Starting module" is never resolved from first available module

Claus Due 04/19/20, 13:57 updated 04/21/20, 10:43

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.

Reviews 1