Closed (works as designed)
Project:
Superfish Dropdown Menu
Version:
7.x-1.8
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Dec 2011 at 12:23 UTC
Updated:
9 Dec 2012 at 16:40 UTC
When you configure a menu action trying to control menu active class (for any condition), the superfish item link isn't affected.
The original core menu work as expected, triggering the active class.
Comments
Comment #1
mehrpadin commentedHey Jannise,
Can you try the v1.9-beta4 please?
Comment #2
masterperoo commentedSame thing.
v1.9-beta4 makes no difference.
Context still wouldn't set the item active.
Comment #3
ardas commentedYes this is a known problem in Superfish. I think it happens because Superfish builds menu using its own function instead of use Menu API functions like Menu or Block Menu modules do.
Is there a way you can use menu api to build superfish menu tree?
I am pretty sure that thismay also solve a problem with contextual links which are not visible on superfish block.
And this also will solve problem with NO LINK module integration - superfish doesn't understand no link token.
Thanks.
Comment #4
mehrpadin commentedTo Jannise & Mark: I'll reproduce this asap.
To Dmitry: Privet! Contextual links is working since v1.9-beta3; We can't use the API the way Menu Block did because we need a lot of customisations and so on.
Comment #5
mehrpadin commentedJust to make sure, are you all using Context 7.x-3.0-beta2 ?
Comment #6
ardas commentedWe are not using Context at all but we use Menu Block and other modules that hook into menu structures... all of them can't work with Superfish, since it builds menu with its own theme function instead of use Drupal Menu API. I think this is a problem.
Comment #7
sassafrass commentedUsing Context 7.x-3.0-beta2 and having same Superfish/Context/Active menu trail problem
Comment #8
ardas commented>> To Dmitry: Privet! Contextual links is working since v1.9-beta3; We can't use the API the way Menu Block did because we need a lot of customisations and so on.
Yes, we understand this. But may be some partial integration with Menu API so that all customization done for menu is reflected in Superfish? Otherwise, Superfish doesn't work with a few key menu functionality.
Comment #9
mehrpadin commentedDmitry,
In many cases Superfish is not the problem, some modules are just not done right hence not compatible with other modules - Special Menu Items, for example - let me know which modules are not compatible and I'll review them as soon as possible. As for the Menu Block, I don't understand how they can be used together? because to me Superfish and Menu Block have nothing to do with each other! both create menu blocks, one simple menus, the other one dropdowns! of course, Menu Block has some features Superfish does not have - it will with v2.0 hopefully - but Menu Block does not do anything to menus but to blocks as far as I know, so I don't expect Superfish to reflect anything, and so on, or perhaps I'm missing something?
Comment #10
mehrpadin commentedAlso, can anybody try the new version? http://ftp.drupal.org/files/projects/context-7.x-3.0-beta3.tar.gz I'm trying to save as much time as possible, thanks!
Comment #11
ccweaver39 commentedHi,
I was experiencing the same problem (superfish menu doesn't show active-trail despite setting it to do so with Context).
I just updated to the latest Context Beta (v7.x-3.0-beta3) and, unfortunately, the problem still happens.
Comment #12
osopolarAs mentioned in #9 this is not a superfish issue. This should and hopefully will be solved in the context module itself. Please review the patch (#72) in this issue: #835090: Context Reaction: Set menu trail, for me it's working well.
Comment #13
balumba commentedMy workaround for now is:
1. Add the desired parent menu item as a breadcrumb.
2. Set the parent menu items active with jQuery based on the second last breadcrumb item:
Comment #14
mehrpadin commentedPhew! buddies, got some time, tried the module, just like Special Menu Items, it's a
theme_menu_linkbeing overridden and so on; follow this: http://drupal.org/node/1862342 :)