Bug #20773
closed
Main module does not load different navFrames in submodules.
0%
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
Updated by Marc Bastian Heinrichs about 14 years ago
The dam main module has its own navigation frame script (with two different get-var parameters for modules file and list) and the catedit module has a special submodule navigation frame script.
Steps:
A)
- web>page
- media>file (nav frame correct)
- media>list (nav frame correct)
- media>file (nav frame wrong)
Reload backend
B)- web>page
- media>categories (nav frame correct)
- media>file (nav frame wrong)
Reload backend
C)- web>page
- media>list (nav frame correct)
- media>file (nav frame wrong)
Reading from the code, it seems to me, that the different submodule navigation scripts (and parameters) are not evaluated, when switching submodules in between the same main module.
Updated by
Updated by Christian Kuhn about 14 years ago
- Committed to trunk rev. 7061
- Committed to 4.3 rev. 7062