"Navigation" appears as the top item in the DHTML navigation menu. It links to the home page. Yet this item does not appear within the normal menu structure for the Navigation menu. Is there a way to remove it? Or is this a bug?
I can't see any reason from the module code why it should be there. "Navigation" is the default term for the block header, but should not appear in the block menu itself.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | dhtml_menu-duplicate-trim-235774-8.patch | 833 bytes | cburschka |
Comments
Comment #1
alpinejag commentedThis is happening to me too.
Comment #2
farf commentedMe too....
Comment #3
alpinejag commentedAnyone figure out why yet?
Comment #4
brmassa commentedGuys,
i dont know about Arancaytar (the module maintainer), but i will not maintain the D5 code anymore.
Im sorry, but i dont have any D5 testing site to work on. Also, the module now uses some features only available for D6, like hook_preprocess.
again, sorry,
massa
Im marking it as Fixed, but anyone can and should reopen it if wanted.
Comment #5
ertomueller commentedsame thing happening to me. interesting is that it didn't happen for almost 2 months. then all of a sudden it started happening about 2 days ago. using drupal 5. does anybody got the issue resolved?
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
fukamit commentedI also encountered the problem.
It occurs when the 'Duplicated menu items:' field contains a blank line.
A patch below worked for me.
The patch won't work if you remove all lines in the field.
In the case, you can suppress the unwanted item by entering something
that already exists in the menu, such as logout.
Comment #8
cburschkaOuch. You can't split a string and then check if the array is empty - the array will always have at least one element even for empty strings. An array with a single empty string element evaluates to true. So the whole
if ($text)never quite worked. I've fixed it by moving the string splitting inside the block, so it checks for empty strings first.I'll check the 6.x branch to see if there is any similar problem - after all, the default value for that field isn't empty, so an empty string is a special case.
Comment #9
cburschkaWhat's happening? I'm sure I uploaded a file. Here we go again.
Comment #10
cburschkaWhatever.
Comment #11
cburschkaOuch. The whole thing was fixed in the development branch the whole time. And so where numerous other fixes that have been done four months ago - 5.x-1.2 is half a year old. I'll freeze that into a final D5 version and off we go.
Comment #12
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.