On a site I'm developing I have a main menu, and then I have a menu I made with "recommended items" that are not on the same lebvel as the main menu items.

So far so good.

When I go to edit one of the "recommended items" the "menu settings" are selected locking the node into the main menu, with as result that editing the content of the node puts the node in the main menu and removing it from the menu it was in.

This happens with book pages and self created content types, so I assume it happens regardless of content type.

This may have something to do with the reparenting menu problem, but I'm seeing this on all nodes that hang in a self created menu.

Comments

Bobby1290’s picture

Bobby1290 commented

Additional info: Closest similar bug report is from 7.0 alpha 6 #881674: Menu Menu breaks when custom menu is used

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

You need to enable that menu in the node type settings.

Bobby1290’s picture

Bobby1290 commented

Thank You.

As a comment the following;
-this does not feel "good"
Apart from making a new menu,
menus have to be connected to the content types that are going to use the menu........this is really convoluted.

Its not an "intuitive" way of placing content in a menu.

In any event, if this is a requirement for using a menu then placing content in non-available menus should fail and give a message.

I still think that if you hang something in a menu and the system accepts it, then no (unrequested) automatic process should reparent or change the menu. Sounds like an "undocumented feature" to me.
How this works out with users who aren't developers and don't have all privileges, is also a concern.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Sure, it is a bug, but I think there are already bug reports open about it. I was just pointing out a workaround :)

Bobby1290’s picture

Bobby1290 commented

Okido, and thanks again for the workaround Bendir..

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Version: 7.0 » 8.x-dev
Priority: Major » Normal
Issue tags: -menu +Needs backport to D7
WilliamB’s picture

WilliamB commented

That work around doesn't really work. i mean my article are not going to always be in the same menu item and some of those article won't even be on menu...

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update

This needs an issue summary update if it's still an issue.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

pameeela commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)
Issue tags: +Bug Smash Initiative
Related issues: +#2954418: Moving a nested menu item via the link edit form or node edit form does not update menu of the children, +#2761755: [regression] Menu links reparenting via interface could lead to unusable broken menus

Thanks Bobby1290 for creating this issue, it is one that has bitten me before too! There are already a couple of tickets with patches in progress for this issue, so I added them as related and I'm closing this as a duplicate.