Hello
I recently updated my Drupal website from 7.7 to 7.9. Since this update, I noticed there is something wrong with the "available menu" filtering.
Steps to reproduce:
- Create a content-type with for example "available menus" filtering set to "Main Menu"
- Create a node for this type (notice that the "parent item"-list in the menu settings tab is filled correctly)
- Attach your node to "main menu"
- Save the node
- Edit this node again
- Notice that the "parent item" list in the menu settings tab is filled with all menus, not filtered by the "available menu" filtering.
If you save the node without attaching it to the menu, there is no problem.
I retested this in a clean Drupal 7.9 installation with no contrib modules...
Ozmodiar
Comment | File | Size | Author |
---|---|---|---|
#3 | available_menu_list-1334394-3.patch | 753 bytes | dooug |
#2 | available_menu_list-1334394-2.patch | 729 bytes | dooug |
Comments
Comment #1
jvandooren CreditAttribution: jvandooren commentedIf I make the following change (menu.module line 617)...
My testcase does work... Maybe this helps.
Edit: changed node.module to menu.module offcourse, tnx Dooug
Comment #2
dooug CreditAttribution: dooug commentedI experienced the same issue. I noticed the bug was not in
node.module
butmenu.module
. It appeared to me that $type should be passed in as the third argument (as in the patch mentioned above). I posted a patch. This worked for me.Comment #3
dooug CreditAttribution: dooug commentedNew patch, it seems the
menu_parent_options
function expects$item
to be the menu item id or$type
. Although, this patch might be overkill, the first one should work.Apparently the
menu_parent_options
function is known to be goofy:http://api.drupal.org/api/drupal/modules--menu--menu.module/function/men...
Comment #4
figureone CreditAttribution: figureone commentedChanging the status so this patch gets tested. I applied it on my own system and it worked correctly. Thanks!