I am running Drupal 7 with Superfish 1.9 with dropdowns.
If I go to Content --> and update an article --> click save. The parent item li class gets changed from
<li id="menu-344-2" class="sf-depth-1 menuparent">
to
<li id="menu-344-2" class="sf-depth-1 no-children">
This makes my dropdown for that parent disappear. I can fix it by going into Structure --> Menus --> Disable a child in the affected parent --> Click save --> Then re-enable it and the dropdown shows back up again and the no-children class is removed.
What is causing the no-children class to be added after updating my content?
Comments
Comment #0.0
jdardis07 commentedAdded
tags to display description.Comment #1
chris.jichen commentedI have experienced the same problem. But as soon as i disable a children menu item. the dropdown comes back ("no-children" class name is gone.).
Comment #2
mehrpadin commentedHey everybody,
Can you please try the development release? (with the master branch of the library)
Comment #3
jlongbottom commentedThis was happening with me. Disabling and re-enabling a child menu item did not help.
There appears to be some conflict between superfish and Menu_Block because when I removed the menu block from all the regions on the page, SuperFish started working properly again.
Not sure how to fix this since I need menu block to show the current page's children in the sidebar because my site uses both a drop-down menu and a sidebar menu.
Comment #4
mehrpadin commentedHey again,
I need to see these, please put them online and email me the URLs, thanks.
Comment #5
roflcopterDorrie commentedI believe this could be related to https://www.drupal.org/node/955378.
Some of my menu items have has_children set incorrectly and it is causing superfish to not render those menu levels (and adding the sf-no-children class).
Here is a patch for 7.x-1.9-rc1. It simply removes the test for has_children and relies on below to test if there are children.
Comment #6
roflcopterDorrie commentedComment #8
mehrpadin commentedHey there,
Thanks, patch applied.