UberMenu 3.0 requires jQuery 1.11.1 or higher (but less than jQuery v2), which should automatically be included with WordPress 3.9 or higher. If your theme or another plugin has changed the jQuery version, that can cause javascript errors that can break the menu as well as other javascript component on your site.

If the theme is setting overflow:hidden on one of UberMenu’s ancestor elements, it can effectively cut off the submenus, either partially or from displaying at all.

When HTML elements overlap on the page, they have to be layered – one element has to be in front of, and the other behind on the z-axis. The element on the bottom may be hidden by the element on top. If UberMenu appears below other elements on your page, it means you need to set the z-index appropriately for adjacent containers. Most of the time, the containers to be adjusted are part of your theme and your CSS style won’t include any UberMenu selectors.

If a WordPress theme does not include the required hooks (wp_footer), UberMenu can’t load its javascript, so javascript functionality like animations, triggers, and maps will be lost.

If a WordPress theme does not include the required hooks (wp_head), UberMenu can’t load its stylesheets, so the menu won’t be styled.

Internet Explorer can only load 31 stylesheets per page. If your theme or another plugin is loading a large number of stylesheets, and the limit is reached before UberMenu’s stylesheets are loaded, UberMenu’s styles will not appear at all in Internet Explorer, because IE has ignored those stylesheets entirely.

If your theme’s menu styles are based on a hard-coded element wrapping the menu, those styles will still apply after replacing the menu markup, and will conflict and negatively impact the style and functionality of the menu.

If you disable jQuery Enhancements, you will lose all javascript functionality in the menu, including animations, maps, non-hover triggers, and the responsive menu toggle expansion.

If the basic.css file has been disabled in the Control Panel, the menu will not function properly if the styles have not been included elsewhere.

Because Flash objects are always layered above all other HTML elements, if they overlap with your submenu, the submenu will be partially obstructed.

If another plugin or your theme throws a javascript error before UberMenu’s javascript has been executed, it will prevent UberMenu from functioning properly, including submenu positioning, click events, responsive menu toggling, and more.

If two or more plugins (or theme) load the Google Maps API, and the library is loaded twice, a javascript error will occur and the maps will stop working.

UberMenu setup requires you to select which Theme Location to target and turn into an UberMenu in Appearance > Menus. If you do not select a Theme Location, UberMenu will not be applied to any menu on the site.

The wp_nav_menu() call in the theme MUST use the theme_location parameter for UberMenu to be applied to that menu.

If a theme’s wp_nav_menu() call uses the menu parameter, the critical theme_location parameter will be ignored – and therefore UberMenu cannot target the menu.

Some themes call wp_nav_menu twice with the same theme_location parameter – doing so may have strange results.

Some themes will manipulate the UberMenu output in a non-standard way, resulting in breaking the menu style, layout, and functionality, as the markup is not as expected.

If the menu is printed in HTML5 mode, IE will require something like the HTML5 shiv to properly render HTML5 elements; older versions do not support HTML5 elements out of the box.

If the doctype cannot be properly interpreted by IE, IE will revert to Quirks mode, which will essentially display the site as IE6. The document must have a valid doctype, and it must be the first line in the file.

If you have an HTML syntax error in your menu (generally introduced via a widget or a content override), IE may seem to stop rendering the menu half way through (at the point of the error), leaving the remainder of the menu unstyled.

If your submenu is hidden or partially obstructed in IE only, it’s likely that you have a z-index issue manifesting only in Internet Explorer. See z-index

You can NOT use IE gradient filters on your menu bar. If you add an IE filter to your menu bar in order to create a gradient, IE will automatically treat that element as overflow:hidden, no matter what CSS settings you change. This effectively chops off the submenu and prevents it from displaying.

UberMenu replaces the markup of the menu in your theme. However, it also replaces the CSS styles. If the position of the theme’s menu was determined by absolute positioning rather than relative positioning, the menu may not appear in the expected location.

Some themes’ menu javascript will still affect the menu even after UberMenu has replaced the default menu. As a result, UberMenu can appear distorted, the styles can be incorrect, extra markup may be added, and the functionality may break.

WordPress, your theme, or another plugin may be running autop or textualize filters on the map HTML, which adds extra BR elements and breaks the map output. Upgrade to the latest version of UberMenu (2.2.1.0 or later) to resolve the issue.

When you’re using a modular system like WordPress, it’s important that all jQuery is compartmentalized and running in noConflict mode in order to avoid conflicts. When other themes/plugins don’t follow this standard, you’ll get jQuery errors that break other scripts, like UberMenu.

When two elements overlap, one has to be on top. The one on the bottom may still be visible if the top element is transparent, but the bottom element can’t be interacted with because click/hover events are applied to the top level element and are blocked from the one below it.

Sometimes, a theme or plugin will use a filter to strip out the standard WordPress menu item classes like menu-item. When these are removed, UberMenu’s styles, which rely on these classes, cannot be applied. Themes and plugins should never remove core functionality.

When other plugins/themes load their javascript on pages that aren’t their own, they can break things.

To set the color, you need to click the color wheel in the lower right corner of the color picker.

Some theme strip out core menu classes like the current-menu-item classes and replace them with their own ‘active’ class. This forces the menu open on page load.

In some cases, the theme’s CSS will set the menu to display:none;, which will hide the menu even when the toggle tries to expand it. For full details, please see the Knowledgebase: Residual Styling. Depending on the nature of the issue, you may need to use Manual Integration to prevent the theme from interfering.

Some themes call wp_nav_menu twice with the same theme_location parameter to produce separate desktop and responsive menus. UberMenu will replace both, and be visible as the theme’s mobile CSS no longer applies.