If your videos are dynamically created and inserted (with javascript, for instance), and they overlap an UberMenu submenu (or any content on your page) iOS won’t handle that nicely – the overlapped content will become unresponsive after you activate/play the video. Unfortunately, there is nothing to be done from an UberMenu standpoint – this is an issue with the way iOS handles dynamically inserted Flash objects and overlapping HTML elements. Here are some potential solutions for the issue – your mileage may vary: Potential Solution #1 Getting embedded Youtube videos to stay under your drop down menu – even with an iPad – if you are using embed code, this may work – just like the wmode fix presented above. Potential Solution #2 This Stack Overflow answer explains the dynamic insertion issue (see the answer with 18+ votes) : This solution has worked for some people, depending on the situation You can fix z-index on dynamically created videos by giving the video element -webkit-transform-style: preserve-3d Potential Solution #3 If your videos are dynamically inserted, insert them statically instead. The issue seems to only occur with dynamically inserted videos, based on reports. Potential Solution #4 If all else fails, you could write some javascript that will hide the video when UberMenu is in the hover state. Something like: But even this may introduce its own issues in iOS. Until iOS Safari becomes a more robust browser, this may simply be a limitation of having videos on your site If none of the above solutions work for you, unfortunately this issue seems unresolvable for the time being. This issue is due to the way mobile Safari handles video elements and focus layering. Until Apple resolves the issue with mobile Safari, there is no solution to my knowledge.

Please note that this is not an UberMenu issue. It is a server configuration issue. Unfortunately, there is nothing UberMenu can change to fix the issue. You’ll have to work out the solution to remove the POST vars limitation on your server or with your host. Hopefully this FAQ will point you in the right direction. Some users will experience a limit to the number of items they can add to their menu. Unfortunately, this manifests as all menu items after the first X (X may be 16, 72, 270, or any number), and the rest will be lost. This limit is NOT imposed by UberMenu. The limit is actually a server configuration issue. There are two common server configuration issues that can cause this problem. For an in-depth analysis of this WordPress/PHP issue, please refer to my detailed article on the subject: The WordPress Menu Item Limit or: Help! Half my menu items just disappeared! 1. max_input_vars As of PHP 5.3.9, there is a new PHP ini directive called max_input_vars (which does the same thing as Suhosin’s post.max_vars, below). By default, max_input_vars is set to 1000, which can easily be reached with the WordPress menu system. The solution is to add the following to your php.ini: (you might start by trying 3000) Alternatively, you can try placing this in your .htaccess. This won’t work on some servers, so your mileage may vary. 2. Suhosin This issue can also occur due to a program called Suhosin which runs on your server. This is a known issue with WordPress, and affects both the standard WordPress Menu System, as well as UberMenu, which is built on top of that system. In most cases, the solution is as simple as asking your host to increase the max_vars variables in your php.ini. Here are […]

UberMenu 2.0 includes some CSS3 transitions that make things smoother in modern browsers, for example the top level menu item tabs on hover. You’ll notice these effects in Chrome and Firefox, but not older versions of IE. If you wish to remove these transitions, add this CSS: Note that this is not the same as the submenu dropdown animation. You can turn that off in the UberMenu Control Panel if you wish.

In WordPress 3.3, the way Featured Images were handled changed, making the “Use as featured image” option in the Media Manager “disappear”. UberMenu 1.1.4 was released to make UberMenu compatible with the new WordPress release (please see the UberMenu change log at the bottom of the product page for more information). If you are still using UberMenu 1.1.3 or earlier, and have upgraded to WordPress 3.3, you have two options: upgrade to UberMenu 2.0 (see the important upgrade instructions), which you can download through your CodeCanyon Downloads page.

This is actually a built-in WordPress feature. In the Appearance > Menus screen, click Screen Options in the upper right. Then, under Show advanced menu properties, check “Link Target” Then check the “Open link in a new window/tab” option on your menu item Overview

