Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Your menu block (navigation) better to be Drupal friendly - i mean - it is not possible mow to move it and configure in and between blocks and it uses other classes format - not possible to use it with DHTML menu for example - it expects some classes like "menu", "leaf", "collapsed" and so on.... i think that are standarts for Drupal UI
But I didn't catch what was changed really yet... it seems main-menu links still not possible to move or disable between blocks - and also your menu cannot work with levels - they don't show ( deeper than first :))
hey, maybe they can't be moved because I put then hardcoded in the page template (like Bartik), if you want to be able to move them they should be used as blocks, maybe I'll do that instead have them as blocks in the header region as default... hang in there gonna work on this today! :)
Hey pyotrpro, after a couple of hours of testing and hacking to try and get this to work I've come to the conclusion that it works exactly as designed.
The "problem" here is that the behaviour you expect comes from a block, whereas in page.tpl.php the menu is being shown according to Drupal Core's $main_menu variable. The same behavior occurs in Bartik and Stark.
In order to show an expanded menu and be able to manipulate it as a block simply enable the menu block normally from the administer blocks screen and comment out the menu from the the page.tpl.php!
Comments
Comment #1
pyotrpro commentedYour menu block (navigation) better to be Drupal friendly - i mean - it is not possible mow to move it and configure in and between blocks and it uses other classes format - not possible to use it with DHTML menu for example - it expects some classes like "menu", "leaf", "collapsed" and so on.... i think that are standarts for Drupal UI
Comment #2
alexweber commentedComment #3
alexweber commentedfixed in beta 2, please test and report back!
Comment #4
pyotrpro commentedHello
Thanx for update!
But I didn't catch what was changed really yet... it seems main-menu links still not possible to move or disable between blocks - and also your menu cannot work with levels - they don't show ( deeper than first :))
Comment #5
alexweber commentedhey, maybe they can't be moved because I put then hardcoded in the page template (like Bartik), if you want to be able to move them they should be used as blocks, maybe I'll do that instead have them as blocks in the header region as default... hang in there gonna work on this today! :)
Comment #6
pyotrpro commentedMoving by hardcoding is not big problem - about levels in menu - that have to be done for sure - sorry can't help you ...
Comment #7
alexweber commentedno problem! and just for the record, bartik does this too... (maybe its a feature?)
Comment #8
alexweber commentedComment #9
alexweber commentedHey pyotrpro, after a couple of hours of testing and hacking to try and get this to work I've come to the conclusion that it works exactly as designed.
The "problem" here is that the behaviour you expect comes from a block, whereas in page.tpl.php the menu is being shown according to Drupal Core's $main_menu variable. The same behavior occurs in Bartik and Stark.
In order to show an expanded menu and be able to manipulate it as a block simply enable the menu block normally from the administer blocks screen and comment out the menu from the the page.tpl.php!
--Alex
Comment #10
pyotrpro commentedthank you Alex!