TYPO3 Core

so where's your patch you were talking about, Franz? BTW: did you notice that nobody else has this problem?

Hello Ingo, the patch to be discussed is on the English Mailinglist. You refused to having it added on the 4886 site.
I do not know who has tried out my reproduction steps so far. There has not been any response yet to these reproductions steps on a completely new install without any database and with no extensions installed.

Franz, as long as the ptch is not attached here, it officially doesn't exist.

I can reproduce this bug since revision 2330 from svn. If I downgrade to rev. 2321, everything works fine.

(Firefox 2.0.0.3 on Ubuntu Feisty)

I can reproduce the problem:

grabbed a fresh svn checkout an hour ago and none of the backend modules worked. After applying the attached patch, everything works as expected.

Please test the attached patch 0005655.diff

The reason is $GLOBALS['BE_USER']->uc['noMenuMode']:
If this information was never changed is has the value "0".
The evaluation was done the following way because of the missing type check:

$GLOBALS['BE_USER']->uc['noMenuMode'] == 'icons'
// 0 == 0 -> thus, the statement was true and used topmenuFrame instead of menu

The file 0005655_v2.diff fixes another problem on the initial login to the TYPO3 backend. In alt_main.php there is a call to e.g.

window.setTimeout("top.goToModule('help_aboutmodules',false,'');",1000);

Hello Oliver, yes it would work also with your patch.

$GLOBALS['BE_USER']->uc['noMenuMode'] = 0

if ($GLOBALS['BE_USER']->uc['noMenuMode'] 'icons') {
has resulted in TRUE in this case, which it shouldn't.
The string 'icons' seem to have been converted into an integer before the comparison. Therefore it has been '0 0).

Committed to SVN Trunk (rev. 2349)