| 开发者 | wpxero |
|---|---|
| 更新时间 | 2026年10月11日 12:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
nav_menu) and block Navigation menus (wp_navigation) — both normalised to the same tree shape.[menuverse_mobile_menu] or [menuverse_bottom_menu].menuverse_the_mobile_menu() or menuverse_render( 'bottom_menu' ).prefers-reduced-motion on every animation.menuverse/v1, and dashboard SlotFill points are documented in docs/extension-points.md for companion plugins and a Pro tier.
/wp-content/plugins/menuverse/ or install it from the WordPress plugin directory.[menuverse_mobile_menu]
[menuverse_bottom_menu]
Template tags
<?php menuverse_the_mobile_menu(); ?>
<?php menuverse_the_bottom_menu(); ?>Install MenuVerse, open MenuVerse in the admin sidebar, and enable the Bottom Menu module. Pick a ready-made look, choose what each button points at — a link, a page, or a search sheet — and save. The bar appears on mobile straight away; you can also place it yourself with a block, a shortcode, or a template tag if you would rather control exactly where it renders. No theme files are edited and no code is required.
Yes, and it fixes a problem block themes have. Block themes do not register Appearance → Menus, so WordPress hides that screen — which is also where per-item icons and badges are edited. MenuVerse restores it when your theme leaves it out, and does nothing when your theme already has it. MenuVerse also reads block Navigation menus (wp_navigation) directly, and registers native blocks you can drop into any template in the Site Editor.
No. MenuVerse displays menus you already built — classic menus under Appearance → Menus and block Navigation menus. It never copies or replaces your menu storage.
Enable the Mobile Menu module, pick one of your existing menus, then either turn on automatic insertion or place the MenuVerse Mobile Menu block (or [menuverse_mobile_menu] shortcode) where you want the button to appear. Set the breakpoint to match when your theme’s desktop menu should take over.
A bottom navigation bar — sometimes called a tab bar or mobile footer menu — keeps your most important links thumb-reachable on phones, the way native apps do. MenuVerse’s bottom bar supports icons, labels, a More drawer, and action buttons like search, call, and chat alongside ordinary links.
No, when configured normally. Disabled modules load nothing. Enabled modules enqueue assets only on pages where they actually render. With every module off, MenuVerse adds zero bytes to the frontend.
Yes. MenuVerse outputs scoped markup and its own CSS custom properties, so global theme rules for button and a do not override it. You can also hide your theme’s menu on small screens when the mobile menu takes over.
Yes. When WooCommerce is active, a bottom-bar button can show a live cart count badge fetched from the WooCommerce Store API — safe under full-page caching because the count is per visitor.
MenuVerse registers native WordPress blocks, so it works anywhere blocks or shortcodes work — including the Site Editor, block themes, and most page builders that respect core blocks or shortcodes.
Yes, with Pro. Both the mobile menu and bottom bar support show-everywhere, only-on-these-pages, and everywhere-except rules when using automatic insertion, and page rules are part of MenuVerse Pro. A menu you place yourself with a block or shortcode always shows where you put it, on any tier.
Yes. Under MenuVerse → Tools, export your settings as JSON and import them on another site. Menus, mega panel content, and media are not included — a settings file cannot carry them meaningfully across sites.
Only if you choose to. Turn on Delete data on uninstall under Tools before deleting the plugin. It is off by default so uninstalling never destroys your configuration by surprise.
Yes. Free builds a menu that works: an off-canvas panel that opens, closes, and looks like the site it is on, and a bottom bar of up to four buttons with an icon, wording, a colour, a height, a corner radius, and a marker for the current page. MenuVerse Pro, a separate plugin, adds where a menu appears and who sees it (page rules, per-button visibility by role or sign-in state), what a button can do besides open a link (WhatsApp, phone, Popup Maker, a slide-up panel), every finish beyond one colour (gradient, frosted glass, a background picture, shadows, dark mode, per-button colours), the extras inside the mobile panel (search, social links, free text), live cart and wishlist counts, and the fifth button onwards. Your saved settings are never deleted when Pro is inactive, and nothing is truncated in the database. Gated options simply fall back to their defaults on the frontend, and rows past the free limit stay stored and editable, until a licence is active.
Yes. Modal surfaces use focus traps and return focus to the trigger when closed. Animations honour prefers-reduced-motion. Layout uses CSS logical properties so the same stylesheet works for left-to-right and right-to-left sites.
Each mega panel will be a dedicated post type entry edited with the block editor inside the MenuVerse dashboard, giving you revisions and the full block library. The mega menu module is marked Coming soon in the dashboard until it ships.
menuverse_hide_admin_notices and menuverse_current_url filters, and a --menuverse-bar-ring custom property.menuverse_classic_menus_screen filter turns this off for sites that build their navigation as block menus.