Hi Steve,

Yup, if your theme doesn’t meet the WP3 Nav Menu integration requirements (see How can I tell if my theme is compatible with WordPress 3 Menus?), then you have 2 options.

1. You may be able to get UberMenu to automatically apply to your nav menu by turning off Strict Mode under Appearance > UberMenu > Theme Integration > Strict Mode

2. If that doesn’t work, you can follow the instructions for How to Use UberMenu with Themes that do not support WordPress 3 Custom Menus (it’s pretty simple).

Hope that helps!

Chris

Hi jtpik,

The code that is causing the issues is javascript, not PHP . You’d need to remove the following javascript call:

jQuery("ul.sf-menu").superfish

on line 7 of plugins/multi-level-navigation-plugin/scripts/superfish_settings.js.php, or else remove the PHP that loads that script in the first place. Still, it doesn’t seem like this script should be included at all if the plugin is deactivated, unless the theme is requiring it and importing it directly (that would be very strange).

It does seem like the second error with the ddsmoothmenu has been resolved.

Best,

Chris

Thanks for the assistance Chris, I do appreciate it. :/ I went ahead and just deleted that plugin. Now the megamenu doesn’t drop down.

Deleting the plugin has actually improved things (that error you had before is gone) – but now it has exposed additional javascript errors.

It looks like your theme is including an older version of jQuery, 1.3.2, while WordPress 3.1 includes jQuery 1.4.4. You can try switching UberMenu into “noConflict” mode and it may resolve your issue (Appearance > UberMenu > Theme Integration > Run jQuery in noConflict Mode)

Hi Matt,

Glad you got the IE issues resolved. Might be something where you’d need to rebuild the cache whenever you make a change, as caching programs pack all the CSS together and can sometimes make a mess of things.

Here are some styles that will likely be useful for you:

/* Level 2: Column Headers */
#megaMenu ul li.ss-nav-menu-mega ul.sub-menu-1 > li > a

/* Level 3: Headers */
#megaMenu ul li.ss-nav-menu-mega ul ul.sub-menu .ss-nav-menu-header > a

/* Level 3: Normal Links */
#megaMenu ul li.ss-nav-menu-mega ul ul.sub-menu li a

/* Widget Area Titles */
#megaMenu .wpmega-widgetarea h2.widgettitle

Also, a really useful tip for styling in Firebug is to temporarily set your dropdown trigger to “click” – this allows you to expand the submenu and investigate it in Firebug at your leisure

Hope that helps!

Chris

Responded to your other thread below

Hi Steve,

Sorry to hear you’re having trouble with the new version. I can assure you it is fully functional The effect you are experiencing can happen if your theme isn’t coded to proper WP standards. UberMenu 1.1 uses jQuery noConflict for compatibility purposes, but sometimes themes haven’t been coded in noConflict mode and can cause problems. I’ll try to put together an update that makes this optional to support themes that have this issue.

Best,

Chris

Steve, just wanted to let you know that I just made a quick update to UberMenu and it is currently in the review queue. The update defaults to not using noConflict mode, but will allow you to switch it on in the control panel if necessary for a particular theme. It might take a few days to get reviewed, but I wanted to let you know it’s on its way.

Hopefully that’ll help out users in your position

Chris

I took a look at the site code, and you’re right, it does seem you’re using the old version (1.0.3). If you’ve downloaded the plugin since last Friday, you should have had the new version. I have heard of caching issues like that before. Anyway, I would try downloading 1.1 again – you can tell the version quickly by the download file name (the new one should be named ubermenu-wordpress-mega-menu-plugin.zip ). If you’re still getting the old version (UberMenuPackage.zip), shoot me an email through my contact form and I’ll send you the new version via email – and I’ll let support know about the glitch!

I’d definitely recommend upgrading to 1.1 though. There is an IEFix script in 1.0.3 that sometimes caused issues in IE with certain themes (I’ve never seen it crash IE, but that could be your issue). This has been fixed in 1.1, so that’s the first thing I’d try.

Let me know – and sorry for the download glitch!

Chris

Greetings DeBole1032,

Thanks for your purchase! I took a look at your site, and the menu looks properly styled to me. Perhaps you already figured it out since you left the message? If not, maybe send me a message through my contact form and point out where the issue is.

Thanks!

Chris

Great to know, I’ll holler the moment I’m ready to pull that trigger.

Two questions before I buy your menu. Is there a way for me to embed HTML into the menu, for instance, if I wanted to put in a table or some special div setup? Also, if you answer in the affirmative for the first question, how do I go about discussing next steps for the black out option we previously talked about with the Adidas site?

Actually never mind about that first question I went ahead and bought it. I just realized I could make a widgetized area for HTML insertion. So if you could just let me know about the second question that would be great.

Like you said, using a widget would be the optimal way to put whatever HTML content you want into the menu.

If you’d like to discuss customization options, rates, and time estimates, please contact me directly via my contact form on my profile page. Please note that I will be traveling Tuesday and Wednesday of this week, and may not be able to respond until I return home on Thursday.

Best,

Chris

Greetings htdl,

I took a look at your site. What’s happening is that Nivo Slider is including an extra copy of jQuery, and this is causing conflicts. You can see these lines in the code:

<script src="http://s357873246.websitehome.co.uk/wordpress/wp-content/scripts/jquery-1.4.3.min.js" type="text/javascript"></script>
    <script src="http://s357873246.websitehome.co.uk/wordpress/wp-content/scripts/jquery.nivo.slider.pack.js" type="text/javascript"></script>

