Common Symptoms

Click the [+] to see more specific symptoms. Click a symptom to see potential diagnoses.

UberMenu
Symptom Details
UberMenu Troubleshooting Symptoms
- Google Maps display issue
  Symptom Details
  The map is either not displaying, or is not drawn completely.
- jQuery/javascript errors
  Symptom Details
  A javascript error is printed in the javascript console.
- [+] Styles don't look like the demo
  Symptom Details
  Because we're injecting a chunk of HTML into a theme's markup and replacing an existing menu, the theme (or other plugins) CSS styles, javascript, or PHP functions can affect how the menu displays. Generally, themes that are written with modularity in mind don't have this issue.
  - No animations
    Symptom Details
    The submenu opens when hovering over a top level menu item, but the animations do not occur.
  - Menu items completely unstyled
    Symptom Details
    The menu items are present, but they are not styled at all like a menu - they just display as an unordered list.
  - Styles present but not like demo
    Symptom Details
    It is clear that the UberMenu styles are being applied, but they don't look like the demo - this indicates that other styles (from the theme or another plugin) are also affecting the look of the menu.
- [+] Submenus (dropdowns) not displaying
  Symptom Details
  The submenus are not appearing when the top level menu item is activated (hover or click).
  - Javascript error
    Symptom Details
    Any javascript error can prevent UberMenu's javascript from running, resulting in the submenu not opening. Javascript errors are displayed in your browser's javascript console.
  - Submenu partially obstructed
    Symptom Details
    The submenu can be seen to open, but part of it is hidden behind other elements of the site.
  - Submenus display but third level menu items are hidden
    Symptom Details
    The submenus open, but the third level menu items remain hidden until hovering over their parent second level menu items.
- Internet Explorer display problem
  Symptom Details
  There is a display issue, specifically in a version of Internet Explorer (IE).
- Can't Expand Responsive Menu Toggle
  Symptom Details
  When you click the collapsed "Menu" button on a mobile device, nothing happens and the menu items are not revealed.
- UberMenu does not appear
  Symptom Details
  UberMenu replaces the existing menu by targeting a theme_location on a specific wp_nav_menu call. Because we're injecting the menu markup into the middle of a theme template, the theme's CSS, javascript, and PHP code can affect the rendering of the menu.
- UberMenu and Theme Menu Both Appear
  Symptom Details
  When using a responsive theme, UberMenu and the theme menu both appear once activating UberMenu.
- Menu is not positioned properly
  Symptom Details
  The menu does not appear in the expected location
- Style Generator Color Picker Won't Work
  Symptom Details
- Current submenu open by default
  Symptom Details
  When visiting a page, the submenu of the current menu item opens automatically without it being triggered by the user.
- UberMenu appears twice / duplicated
  Symptom Details

Diagnosis

Invalid doctype

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.

Background

The doctype lets the browser know what standards your HTML document is following. While most browsers are pretty lenient in this regard, Internet Explorer likes to explode if you haven’t done everything perfectly.

The Problem

If your doctype isn’t properly formatted and detectable, Internet explorer reverts to Quirks Mode, an awful browser rendering similar to IE6. Common causes:

Invalid document type – your doctype has to be one of the approved HTML doctypes
Missing doctype – your site does not include a doctype
Doctype isn’t the first element in the source

If any of the above are true, your site is going to render like it’s 1999 in Internet Explorer.

Identifying the issue

View your source and take a look at the first line. If the doctype declaration is not the first element in the document (before the opening >html< tag), isn’t present, or is malformed, that’s your issue.

The Solution

Make sure that you have a valid doctype and that it is the first line in your HTML.