Removing suckerfish?

Good timing... a theme setting to disable the dropdown is already implemented and will be in the next release coming asap

This is now a theme setting (under the Navigation fieldset) in the latest beta 4 release.

I'm not sure I understand the question. If they're not in the dropdown, where would they be rendered? :)

But yes, if you want to do your own dropdown structure, you'll need to re-add them on your own. I'm curious why you're doing this? There are ways to use the other Superfish menu styles in your subtheme, or completely differently theme the look of it so we'd be happy to point you at that if that's the issue, or if you have any suggestions to make it better suit your needs.

Shouldn't it be rendered as a normal drupal menu, as if it was a block put into a region? No. Primary and secondary links in Drupal are special and don't have the same output as blocks regardless. But we're doing even more with theming of the output in order to do the dropdowns. There's not really a way to make them "there" yet not mess up the display. If you need the sub-items output for styling, you can just use the primary links block in a region, or I would give the menu block module a try to just put the sub-items elsewhere: http://drupal.org/project/menu_block

Again I'd love to know what you're doing with it so we can better understand what isn't possible with the current output.

Thanks!

ManyNancy,

We don't currently have the Skinr functionality (page level settings) that would allow us to disable the Superfish js.

In the meantime, if you really want to remove the js (and css) you can comment out the following declarations in the fusion_core.info file in your fusion_core directory:

stylesheets[all][] = css/superfish.css
stylesheets[all][] = css/superfish-navbar.css
stylesheets[all][] = css/superfish-vertical.css

scripts[] = js/jquery.bgiframe.min.js
scripts[] = js/hoverIntent.js
scripts[] = js/supposition.js
scripts[] = js/supersubs.js
scripts[] = js/superfish.js

I am having a similar issue. I want use use the superfish module, for its added functionality. With some css changes, i've got it working, but the superfish js filesnloaded by fusion are getting in the way of the other superfish js files used by the module.

Is there any reason for the theme to load the superfish js files if dropdown menus arent enabled? It would be nice not to have to change the info file.

My solution: this patch only loads the following javascript files if Superfish has been enabled, saving 12KB: hoverIntent.js, superfish.js, supersubs.js, and supposition.js.

I'm not sure why the test failed - I used the commands from the module's Version Control page to get 6.x-1.x. Was also able to re-download and apply the patch on my system (Windows). I've uploaded patches before but this is the first time Drupal.org decided to test one!

Update to patch: check if $.superfish() exists in script.js

Closing as won't fix since the D6 version is not getting any new development.