Menu Cache
Features Caches the output of your menus. That’s it 😉 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. Why should I use this plugin? If you want to cache your menu content obviously, bu
About this tool.
Features
Caches the output of your menus. That’s it 😉
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.
Why should I use this plugin?
If you want to cache your menu content obviously, but specifically if you want to cache your menu content and 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.
Why shouldn’t I use this plugin?
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.
Languages
- USA English
- Deutsch (German) – thanks to Alexander Praetorius for providing this translation.
Getting started.
- 01Upload the complete ‘menu-cache’ folder to the ‘/wp-content/plugins/’ directory OR install via the plugin installer
- 02Activate the plugin through the ‘Plugins’ menu in WordPress
- 03That’s it. The plugin is now working 🙂
Visit the Unique Headers Plugin for more information.
Frequently asked questions.
Can I use this plugin to cache my widget areas too?
Nope. But luckily for you, Kaspars Dambis has created the Widget Output Cache plugin which does that for you.
How long are the menus cached for?
They are set to cache for one hour by default. You can change this by creating an extension plugin which extends the main plugin class and modifies the cache_time variable.
Why isn’t this baked into core WordPress?
Because it is not a good idea to cache a fresh menu for each page on some websites. If you don’t have many pages, then this is a perfectly acceptable way to handle menu caching. But if you have a large site with many pages, then there may be too many menus to efficiently cache.
