Hello,

thanks for creating the Node Hierarchy module, it works very well, have a logical UI and works exactly as one would expect it to. The Views integration is sweet.

However, I must be doing something wrong, because every time I edit a child node, the order of the menu is reset.

Also, if I want to create an top level node with a specific menu item, I can't. The menu option will instead be placed in the default content menu.

Any advice would be appreciated.

Thanks.

Comments

joshmiller’s picture

joshmiller
he/him
Primary language English
Location Indianapolis, Indiana, USA
commented
Priority: Normal » Critical

Gabriel, I am having the same issues with the menu being reset. This is a big deal, as I'm developing a large site and EVERY TIME I save a node, my menus change. I'm fearful of that client phone call a year from now, "so I edited so and so page and the whole menu has changed! help!"

Josh

cdmarine’s picture

cdmarine commented

I'm seeing the same thing. Every time I set a parent or child node, my primary nav menu jumps around.

Not sure why that's happening, as the nodes I'm editing don't have any relationship (yet) with that menu.

joshmiller’s picture

joshmiller
he/him
Primary language English
Location Indianapolis, Indiana, USA
commented

Temporary work-around:

I've found that my nodes that are being handled by node hierarchy behave in the menu if I click on the parent, then the "children" tab and manually set *every* node (sometimes this requires just cycling through each of them. Once you have made node hierarchy touch each node and their "position" this seems to enforce node hierarchy's "custom weight"

This really should be addressed by the node author as I have tried to figure out what it is trying to do in the code and don't get it.

Personally, I'd like node_hierarchy to just set hierarchy and let the menu system deal with the ordering.

Josh

FreddieK’s picture

FreddieK commented

Have this problem too, if I can't find a solution that'll be enough to make me drop this otherwise awesome module.

DeFi’s picture

DeFi commented

Same Problem here. I fixed it by disabling the automatic menu reordering in the nodehierarchy module completely.

One can do this by letting adding a "return FALSE;" as the first line of the function "_nodehierarchy_set_menu_order".

As I don't create menu entrys for my child nodes this has worked for me so far.

freddyseubert’s picture

freddyseubert commented

Subscribing.

I wonder if this issue is fixed by design in 2.x branch?

mraichelson’s picture

mraichelson commented

subscribe