This may be a dupe of http://drupal.org/node/271112, but that thread is for the 6.x version. My issue is that since upgrading to version 5.x-1.2, my top-level parent node menus are getting set to a weight of -10, and I can't change them manually. If I edit the node and change the menu weight, the weight just gets set back to -10. If I set the menu weight in Administer > Site building > Menus, the menu weight sticks but the menu gets all out of order.

If I disable the Node Hierarchy module, the issue goes away, and I can set my top-level parents to their correct menu weights.

Any ideas?

Comments

blowski’s picture

blowski commented

I constantly suffer the same problem. The site outline page behaves in mysterious ways.

I've found that doing a few at a time, and pressing refresh to see if it's actually remembered it eventually works, but it doesn't scale. The site outline functionality should either behave like the Drupal Menu and Taxonomy blocks, or be pure HTML.

broeker’s picture

broeker commented

I've been poking through the queue for versions 5.x and 6.x and it appears there are several variations of this problem. Here is ours for version 5.x and our subsequent fix:

PROBLEM:

After editing or saving a node, all of the top-level menu items are re-ordered in a highly annoying fashion. If you reset, they are blasted again whenever a new node is added to the site. We have tracked our particular problem down to this line:

nodehierarchy.module Line 400:

 _nodehierarchy_normalize_child_order($node->parent);

What is happening here is that inserting ANY node without setting an explicit parent (regardless of whether that content type is eligible as part of a hierarchy) ends up re-ordering all of the site's top-level menu items based on the order they were originally inserted into the Drupal menu table.

SOLUTION:

According to our initial tests it appears a very simple fix is to add a quick check for the existence of a parent:

if ($node->parent) {
    _nodehierarchy_normalize_child_order($node->parent);
}

CAVEAT:

I haven't had time to explore other possible implications of this fix, and it appears our symptoms are at least slightly different than some of the other related posts in the queue so your mileage may vary. Not sure if such a small change warrants a patch but will create one if desired . . .

ronan’s picture

ronan commented
Status: Active » Fixed

I have committed a variation on this update to the latest 5.x-1.x-dev. This should hopefully fix this issue. Let me know if it persists.

Thanks

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.