TYPO3 Core

Are you using templavoila? Activate classic page module and try again. This seems to be caused by hardcoded "top.goToModule('web_layout');" in the workspace js.

Additional note: this happend for me only, if the current loaded module was not a 'web_xyz' module, e.g. user setup.

Quick fix: instead of forced web_layout, this switches to the first available module. So templavoila, regular page, list, file, ... whatever is available.

--- typo3/js/workspacemenu.orig.js 2010-07-21 11:27:27.000000000 0200
++ typo3/js/workspacemenu.js 2010-07-21 12:11:27.000000000 0200
@ -168,7 +168,7 @
// the boolean "true" makes the page reload from the server
$('content').contentWindow.location.reload(true);
} else {
- top.goToModule('web_layout');
top.goToModule($$('#typo3-menu li.menuSection:first-child > ul > li:first-child')[0].readAttribute('id').substring(8));
}

// reload the module menu

I can confirm that it does not happen with web_xyz modules.

Can confirm this issue with TV.

I will ask Stefan Galinski, if he has a cleaner solution. Does this also exist in 4.3?

The cleanest solution would be:

top.goToModule(TYPO3.configuration.pageModule);

The patch is currently on the way to the mailing list. Happy voting!

What if the user has no page module? A user could be limited to list or any other workspace-aware module.

You are right! That could really be a problem, but it's not a solution to redirect to the first available web module. Maybe we should define a fallback order or anyhting like this?

Probably: page, list, workspace? Other modules are most likely not available for a regular user (except News-Admin maybe). The start module for a user could be limited to live workspace, but at least that would be adjustable?

Committed to svn
4_4 rev 8296
trunk rev 8297