Bug #22395
closed
Main module does not load different navFrames in submodules in dependency of navFrameScriptParam
Added by Marc Bastian Heinrichs about 14 years ago.
Updated almost 14 years ago.
Description
DAM module file has the configuration $MCONF['navFrameScriptParam']='&folderOnly=1' , but the list module not.
If you switch between these modules, the nav frame isn't reloaded.
related to #20773
(issue imported from #M14026)
Files
Generic solution is not possible. There are two use cases here:
1. Navigation frame must be reloaded (DAM case, #8695)
2. Navigation frame must not be reloaded (all standard Web & File modules)
If the navigation is reloaded in standard modules, the tree will lose its selection + it will be unnecessary extra requests + slower than it is now. Thus every module should indicate if it needs to reload navigation frame. Currently it is possible by specifying 'navFrameScript' in $MCONF. See also #14207.
In addition to my previous note: navFrameScriptParam is not currently passed to module list generation script in the core. Probably this is a cause of this bug. I'll see how we can change it. Currently the solution is to include parameters to navFrameScript and make navFrameScript unique if you want to reload the tree.
revisions 7449, 7448, 7447
Also available in: Atom
PDF
Updated by