Bug #24273

help_aboutmoules hardcoded as start up module - returns error if uninstalled

Added by Soren Malling almost 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2010-12-02
Due date:
% Done:

0%

TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

With great features comes great responsibility ;)

As we are now able to uninstal former hardcodede extensions, some issues are shown.

If you uninstall the "aboutmodules" extension and haven't changed your "start up" module, the following error will be shown in the javacsript console/debug console

[string] help_aboutmodules was not found in modules

which is correct. The reason for this issue is at line 119 in t3lib/class.t3lib_beuserauth.php

var $uc_default = Array(
'interfaceSetup' => '', // serialized content that is used to store interface pane and menu positions. Set by the logout.php-script
'moduleData' => Array(), // user-data for the modules
'thumbnailsByDefault' => 0,
'emailMeAtLogin' => 0,
'condensedMode' => 0,
'noMenuMode' => 0,
'startModule' => 'help_aboutmodules', <------ HERE

The "aboutmodules" is hardcoded as startup module and only changed, if you as a user changes the settings.

What should be done here? Is it a administrator responsibility to change the default module for created users if he/she uninstall the default startup module?

(issue imported from #M16646)

16646.patch View (2.43 KB) Administrator Admin, 2010-12-03 00:06


Related issues

Duplicated by TYPO3 Core - Bug #24206: JavaScript console emitts: help_aboutmodules was not found in modules Closed 2010-11-25

History

#1 Updated by Steffen Ritter almost 9 years ago

think so, but this is more an usability issue, do you mind to report this issue to the usability guys at http://forge.typo3.org/projects/usability/issues,
if you post a short reference, it could be closed at this tracker.

#2 Updated by Steffen Kamper almost 9 years ago

This is a valid request. The same happens if you switch to a workspace: the defined start module may not be visible then and you get an error message.

I will provide a fix soon: if start module is not present, take first module instead.

#3 Updated by Steffen Kamper almost 9 years ago

Committed to trunk rev 9764

#4 Updated by Susanne Moog over 8 years ago

  • Target version deleted (4.5.0)

Also available in: Atom PDF