The top line, which includes a duplicate jQuery, should be removed. Also, it’s generally best to put script calls in the head of the document or else in the footer, but not in the middle of the page.

Anyway, I think removing the extra jQuery line will take care of your problem. Only question is if Nivo Slider is compatible with the latest version of jQuery included with WP 3 .1. If it isn’t, you’d need to deregister the default WP jQuery script and register the old version of jQuery instead (UberMenu should work on either). If you have further questions on that feel free to contact me via my contact form

Hope that helps,

Chris

Hi DrewAPicture,

Thanks for the feedback! Always appreciated I’ll take these into account for the next iteration of UberMenu.

First off, I assume you’re referring to the Style Generator in all of these?

1. Top Level Menu Highlighting – So would you want to be able to highlight like the “highlight” checkbox that appears on sub menu items, or highlight as in the current page item? Highlight color or background or both?

2. Gradient for top-level hover – this was originally a feature in UberMenu. Unfortunately, there is a gradient bug in IE (of course) that breaks dropdowns when used on top-level item hover, so I removed it (boy did that take a long time to track down the problem). That’s why all the presets have the functionality that they use CSS background gradients in supported browsers and images in IE. Frustrating but it’s the reality of working with IE, unfortunately. Your best bet here is to use background images.

3. I thought there was already this feature but I’ll go back and look at it. Unfortunately not every style can be included in the Style Generator (it’d become way too complicated) but this might be a good one to add in if it’s not already

Thanks for your input!

Chris

You can target different levels using the list item depth classes, for example:

#megaMenu ul li.ss-nav-menu-item-depth-1 > a{
  //Depth 1 = Submenu column headers
}

#megaMenu ul li.ss-nav-menu-item-depth-2 > a{
  //Depth 2 = Submenu column items
}

The submenus also have depth markers, e.g. ul.sub-menu-1

Hope that helps,

Chris

Greetings,

Thanks for your interest. The short answer to your question is yes, you could insert an UberMenu anywhere, with two caveats: (1) You’d need to edit a little PHP (usually one line) and (2) You can only place one UberMenu per page.

The longer answer is that WP3 Nav Menus have two important parts: menus and menu locations. Themes register one or more menu locations and they control where those locations occur in the code. This allows you to create a menu and place it in a registered menu location (in Appearance > Menus). UberMenu’s plug-and-play capability comes from hooking into the the theme’s menu locations and replacing the default menu with an UberMenu.

Sometimes themes don’t register menu locations properly, which means UberMenu can’t hook in. For those situations, UberMenu has a feature called “Easy Integration”. It registers a brand new menu location automatically, and all you need to do is place one line of code, uberMenu_easyIntegrate() in your theme template to “print” the menu. So in your situation, you could still use this “extra” menu location and just pop that PHP code in wherever you want your menu to appear (usually in header.php).

I’m not sure exactly what you mean by “WordPress Structures”. If you mean page, post, and taxonomy hierarchies, WP3 Nav Menus are completely customizable and are not restricted by these structures. However, all UberMenus must be designed and “structured” through the WP3 Nav Menu control panel drag and drop interface (Appearance > Menus).

Of course, all of this requires Wordpress 3.

I hope that answers your question

Chris

That’s a pretty good (and quick) and sizable answer. I’ll go ahead and snag it and see what I can do. At that price the worst that happens is I learn something

Thanks again!

Hi Burundukas,

For #1 and #2, send me a link to your site via my contact form and I’ll take a look at your CSS . #1 is something that should be easily fixable for vertical menus and #2 works for me, so perhaps you have some theme styling that is blocking the background hover.

3 – to get an item with no linking just create a custom item with URL set to #. If you set the trigger to ‘click’ in Appearance > UberMenu the submenu will open when it is clicked

Chris

Thanks for the fix! now everything is good.

Thanks! Glad it helped you out

I’m sorry, I don’t understand the question. All of the styling materials in the demo are included in the plugin. The manual explains how to set up all types of menu items: http://wpmegamenu.com/help/#MEGA-adding-content

2 things, When adding an image say 17px square, it pushes my menu down text down instead of being beside it like your icons in the demo.

Also how to add the search bar? I’ve tried a custom link menu but get all the menu names showing.

How to have just the search bar showing like in your demo?

Thanks for clarifying

For the displaced menu item text, that sounds like there might be some residual styling from the theme that is affecting the menu? If you can send me a link to your site, I’ll take a look firsthand. It may be a clear or incorrect padding that is affecting things.

As for the search bar, I just wrote up a little help item in the support manual to help you out Basically, use the --notext-- as the Menu Item text and set the Search box’s title to ’ ’. See http://wpmegamenu.com/help/#MEGA-mega-widgets-top for more info.

Hope that helps

Chris

Feel free to send me a link and I’ll take a look

I wouldn’t recommended changing the menu text tags to headings (H4s), but if you want to change that you’d need to update wpMegaWalker.php

Changing the font size can be done via CSS . For example, this style would target the top level menu items:

#megaMenu ul.megaMenu > li > a{
  font-size:20px;
}

There are some general tips on changing the styles in the support guide: http://wpmegamenu.com/help/#MEGA-custom-styles – I’d especially recommend using Firebug to target and test your styles right in the browser: http://wpmegamenu.com/help/#MEGA-firebug

Hope that helps

Chris