Hello,

When we edit a basic page (which is Linked to a menu link of Secondary menu), it moves itself to primary menu after the edited page is saved.

All modules on my site are upto date.

Thanks

Rugman

CommentFileSizeAuthor
#2 dummy | drupal7head.local_.jpg166.34 KBlyricnz
#2 Edit dummy Uxor Virtus | drupal7head.local_.jpg70.77 KBlyricnz

Comments

sarjeet.singh’s picture

sarjeet.singh commented
Status: Closed (duplicate) » Active

Rugman..

please check content type "menu settings". and make sure "Available menus" set as "Secondary menu". "Default parent item" also set as "Secondary menu".

If you already done above settings. please provide me list of all modules(core and contributed) which you used.

thanks

lyricnz’s picture

lyricnz commented
StatusFileSize
new Edit dummy Uxor Virtus | drupal7head.local_.jpg70.77 KB
new dummy | drupal7head.local_.jpg166.34 KB

I was able to reproduce submitters issue. The problem is exactly as described by reply #1. I'll explain

@Rugman: I assume that you manually added the link to the node from the menu-editor? The problem is that your *content type* is not configured to show the secondary menu as one of the options. This means that when you edit the node, the Secondary menu is not shown, so it defaults back to the Main Menu. See first screenshot. If you enable the correct menu (User Menu for me), then go back end edit the node, you'll see both Main Menu and User Menu as being available, and your pre-created menu entry selected by default (see second screen shot).

lyricnz’s picture

lyricnz commented
Status: Active » Closed (duplicate)

However the UI definitely helps create this confusion. It has been discussed for about a year at #761648: Menu D6->D7 upgrade doesn't maintain node-menu configuration (f.k.a.: Menu items disappear after upgrade or manual menu entry). Closing this one as duplicate.

Rugman’s picture

Rugman commented

Dear Lyricnz,

Many Thanks for detailed update.

Ideally one may/may not update content type after creating/updating content type. In normal flow, content types are created first and then added into menu(s). But I beleive people behind drupal are far more better than me so not arguing about this.

Please refer your first screenshot, its shows default parent item, isn't it possible to make default menu item - source menu before editing, kindly give it a thought.

Regards,

Rugman

lyricnz’s picture

lyricnz commented

Scenario: Consider two menus (A+B), and content type "page". The content type "page" has only menu A enabled, and not B. If you were creating a "page" from scratch, and checked the "add item to menu" checkbox, you would only have Menu A available to select from. However an administrator has added a link to a particular page "welcome" from menu B (using the menu editor).

In the current Drupal 7 situation, if a normal user *edits* the page "welcome", the menu selection will be limited to only those menus that are permitted (i.e. Menu A). So the drop-down in the parent-menu selection *changes* to just Menu A. If you save the node, you will *remove* the link from menu B, and add one to menu A. This is the unexpected behaviour described in this issue.

Now (in the next version of Drupal 7, since the patch in the issue has been applied), when you edit the "welcome" page, the menu entry will *not* show up, and "add item to menu" will be unchecked. If you check that, the "parent" dropdown shows up, and you can select only the Menu A. The existing link from Menu B will be unaffected (since the current user isn't allowed to add a link to that menu, they shouldn't be able to delete from it either). We cannot just show the link from Menu B, because the user is not allowed to select that menu.

Status: Active » Closed (duplicate)

Correcting issue status, see #2125263: Issue status not taken from last comment during D7 migration.