✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Max Mega Menu: menu locations, items, and themes as tables

Max Mega Menu builds on WordPress nav_menu terms with extra term meta, item meta, and theme settings in wp_options. SleekView surfaces the whole menu footprint as one queryable table for audits and bulk edits.

♾️ Lifetime License available

SleekView table view for Max Mega Menu

Every menu item in one workspace

Max Mega Menu extends core WordPress menus, which live as terms in the nav_menu taxonomy, with items stored as nav_menu_item posts in wp_posts. Mega menu settings sit in term meta and post meta, while themes and global config land in wp_options under keys like megamenu_themes and megamenu_settings. The default WordPress admin treats each menu as a separate drag-and-drop screen with no cross-menu visibility.

SleekView reads every nav_menu term, all nav_menu_item posts, plus the Max Mega Menu options and joins them into one filterable table. Filter by location to audit which menus actually fill a registered slot. Filter items by mega-enabled flag to find which menus use the mega features versus standard dropdowns. Sort items by depth to see flat menus versus deeply nested ones at a glance.

Inline edits to label, URL target, and menu order write through standard WordPress menu APIs so any Max Mega Menu cache invalidation hooks fire as expected. The mega menu visual layout itself still lives in the plugin's own editor, but the surrounding metadata is fair game for housekeeping and audits.

Workflow

From five menu screens to one navigation audit

1

Read every menu and item

SleekView pulls all nav_menu terms, nav_menu_item posts, plus megamenu_* options into one queryable view. The full menu footprint lands in one place.
2

Add audit columns

Location, depth, mega-enabled flag, theme, target object, and last edited become first-class columns. Filter chips replace flipping between drag-and-drop screens.
3

Save navigation views

Pin a mega-enabled-items view, a broken-links view, and a location-coverage view. Each audit becomes a one-click slice instead of a manual walkthrough.
4

Inline-edit items

Update labels, URLs, and CSS classes from the row. Edits route through WordPress menu APIs so any Max Mega Menu invalidation and caching hooks fire normally.

Sample columns

A typical menu items view

Items across every nav_menu with their mega-enabled flag and theme.
Source: wp_terms + wp_term_taxonomy (nav_menu) + wp_posts (post_type=nav_menu_item) + wp_options (megamenu_*)
Item Menu Location Depth Mega enabled Status
Products Primary primary 0 Yes Active
Pricing Primary primary 0 No Active
Old offers Footer footer 1 No Hidden
Resources Primary primary 0 Yes Draft

Comparison

Default Max Mega Menu admin vs SleekView

Default Max Mega Menu admin

  • Each menu is a separate drag-and-drop screen with no cross-menu view
  • No filter to see which menus use mega features versus standard dropdowns
  • Theme assignment per menu isn't visible in any list
  • Bulk reordering or relabeling items across menus is manual
  • Stale items in unused menus stay hidden inside nav_menu_item posts

SleekView

  • All menus and items across nav_menu in one table
  • Saved views for mega-enabled items, location coverage, and hidden items
  • Inline edit label, URL, and menu order on nav_menu_item posts
  • Filter by location, depth, theme, or mega-enabled flag
  • CSV export of any menu audit slice for handovers

Features

What SleekView gives you for Max Mega Menu

All menus in one grid

Every nav_menu term and its nav_menu_item children land in one filterable table. Location coverage and item depth become columns instead of clicks across menus.

Mega versus standard filter

Filter by the Max Mega Menu mega-enabled flag to scope the grid to items that actually use mega layouts. Audits stop guessing which menus rely on the plugin and which just use plain dropdowns.

Inline label and URL edits

Rename items or fix broken URLs without dragging them in the menu editor. Edits route through WordPress menu APIs so Max Mega Menu cache invalidation runs as designed.

Audience

Who uses SleekView for Max Mega Menu

Agencies

Audit menu coverage and mega usage across client sites without opening each menu screen. Per-client saved views keep handovers consistent across dozens of installs.

Editorial teams

Track which menu items point at which campaign pages from one workspace. Bulk relabel items at the start of a season instead of clicking through five separate menus.

Site operators

Catch menus assigned to locations that no longer exist and items pointing at trashed pages. A weekly pass through the saved-view grid keeps navigation clean.

The bigger picture

Why menu audits get ignored until they break

Navigation is the most visible part of any WordPress site, but it's also the most neglected from an audit standpoint because WordPress core's menu editor is designed for editing one menu at a time. Max Mega Menu adds power on top of that surface (mega panels, themes, per-item settings) but inherits the same one-menu-per-screen workflow. Items pointing at trashed pages stay listed until someone clicks through every menu.

Locations assigned to menus that no longer exist sit dormant. Mega menu themes drift across menus when nobody compares them side by side. Agencies running Max Mega Menu across dozens of client sites and in-house teams running it on a single high-traffic site face the same audit debt.

A queryable inventory changes the cost of menu audits from a manual walkthrough to a one-pass review. Filter mega-enabled items and check that each one still maps to a live destination. Compare theme assignment across menus in one column.

Spot orphan items and prune them in batches. The data already exists in nav_menu_item posts and megamenu_* options; the grid just gives it a working surface.

Questions

Common questions about SleekView for Max Mega Menu

Menus and items live in core WordPress tables (wp_terms, wp_term_taxonomy, wp_posts with post_type=nav_menu_item). Mega menu settings extend those with term meta and post meta, plus options like megamenu_themes and megamenu_settings in wp_options. SleekView reads all of those so the whole menu surface lands in one table.

 

Yes. Label, URL, target, CSS classes, and menu order are inline-editable on nav_menu_item posts. Edits go through the standard WordPress menu APIs, so Max Mega Menu cache invalidation and any third-party menu hooks run as designed.

 

Yes. Each menu carries the Max Mega Menu theme assignment as a filterable column, pulled from term meta and the megamenu_themes option. Audits can scope to menus on a specific theme to verify visual consistency across a multisite or agency client base.

 

Yes. SleekView reads the per-site nav_menu terms and nav_menu_item posts on each blog, so the same audit grid works across a multisite. Saved views can be scoped per site or shared across the network depending on user permissions.

 

Yes. SleekView joins each nav_menu_item to its target object (page, post, custom URL) and surfaces broken references as a saved view filter. Cleaning up dangling menu items used to require checking each menu visually; the grid turns it into a one-click pass.

 

Yes. The grid handles menu items and their metadata. The mega submenu layout (rows, columns, widgets per item) still lives inside the Max Mega Menu editor where the visual controls belong. SleekView never touches the mega layout data; it only surfaces and edits the surrounding menu structure.

 

Yes. Every view exports to CSV with your visible columns, including location, depth, mega-enabled flag, and theme. Agencies use these as menu audit deliverables; in-house teams use them as the input to navigation redesigns.

 

No. SleekView is read-mostly for menu structure and writes only through standard WordPress menu APIs. The front-end menu render, the Max Mega Menu cache, and any related wp_nav_menu filters all run unchanged because nothing about their loading path is bypassed.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView