Currently, I find it a bit irksome that after installing the menu, I still have to navigate to the Block administration and clumsily replace the Navigation block with its DHTML counterpart.
Since Navigation is a core menu that is definitely there and definitely the prime candidate for a dynamic block if you install the module, could we be presumptuous enough to take over that step? The installation function could change the block settings automatically.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | dhtml_menu_autoreplace-188971-1.patch | 2.61 KB | cburschka |
Comments
Comment #1
cburschkaAs doing it without asking the user seems a bit too pro-active, this patch instead adds a "one-click" option that is displayed as a status message on enabling.
1. When the module is enabled, a status message pops up offering the user the choice to "enable DHTML for the main navigation menu". This links to a menu callback.
2. If the user visits the link, the module reads the values of the navigation block (user:1) for all themes, assigns them to the dhtml_menu:navigation block and disables the former. This effectively replaces the navigation block with its DHTML equivalent.
3. The module then redirects immediately to admin/build/block.
This patch adds an .install file for the hook_enable function.
Comment #2
brmassa commentedArancaytar,
code commited. Soon on the next version
regards,
massa
Comment #3
brmassa commented