Drupal Association members fund grants that make connections all over the world.
First of all, let me tell you that I deeply love this module!
Well written and so easy to use: great job!
I am experiencing what I think is a bug:
Menu Block seems to ignore active trail when "the menu selected by the page" is used, that is, it seems to only care about whether current menu item is in a menu to display a block, ignoring its ancestors in the active trail.
As a result, a "Current menu" block may completely disappear because current menu item is not inside it, even if its ancestors in the active trail are.
Here is a simple concrete example:
- create a simple hierarchy of menu links in Main menu, leaf being a link to a node.
- create 2 menu blocks: Main menu (level 1) and Current menu (expanded levels 2+)
- navigate to the leaf node: Current menu (expanded levels 2+) shows up as expected
- edit the leaf node: Current menu (expanded levels 2+) disappears :-(
This works as expected when "the menu selected by the page" is not used.
IMO, in such a case, Menu Block should rely on active trail to process a "Current menu".
This way, Menu Block would also support any special active trail customizations made by site developer.
I will try to work on a patch for this.