Bug #18028
When installing an extension that contains a new backend module the module menu is not refreshed anymore when using backend.php
| Status: | Closed | Start date: | 2008-01-20 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Ingo Renner | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.2 | Is Regression: | ||
| PHP Version: | 4.3 | Sprint Focus: | ||
| Complexity: |
Description
When installing an extension that comes with a new backend module the module menu oes not refresh as it was the case with alt_main.php
Actually the class ModuleMenu is already prepared for partial rendering of the menu. The bad thing is that it is still based on an amount of old code. This code dynamically generates javascript code to define what happens when someone clicks a module link.
Now when partially rerendering the menu the javascript is not created for new modules - or at least not printed out which leads to the problem that the browser does not know what to do when clicking a module.
A possible solution could be to route all clicks on a module link through the server which then sends back what should be done - the actions should/may be cached.
(issue imported from #M7222)
reloadMenuOnExtInstall.diff
(10.7 kB)
setActive.txt
(501 Bytes)
Related issues
History
#1 Updated by Steffen Kamper over 7 years ago
very nice!
i attached a snippet to set the active state of menu item, you can include.
vg Steffen
#2 Updated by Ingo Renner over 7 years ago
this would belong to #18027 then. nevertheless this would not be enough as highlighting of a module can also change by calling a shortcut and jumping into a different module. We need to rebuild the old highlightModuleMenuItem() function.
#3 Updated by Ingo Renner over 7 years ago
patch is ready, will commit as soon as SF.net is back
#4 Updated by Ingo Renner over 7 years ago
committed to SVN trunk