Closed (fixed)
Project:
Megamenu
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2010 at 17:08 UTC
Updated:
25 Feb 2012 at 15:37 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedAcquia Prosper is probably loading the primary menu in the page template. You could replace the call to primary links to theme the megamenu block. That would place the themed megamenu output in the same place you are currently displaying the primary menu.
Comment #2
Anonymous (not verified) commentedIn Acquia Prosper lines 74 - 81:
You'll need to replace
<?php print theme('grid_block', $primary_links_tree, 'primary-menu'); ?>with a call to theme the megamenu block. If you are calling the megamenu block for primary links then the code becomes:Comment #3
Anonymous (not verified) commentedThat code goes in the page.tpl.php of the Acquia Prosper theme.
Comment #4
xl_cheese commentedThanks for the replies! I may experiment with this, but being I'm about to put my site into production I may hold off on this menu until it's more stable. I'm looking forward to it's development! I sort of got the nice menu module to do a multi column menu, but it was a little hokey getting it there.
Comment #5
xl_cheese commentedI finally got around to trying this out. Unfortunately, I could not make it work. My primary links would not appear with this code change. Thanks for the help.
Comment #6
Anonymous (not verified) commentedOk, I downloaded Acquia Prosper to try it out myself. And you are right, I made a mistake (shows me to write code blind) :-)
The correct call is:
The zero in the module_invoke() call, happens to be the block # for primary links (for me, it might be different for you).
That worked for me, it spit out the megamenu in the primary-menu area. Alternatively, you could add a region and then just place the megamenu block in it.
Comment #7
xl_cheese commentedThanks again. My primary links Block # doesn't seem to be 0. How do you find that number?
Comment #8
Anonymous (not verified) commentedDo you have other megamenu blocks enabled?
Comment #9
xl_cheese commentedNope.
Maybe I'll try a local install to see if it works there.
Comment #10
Anonymous (not verified) commentedGo to block administration (admin->build->block) then click on configure next to the primary-links megamenu block (or whatever block you are interested in). Notice that the url reads www.example.com/admin/build/block/configure/megamenu/#
That last number is what you want.
Comment #11
Anonymous (not verified) commentedComment #12
priyanka.salunke commentedi also wnt to replace my primary links wth superfish menu plz help me out.......
Comment #13
grimfandango commentedThere are two menu modules that I know of that support Superfish menus.
http://drupal.org/project/superfish
http://drupal.org/project/nice_menus
These projects are unrelated to the Megamenu module.
GrimF
Comment #15
rickyrocks commentedthanks a lot for helping with code. does same code work on acquia marina theme ?
Regards
Comment #16
rickyrocks commentedthanks a lot . this code works perfectly fine.
Regards
Comment #17
brianbrarian commentedThanks ... just what I needed. The code from #6 works great in the Simpler theme.
Comment #18
jantoine commentedMight be an easier solution, but I used
Cheers,
Antoine
Comment #19
Anonymous (not verified) commentedWon't this be overwritten on update? Silly question? Maybe. :) But I was wondering if you add or change page.tpl.php, won't that be overwritten when your theme needs a security update? I'm using this to replace the primary links menu with one using the Megamenus module, but want to make sure I do this properly so I won't have to fix it every single time we update our theme. Thanks!
Comment #20
jantoine commentedHi abuchold,
This is a separate general theming question. Please see http://drupal.org/community for community support and http://drupal.org/documentation/theme for theming documentation.
To briefly answer your question, many drupalistas use a "base" contributed theme and create their own custom sub-theme based on the chosen base theme. If the base theme has a new release, a simple diff can be used to detect if any customized files used in the sub-theme need updating.
Comment #21
kirtimansharma commentedThe code in #6 works just. Are there any tutorials for making custom skins for mega menu too?