First, thanks for developing this module. It's a sort of a "duh" feature that probably should've been in 6. But hey, they made a lot of improvements from 5...so I'll stop complaining. I'm glad someone put in the effort.

Setup:

I added the special_menu_items module as a way to create unlinked parent items in a menu. I altered one of those parent items' urls to "nolink" (without the quotes, of course).

Result:

The parent item still shows as a link; but now (as you might expect) it takes me to the "nolink" page with the little blurb about how I shouldn't be able to see that page.

Possible collision:

I've been running the jquerymenu 6.x-2.3 (http://drupal.org/project/jquerymenu) with success. After I added this module, the jquerymenu still operates normally. However, I'm wondering if there's a conflict in the way the jquerymeny builds it's version of the menu and the way that this module alters the default menu behavior.

Code:

Here's the code for the link via firebug:
<a title="Administrative Team" href="/nolink">Administrative Team</a>

Thanks

Comments

Korinvall’s picture

Component: Miscellaneous » Code
Korinvall’s picture

I checked out the possibility of overlapping style names, but I can't seem to find anything along that path either.

Korinvall’s picture

I'm pretty convinced this module is hitting a wall when it interacts with Jquerymenu. I attempted to use it on a menu that isn't applying the jquerymenu and it worked fine - both the "nolink" and the "separator."

I hope the collision can get figured out (I'll do what I can)....because the jquery modules coming out (like advanced_book_blocks and the jquerymeny) are nice features that work off of Drupal 6's integration of that Javascript library.

Fingers crossed.

Korinvall’s picture

Just and update: I still cannot determine what's causing the conflict between Jquerymenus and this module.

martin naughton’s picture

Version: 6.x-1.2 » 6.x-1.3

i have turned off jquery on my webiste: www.martinnaughton.com and still i can not get the link to become a dummy link.

i entered in nolink in the path for the menu option fake link. it is still a link and goes to a new page called www.martinnaughton.com/nolink

i do not think it is jquery problem for me. is there anything else that is missing in the installation notes or setup.

this is the code for me in firebug:

<div class="navlinks">
<ul id="navlist" class="links">
<li class="menu-182 active-trail first last active">
<a class="active" title="" href="/nolink">fake link</a></li>
</ul> 
</div>

thi is a great module caused it is asked for alot. It is part of cmsmadesimple core and is only a tick box if you want to make the menu item a dummy link.

thanks a million for this module. spent a whole weekend trying to copy code that would do it.

tamerzg’s picture

Assigned: Unassigned » tamerzg

Hi Cacody,

it seems there is a conflict with Jquery menu. I will take a look and will issue fix as soon as possible. Any help would be appreciated.

Martin: Can you try disabling and enabling module again? Do you see "...enter "nolink" to generate non-linkable item, enter "separator" to generate separator item." in Path helptext when adding new menu item?

Korinvall’s picture

@tamerzg

Many thanks. I'm going through the code right now. I only have about 2 hours or so a week I can devote. But I hope to hit something.

cacody (Corin)

afterdark’s picture

Dude, it seems the problem isn't with the jquerymenu...
I tried to put a nolink item in the navigation menu (wich hasn't jquerymenu enabled). It didn't work too.

I wonder if isn't some conflict with another module, like pathauto or globalredirect, although i could't find any relationships betweeen that modules and special_menu_items.
I HOPE the problem isn't jquerymenu, the only reason i want special_menu_items to work is that i want the root item (in a taxonomy menu) to just collapse/expand the list when clicked.

In the matter of facts i think it's a core issue - why can't we simply put a # in the menu link? I hope someone will take care of that in the next release.

In the other hand, why jquerymenu hasn't the option to make the parent item of a collapsible list to just collapse/expand that list?

Ok, wrong thread. Just thinking...

Thx everybody for the efforts.

afterdark’s picture

Title: jquerymenu conflict? » Quick and dirty solution. But it works.

Wellll...

I have finally figured out a solution that every good programmer would hate. But i'm not a programmer, and i've been struggling with the issue all day long.
It's a dirty and quick solution! And it works only for the issue i mentioned before, i.e. parent item in jquerymenu without links and collapsing/expanding the list.
Here it goes:

open the jquerymenu.css and edit the "width" line:

ul.jquerymenu li span.parent {
  position: absolute;
  margin-left: -15px;
  margin-top: 6px;
  width:9px; -----------> change this to whatever you want. It must be long enough to override the item in the menu. I used 120px to overrride "Categorias"
  height:9px;
  display:block;
}

That's it. You'll have an item that, when clicked, will open/close the nested list. I warned it was quick and dirty.

not_Dries_Buytaert’s picture

Just confirming that the 'nolink' and 'separator' do not work with jquery_update 6.x-1.1 and jquerymenu 6.x-2.3.

not_Dries_Buytaert’s picture

Title: Quick and dirty solution. But it works. » Incompatible with jquerymenu

In accordance with previous post, now the title of this issue is explicitly referring to JQuery menu (http://drupal.org/project/jquerymenu).

adam_b’s picture

Version: 6.x-1.3 » 6.x-1.5

Bump... I'm unable to use v6.x-1.5 with jquerymenu v6.x-3.3.

I enter "nolink" or "separator" and save the menu form - it looks fine.
But if I open the form again, it's added a node ID onto the end - eg "nolink/195302" or "separator/195302"

And the menu item is displayed as a link which "takes me to the "nolink" page with the little blurb about how I shouldn't be able to see that page".

benny2012’s picture

Subscribe

gagarine’s picture

Status: Active » Closed (duplicate)

Close as a duplicate.
We should solve #1221294: option to use <a href="#"> for "nolink" items to not break other modules and it will certainly works.