Child menu items created when editing node

Did you come to the edit page through a link from the user 'Sections' page or from normal node editing?

Is 'top' in this case the Menu top level or a node or menu item?

Disregard the above comments. Bug confirmed.

The isseue, actually, seems to be that we are not verifying that a unique menu id is being passed before creating the menu item.

Here is a partial patch that prevents this problem.

The issue that remains is that a node can be assigned to more than one menu and can actually have multiple menu items. This feature currently has trouble with that.

The attached patch stops the creation of a new menu item if one already exists, but this is only a partial fix, because it will not allow these editors with limited permissions to move a node from one section to another.

Title change, since the problem is not the _location_ of the menu items, but the fact that we are creating duplicate items when using this form element.

What do you mean by parent level?

The parent level bit is unchanged, but the UI is a little tricky. I have cleaned that up some -- notably by collapsing the fieldset and changing the help text if a menu item has already been assigned to a node.

By design, when you first create a node, you must choose its 'parent' section. This then becomes visible in the form during later edits.

When a user with the 'publish to my sections' permission first creates a node, she has the option of _not_ assigning it to a menu section. However, once that item is assigned to a section, only a user who may 'administer menu' may remove it.

There is actually a bug in Menu Node API as well.

Both patches are required.

Well, I have the prototype of this in production use, so I need to squash these ASAP, but (obviously) need confirmation.

Yay!

I am going to commit and roll a 6.x.1.1 of both modules.

Thanks!