Closed (fixed)
Project:
Menu Attach Block
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Sep 2013 at 05:27 UTC
Updated:
4 Jan 2014 at 03:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
cameron tod commentedThanks for the patch! I will let the testbot run and then review it later today.
Comment #2
cameron tod commentedJust a quick review while I have 5 minutes...
We don't want to remove this entirely. We just need an option to disable it.
Not sure why the punctuation was lost here :)
OK, I see you adding the JS back in here. It's probably better to add it on a per page basis anyway, although I might move it to #attached.
I assume this is meant to be removed?
Comment #3
fearlsgroove commentedSorry .. terrible patch. Here's another try against -dev, which includes the ajax stuff. This does a couple things:
Note that I couldn't get the ajax feature to work with or without this patch applied. Not sure what's going on there -- the attach function never seems to fire, even though the javascript is included?
Comment #4
designguru commentedHi all,
This seems like an essential feature of this module - I'd love for users to simply click on the menu item title to open up the attached block, rather than the little carrot icon - can someone please write a patch which works for this?
I just tried the patch above and didn't see this functionality working - Ideally instead of writing a 'More' link which gets hidden with included css, the actual menu item name should be printed in the drop link (without printing the original title not linked to anything.)
q./
Comment #5
fearlsgroove commentedThis patch is about removing the requirement that the built-in drop link be included. So if I'm handling dropdown menus myself already via css, superfish, nice menus, whatever, I don't want the cruft included at all. I want to be able to support providing a submenu attached directly to a top level menu without including an extra child menu item, but I still want to show the actual menu link associated with that item. I do NOT want the block to serve as the menu item itself -- that's already supported by using as the path for the menu item link. Nor do I want the drop link to be rendered as the block link -- the idea here is we're using our own css and javascript to handle that.
So if I create a top level menu item with a normal path as the link, attach a block and choose "No drop link", the outputted markup would look more or less like
UL.menu
--LI
----A <-- menu link
----div <-- block contents
Comment #6
cameron tod commentedCommitted with attribution. Thanks!
Regarding the Javascript issue, I'm not having any issues here. Can you test again and post a new issue if you're still having trouble?