Jenst

<p>Settings:</p>
<ul>
<li>Mobile location</li>
<li>Mobile breakpoint</li>
<li>Background color</li>
<li>Text brightness</li>
<li>Logo as text or image</li>
<li>Logo and menu font family</li>
<li>Disable navigation, menu location, CSS, javascript</li>
<li>Hide on scroll, on or off</li>
<li>Custom CSS</li>
</ul>
<p>If you don’t want the HTML to go through the action wp_footer, place this somewhere after the beginning of your body-tag: <code><?php do_action('mn_nav'); ?></code>. It might be better for readability and perhaps SEO.</p>


Mobile Navigation

This broke my whole site on mobile mode.



Don't use if you are on hueman theme

A responsive fullscreen mobile menu navigation. Activate it for your custom made theme to save some time.

Ryan Hellyer

<h4>Features</h4>
<p>Caches the output of your menus. That’s it 😉</p>
<p>Specifically, it caches the output for every unique page. This allows the menus to retain the current/parent/child classes unlike most other menu caching plugins.</p>
<h4>Why should I use this plugin?</h4>
<p>If you want to cache your menu content obviously, but specifically if you want to cache your menu content <strong>and</strong> keep the current/parent/child page classes working. Most menu caching systems do not cater for keeping the various classes working, whereas this plugin does.</p>
<h4>Why shouldn’t I use this plugin?</h4>
<p>You should not use this plugin if you have a huge number of posts/pages on your site. The plugin caches each menu individually for each post. This can result in a huge number of cached menus on some sites, which could actually resulted in a slower site in those situations. It could also overload your object cache backend if it has insufficient memory to store them all.</p>
<h4>Languages</h4>
<ul>
<li>USA English</li>
<li>Deutsch (German) – thanks to <a href="https://github.com/serapath" rel="nofollow ugc">Alexander Praetorius</a> for providing this translation.</li>
</ul>


Mobile Navigation vs Menu Cache