Project

General

Profile

Actions

Bug #20773

closed

Main module does not load different navFrames in submodules.

Added by Christian Kuhn almost 15 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2009-07-20
Due date:
% Done:

0%

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

Description

This bug was introduced by #19202 to current trunk (rev. 5729):

Changing submodules doesn't always reload the navFrame. This is the same behavior as described in #19202 which was solved in 4.2.2.

Reverting typo3/classes/class.modulemenu.php to revision 4591 and typo3/js/modulemenu.js to 3266 (last versions before #19202 was applied) solved the issue.

Test:
You can easily test this with commerce in current trunk (with uncommented XCLASS of typo3/classes/class.modulemenu.php in ext_localconf.php): Category, Orders and Systemdata all have different navFrame scripts, they are not called if you select the commerce modules in a row, but if you choose another module (eg. page) in between and then back to a commerce module the correct navframe will be loaded.

(issue imported from #M11562)


Files

11562.patch (1.79 KB) 11562.patch Administrator Admin, 2010-02-20 15:33

Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #19202: Framehandling problem with FF 3ClosedBenni Mack2008-08-08

Actions
Related to TYPO3 Core - Bug #19034: navFrameScript is not loaded for submodulesClosedOliver Hader2008-06-28

Actions
Related to TYPO3 Core - Bug #22395: Main module does not load different navFrames in submodules in dependency of navFrameScriptParamClosedDmitry Dulepov2010-04-07

Actions
Related to TYPO3 Core - Bug #18011: Navframe does not proper reloadClosed2008-01-17

Actions
Actions

Also available in: Atom PDF