Superfish dropdown
Permalink
Hi all,
In regards to the Superfish add-on, is it possible to get a menu item read-only ? For example, I have this hierarchy of pages:
Vendor -> XYZ -> Programming -> [Language #1, Language #2, Language #3]
The items in the [] are child-pages of the Programming page as you can see. Is it possible to make the Programming menu item read-only so that it is only a category or read-only node that you can see in the Superfish dropdown menu ?
A related question would be is there a way to also do this in autonav ?
Looking forward to any ideas, thanks.
In regards to the Superfish add-on, is it possible to get a menu item read-only ? For example, I have this hierarchy of pages:
Vendor -> XYZ -> Programming -> [Language #1, Language #2, Language #3]
The items in the [] are child-pages of the Programming page as you can see. Is it possible to make the Programming menu item read-only so that it is only a category or read-only node that you can see in the Superfish dropdown menu ?
A related question would be is there a way to also do this in autonav ?
Looking forward to any ideas, thanks.
i think he wants it to just be a menu item that doesnt link anywhere..
thats a feature we're adding to superfish right now.
thats a feature we're adding to superfish right now.
It would be a place holder that is active but doesn't go anywhere upon clicking. maybe?
Yes, the ability to have a non-linked menu item or placeholder (thanks Bryan....that's the word I was thinking of) was what I was asking about. Glad to hear that it's on the drawing board.
Thanks again everyone for their replies.
Thanks again everyone for their replies.
ive done a quick and dirty fix for this using an external link that goes to "#"
Superfish 1.1 is now released:
http://www.concrete5.org/marketplace/addons/superfish/...
if you want this option, add a checkbox/booelan page attribute with the handle dont_link to the page that shouldn't have a lind.
http://www.concrete5.org/marketplace/addons/superfish/...
if you want this option, add a checkbox/booelan page attribute with the handle dont_link to the page that shouldn't have a lind.
Just thinking...this doesn't work in the autonav, say, if you have your site map in the footer.
So its not really a page attribute, as much as a superfish attribute, even though the property is stored as a page attribute.
Semantics? Yes, and pretty important when designing complex sites.
So its not really a page attribute, as much as a superfish attribute, even though the property is stored as a page attribute.
Semantics? Yes, and pretty important when designing complex sites.
well..yes and no.
we've gotta be really careful about extending custom attributes to do more than they originally were designed for. We ended up causing all sorts of chaos when we made exclude from nav also impact page list in addition to autonav... so yeah..
generally page attributes are set at the page level, but are designed to impact ONE behavior so everyone can keep things straight.
we've gotta be really careful about extending custom attributes to do more than they originally were designed for. We ended up causing all sorts of chaos when we made exclude from nav also impact page list in addition to autonav... so yeah..
generally page attributes are set at the page level, but are designed to impact ONE behavior so everyone can keep things straight.
I see your point.
But my real problem is how to solve the discrepancy between the non-linking items in my superfish menu, and the same linking items in my footer auto-nav.
The attribute 'exclude from nav' works in superfish and the auto-nav,
but
the attribute 'dont_link' affects only superfish.
But even if the auto-nav could have non-linking items, that's not really what I want in my footer menu anyway.
The real problem arises from the fact that I have to create an empty page in order to get a menu item to function as a category for my dropdown menu.
If I could add menu items as categories, not pages, all these problems would be solved :)
So that may be the best option, rather than a cascading series of fixes that get further from the root of the problem.
Just a thought
But my real problem is how to solve the discrepancy between the non-linking items in my superfish menu, and the same linking items in my footer auto-nav.
The attribute 'exclude from nav' works in superfish and the auto-nav,
but
the attribute 'dont_link' affects only superfish.
But even if the auto-nav could have non-linking items, that's not really what I want in my footer menu anyway.
The real problem arises from the fact that I have to create an empty page in order to get a menu item to function as a category for my dropdown menu.
If I could add menu items as categories, not pages, all these problems would be solved :)
So that may be the best option, rather than a cascading series of fixes that get further from the root of the problem.
Just a thought
there is an option so that you can only see to a certain depth in the subpages i think the default is 4.