Many responsive themes use the “responsive select menu” paradigm to display their responsive menus. This means that the theme actually prints two menus, and uses CSS media queries to only display one at a time. By calling wp_nav_menu twice with the same theme_location parameter, the theme produces two menus, only one of which will become an UberMenu. The second is now superfluous. Here’s what the setup usually looks like: Several situations may arise, depending on how the theme has setup its responsiveness: Both menus may be displayed at small sizes UberMenu may be hidden by the theme at small sizes UberMenu may be hidden at full size You have three options to resolve this: 1. Using only UberMenu UberMenu is already responsive, and does not require an additional menu. If you wish to use UberMenu’s responsive capabilities, you’ll need to find the secondary (responsive) wp_nav_menu call (normally in your theme’s header.php), and remove it. Now you’ll have a single menu controlled entirely by UberMenu. Be sure to remove any residual styling (see also: residual styling troubleshooting guide) in the process. 2. Using UberMenu with the theme’s responsive menu If you want to use UberMenu for wider screens and the theme’s responsive menu for mobile devices, you’ll need to do two things: If your responsive menu is printed first, and you aren’t getting an UberMenu at all due to the wp_nav_menu function being called twice with the same theme_location parameter, replace the wide-screen wp_nav_menu call with UberMenu Easy Integration. This creates a separate theme_location (called “UberMenu”), which we will activate – and then deactivate the theme’s standard theme_location. You’ll then (likely) need to apply CSS to hide UberMenu ( #megaMenu{ display: none; } or .main-menu-standard{ display: none; } ) for the appropriate size/media query. This will vary based on your theme, […]

Some users may experience a memory limit error. This means that your WordPress installation (core + theme + plugins) have overrun the memory limit allowed by your server. The error looks like this: Fatal error: Allowed memory size of XXXXXXX bytes exhausted (tried to allocate XXXXX bytes) in /path/to/function/file on line XXX Tip: You can check your PHP configuration settings by viewing the output of the phpinfo() function The solution is to increase the PHP memory limit on your server. There are several potential ways to do this: 1. php.ini Your server has a PHP initialization file (php.ini). To increase your memory, you change the memory_limit directive. Usually 64MB or 128M is a good amount. memory_limit = 64M The error message will indicate how many bytes (translate this to MB using Google if needed) your current system has allocated, and you can use this as a basis for how much you increase your limit. 2. wp-config.php WordPress offers a way to Increase memory allocated to PHP in your wp-config.php file. 3. Contact your host Depending on your host, you may or may not have access to php.ini, and they may disallow the wp-config.php solution. In that case, you will need to contact them directly to resolve the issue. If they refuse to increase your memory limit, you’ll either need to change your hosting plan or lighten your plugin/theme load to reduce the memory requirements of your installation. Please note that this is not a problem with UberMenu – the available memory is shared among all plugins, theme, and WordPress core running in your installation. As the different parts of your installation load, they use up your server’s capacity. The error simply occurs on the function that happens to send it over the limit. Often the function that puts it over […]

If you run into a PHP error, for example, an Internal Server Error, you’ll need to enable debugging on your WordPress site in order to identify the error in a meaningful way. To do so, edit your wp-config.php file as described here. Replace the part that normally sets WP_DEBUG to FALSE with Now re-do whatever caused the error, and then check the debug.log file (again, don’t forget to make sure the server can write to it!) The debug log normally gives a pretty clear explanation of the issue. The most common issues will be resolved by configuring your server properly, normally by increasing the memory_limit or max_execution time.

Recommended: If you are using a caching plugin, you should disable the Default to theme menu in IE6 setting in the UberMenu Control Panel > Theme Integration. You don’t want your caching plugin to cache a non-UberMenu version of the page. (Don’t forget to clear the server cache after changing the setting). If you have disabled the Default to IE6 setting and are still having issues, read on Some users have reported issues with caching plugins such as W3TC (W3 Total Cache). The symptom is that the menu is intermittently displayed as an unstyled list on cached pages. I’ve investigated this issue, and the cause is that the page caching program has not cached the UberMenu markup in the static cache file – instead, it seems to revert to either the theme’s markup, or some default markup for the menu, thereby resulting in the unstyled list of menu items. In other words, UberMenu is not being displayed at all. Codewise, UberMenu’s display is a combination of two things: HTML and CSS. The CSS (stylesheets) are still loaded; however, the static cached page does not display the UberMenu-generated HTML markup. As a result, there is nothing for the CSS to style (the elements which the CSS targets do not exist). The menu being displayed is not UberMenu at all, and that is the problem. To my knowledge, there is nothing UberMenu can do to change how the caching plugin chooses to cache the page. UberMenu follows all of the WordPress standards to create the menu markup (via filters and custom navigation walkers). Please note: I am not sure if this is an issue with the caching plugin itself, the underlying server caching modules, or with the way the plugin has been configured on a particular site. It takes some expertise to […]