This is a little hard to describe, since the behavior is so odd and unpredictable.

I'm learning Drupal and converting a site that will start with about 200 static pages. Dynamic content will follow. Thus the menu system must be well designed. It consists of a Superfish tab bar with 6 items. Each has only level 2 dropdown items. When an item is selected the node's page is displayed.

On the right of each page is the menu column. Using Menu Block and Taxonomy, this appears automatically for each page. All each node must specify is "Provide a menu link" is checked and a "Parent Item" is selected. In this manner a hierarchial tree for all nodes can be contructed. Until the D7 betas come, I've only got 16 test nodes entered.

All was going fine, no problems at all, until I realized the glossary needed to be handled differently. It has 56 terms. It can't be part of the Main Menu tree. So I created a Glossary menu and then added 3 existing nodes. Then I added that block to the right region for only the 3 nodes listed.

Finally, to have the 3 glossary terms not show up in the Main Menu, I edited those nodes and unchecked "Provide a menu link."

To my surprise, after a save, when I edit again nothing has changed! Worse yet, after a save, the node is removed from the Glossary menu! Even worse, when this is done, sometimes the node is MOVED in the Main Menu arrangement to be on the first level! This causes it to show up in the tab bar. It actually shouldn't be in the Main Menu at all.

Drupal 7 is outstanding, but there are a few pesky bugs left. I really don't know if this problem is in the added modules or core. But I thought I'd report it right away. I'd be glad to run any suggested tests.

Comments

aspilicious’s picture

Version: 7.0-alpha6 » 8.x-dev

I'm not sure I understand this all. Is it still broken?

larowlan’s picture

Do you have your glossary menu selected as an allowed menu for the glossary node type?
Edit your content type and choose the menu links tab to see if it's switched on.

Jody Lynn’s picture

Status: Active » Postponed (maintainer needs more info)

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

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
Issue tags: +Bug Smash Initiative

As part of the Bug smash initiative, we are triaging issues that are marked 'Postponed (maintainer needs more info)'. This issue is more than 12 months old and no additional information has been provided to reproduce it. As such I am marking it 'Closed (cannot reproduce)'.

If anyone believes this issue should not be closed, please provide specific steps to reproduce when reopening it.