Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I have footermap set to display only my Primary Links, which are organized something like this:
- Home
- About
- Stuff
- Stuff1
- Stuff2
- Stuff3
- Pear
- Apple
- Orange
However, footermap displays it like this:
- Home
- About
- About
- Stuff
- Stuff1
- Stuff2
- Stuff3
- Stuff1
- Stuff2
- Stuff3
- Apple
- Orange
The bolded items are duplicates, and the example item Pear does not show up at all in the footermap.
I've tried with stable and the most recent dev 6.x-1.x-dev 2009-Oct-16 (with and without legacy mode).
I don't know if there's something wrong with my menu system (it's just the standard Drupal 6 Primary Menu), or if it's something with footermap.
My admin/build/menu/settings are like this:
Default menu for content:
Primary LinksSource for the primary links:
Primary LinksSource for the secondary links:
Secondary Links
Let me know if any more information is needed.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | db.PNG | 4.21 KB | jackread |
| #1 | Picture 1.png | 11.37 KB | mradcliffe |
| #1 | Picture 2.png | 13.95 KB | mradcliffe |
Comments
Comment #1
mradcliffeI added everything as normal menu items, and they seem to appear for me.
This is what I did real quick:
Is the Pear menu option a views-generated menu? If so, then you'll have to, unfortunately, enable the system-menus option.
Comment #2
jackread CreditAttribution: jackread commentedI'm getting the same issue using the latest dev version of the code.
I did originally have views creating the menu items... but then I created them manually... but still no luck.
Comment #3
mradcliffeCan you look a the HTML source that's generated on the page?
In the footermap div each footermap item will have a class based on the menu link id.
It should look like this
class="menu-#". Are there any items there where the number is the same? That would mean the module IS getting a duplicate from its queries.Comment #4
jackread CreditAttribution: jackread commentedthe id's are all different... maybe its bringing de-activated menu items as well?
Comment #5
mradcliffeOkay, those are all unique menu items that were created or you created on your site. The module doesn't query for hidden or deactivated menu items so all of those must be enabled menu items.
Comment #6
jackread CreditAttribution: jackread commentedthey don't show up on admin>build>menus.... so they aren't active
Comment #7
jackread CreditAttribution: jackread commentedAny ideas why it would be doing this?
Comment #8
mradcliffeI need to see the database records for these menu items. They are definitely not set to hidden in the database. If you don't have an easy way to do this you can install the Table Wizard module (depends on schema) to see tables in views.
Comment #9
jackread CreditAttribution: jackread commentedhere's a screen shot of one of the items... it looks legit to me.
Comment #10
mradcliffeThat menu item is enabled since the hidden column is set to 0. When you uncheck the enabled checkbox it should set that value to 1.
Comment #11
jackread CreditAttribution: jackread commentedi think you miss the point...
that menu item doesn't show up in admin > build > menus
UPDATE: It doesn't have a corresponding reference in {menu_router}... could this be why it doesn't show up in admin > build> menus ?
maybe you should adjust the db_query that looks up menu items to mirror how the core menu module does it?