Title: MenuVerse – Mobile Bottom Menu & App-Style Navigation Bar Author: WPXERO Published: 5 Eylül 2026 Last modified: 19 Eylül 2026 --- Eklentilerde ara ![](https://ps.w.org/menuverse/assets/banner-772x250.jpg?rev=3681581) ![](https://ps.w.org/menuverse/assets/icon-256x256.png?rev=3681581) # MenuVerse – Mobile Bottom Menu & App-Style Navigation Bar [WPXERO](https://profiles.wordpress.org/wpxero/) tarafından [İndir](https://downloads.wordpress.org/plugin/menuverse.0.4.0.zip) * [Detaylar](https://tr.wordpress.org/plugins/menuverse/#description) * [Değerlendirmeler](https://tr.wordpress.org/plugins/menuverse/#reviews) * [Kurulum](https://tr.wordpress.org/plugins/menuverse/#installation) * [Geliştirme](https://tr.wordpress.org/plugins/menuverse/#developers) [Destek](https://wordpress.org/support/plugin/menuverse/) ## Açıklama **MenuVerse** adds an app-style **mobile bottom menu** — the fixed **bottom navigation bar** your visitors already know from every phone app — and a proper off-canvas ** hamburger mobile menu**, from one dashboard, with no code. Most mobile visitors never open a hamburger menu. A **bottom navigation bar** puts your important pages one thumb-tap away instead: shop, cart, search, account, call. MenuVerse gives you both patterns and lets you use either one, or both together. It builds them from the menus you already maintain under **Appearance Menus** and the block **Navigation** menus WordPress stores as posts. Nothing is copied and nothing is rebuilt in a second admin screen. You keep editing menus where you always did; MenuVerse only controls how they appear on the frontend. Switch a module off and it registers no hooks, enqueues no assets, and outputs nothing. A page with no MenuVerse menu on it downloads no MenuVerse bytes. #### Available now **Bottom Menu** — an app-style **bottom navigation bar** pinned to the viewport on mobile. * Four buttons free, with a **More** drawer for overflow items or a bar that scrolls sideways; more buttons with Pro. * Built-in icon library — no icon font, no CDN, no external requests. Pro can use your own images instead, including a second image for the current page. * Buttons can link to a URL, open a page, or launch a search sheet scoped to the site, WooCommerce products, or Easy Digital Downloads. Pro adds WhatsApp, phone, Popup Maker, and a slide-up panel of your own content. * Five ways to mark the current page: colour, pill, top line, underline, or a raised button — the line and the raised button are Pro. * Optional per-button labels above or below the icon, custom badges, and safe-area padding for notched phones. * Ready-made looks to start from, then fine-tune colours, spacing, and behaviour in a step-by-step dashboard. * Pro adds the finishes beyond one colour (gradient, frosted glass, a background picture, shadows, padding, alignment), a second palette for dark mode, per-button colours, live cart and wishlist counts, per-button visibility by role or sign- in state, and page rules. **Mobile Menu** — a responsive **hamburger menu** and off-canvas panel for phones and small tablets. * Slides in from the left or the right; overlays the page (full screen and push are Pro). * Animated trigger icons (bars, dots) with a squeeze transition; spin and arrow are Pro. * Optional top bar with your logo or site title; custom wording, sticky and hide- on-scroll are Pro. * Accordion submenus that open at the branch the visitor is already on. * Body scroll lock, focus trap, and focus return for keyboard and screen-reader users. * Configurable breakpoint, and a choice of menu per module. * Pro adds the search field, a row of social profile links, free-text inside the panel, swipe-to-close, page visibility rules, and hiding your theme’s own menu on small screens. #### Works on block themes, not just classic ones Block themes (Twenty Twenty-Four, Twenty Twenty-Five and every full site editing theme) do not register **Appearance Menus** at all — WordPress hides that screen unless the theme asks for it, so on a block theme there is normally no way to build a classic menu, and no way to reach the per-item icon and badge fields WordPress only offers there. MenuVerse puts that screen back when your theme leaves it out, and leaves it alone when your theme already has it. Nothing is added twice, no fake menu location is registered, and classic themes are untouched. So the same setup works whether you run a block theme, a classic theme, or a hybrid. #### Coming soon **Mega Menu** — horizontal navigation whose items open full-width panels you build with blocks, folding to an accordion on small screens. Already visible in the dashboard as a preview of what is next. #### Works with the menus and tools you already use * **Classic menus** (`nav_menu`) and **block Navigation menus** (`wp_navigation`)— both normalised to the same tree shape. * Per-item extras in the menu editor: icon, badge, mega-panel link, and hide-on- mobile or hide-on-desktop flags. * **WooCommerce** — live cart count badge on a bottom-bar button (Store API). * **YITH WooCommerce Wishlist** — live wishlist count badge. * **Easy Digital Downloads** — scope a search button to downloads only. * **Popup Maker** — open a popup from a bottom-bar button. #### Four ways to place any menu Every module supports the same four entry points, all rendering through one pipeline so they never drift apart: 1. **Block** — drop a MenuVerse block in the Site Editor, a page, or a template. 2. **Shortcode** — `[menuverse_mobile_menu]` or `[menuverse_bottom_menu]`. 3. **PHP template tag** — `menuverse_the_mobile_menu()` or `menuverse_render( 'bottom_menu')`. 4. **Automatic insertion** — optional; off by default so nothing is silently injected into your theme. #### Dashboard built for non-developers * One admin screen with a **live phone preview** beside every setting step. * Guided onboarding on first run: pick a module, choose a menu, place it, save. * Import and export settings as JSON under **MenuVerse Tools** (settings only — menus and media stay on the site). * Optional **Delete data on uninstall**, off by default. #### Fast, accessible, and self-contained * **Conditional loading.** Assets enqueue only when markup is actually rendered. * **Tiny.** Each frontend module is under 6 KB gzipped (JavaScript and CSS combined); most are under 4 KB. * **Vanilla JavaScript** on the frontend — no jQuery, no React, no framework. * **Accessible.** Correct ARIA roles, keyboard navigation, focus management, and` prefers-reduced-motion` on every animation. * **RTL-ready.** Styled with CSS logical properties; one stylesheet works in both directions. * **Self-hosted.** Icons are SVG geometry shipped with the plugin. No CDN calls anywhere. #### Extensible Module registration, settings schemas, the render pipeline, REST routes under `menuverse/ v1`, and dashboard SlotFill points are documented in `docs/extension-points.md` for companion plugins and a Pro tier. ## Bloklar Bu eklenti 6 blok sağlar. * Mobile Menu An off canvas menu with a hamburger trigger, shown below a width you choose. * Mega Menu A horizontal menu whose items can open block built mega panels. * MenuVerse Navigation Build a menu from blocks. Add items inside it and nest them for submenus. * Vertical Menu A sidebar menu with collapsible groups and an optional sticky position. * Bottom Menu An app style navigation bar pinned to the bottom of the screen on small viewports. * Menu Item One link in a MenuVerse Navigation block. Nest items inside it to build a submenu. ## Yükleme 1. Upload the plugin folder to `/wp-content/plugins/menuverse/` or install it from the WordPress plugin directory. 2. Activate **MenuVerse** through the **Plugins** screen. 3. Open **MenuVerse** in the admin sidebar and follow the short setup walkthrough. 4. Place your menu with a block, shortcode, template tag, or automatic insertion. **Shortcodes** ``` [menuverse_mobile_menu] [menuverse_bottom_menu] ``` **Template tags** ``` ``` ## SSS ### How do I add a bottom navigation bar to WordPress? 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. ### Does MenuVerse work with block themes and the Site Editor? 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. ### Do I have to rebuild my menus in MenuVerse? No. MenuVerse displays menus you already built — classic menus under **Appearance Menus** and block Navigation menus. It never copies or replaces your menu storage. ### How do I add a hamburger menu to my WordPress site? 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. ### What is a bottom navigation bar and when should I use one? 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. ### Will MenuVerse slow my site down? 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. ### Does it work with my theme? 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. ### Does it work with WooCommerce? 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. ### Does it work with page builders? 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. ### Can I show the menu only on certain pages? 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. ### Can I move settings to another site? 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. ### Does uninstalling remove my settings? 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. ### Is MenuVerse free? 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. ### Is MenuVerse accessible and RTL-ready? 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. ### Where will the mega menu panel content be stored? 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. ## İncelemeler Bu eklenti için herhangi bir değerlendirme bulunmuyor. ## Katkıda Bulunanlar ve Geliştiriciler “MenuVerse – Mobile Bottom Menu & App-Style Navigation Bar” açık kaynaklı yazılımdır. Aşağıdaki kişiler bu eklentiye katkıda bulunmuşlardır. Katkıda bulunanlar * [ WPXERO ](https://profiles.wordpress.org/wpxero/) [“MenuVerse – Mobile Bottom Menu & App-Style Navigation Bar” eklentisini dilinize çevirin.](https://translate.wordpress.org/projects/wp-plugins/menuverse) ### Geliştirmeyle ilgilenir misiniz? [Kodu görüntüleyin](https://plugins.trac.wordpress.org/browser/menuverse/), [SVN deposuna](https://plugins.svn.wordpress.org/menuverse/) göz atın ya da [RSS](https://plugins.trac.wordpress.org/log/menuverse/?limit=100&mode=stop_on_copy&format=rss) ile [geliştirme günlüğüne](https://plugins.trac.wordpress.org/log/menuverse/) abone olun. ## Değişiklik Kaydı #### 0.4.0 * Dashboard redesign: a single colour palette and type scale across every screen, module cards with a preview sketch of what each module draws, and a “Settings” link on each one. * Support is now a screen inside the dashboard instead of a link that opened a new tab — it still opens Documentation and Contact support the same way when you follow those from other screens. * The “MenuVerse Pro” pitch was redrawn from front to back: a flat dark card in the sidebar and on the overview screen, and a row of what Pro adds instead of a long list. * Fixed a handful of dashboard buttons and links (the sidebar’s upgrade card, the site-status link, “Compare” on the overview) rendering with the wrong colour due to a styling conflict with the admin UI library — purely visual, nothing to do with settings or data. #### 0.3.0 * Block themes get **Appearance Menus** back. WordPress only shows that screen when the theme asks for it, and block themes do not — so on a block theme there was no way to build a classic menu, and no way to reach the per-item icon and badge fields, which WordPress only offers there. MenuVerse now asks for it when nothing else has. * Themes that already have the screen are left exactly as they are, including block themes that register their own menu locations and sites where another plugin has already done this. No menu location is added and no admin page is registered, so there is nothing that can appear twice. * “Create a menu” now opens Appearance Menus on block themes as well, instead of the site editor’s navigation screen — a block navigation menu cannot carry MenuVerse’s per-item icons and badges, so that was the wrong place to send you. * Developers: the new `menuverse_classic_menus_screen` filter turns this off for sites that build their navigation as block menus. * Renamed to “MenuVerse – Mobile Bottom Menu & App-Style Navigation Bar”. The old name led with “Mega Menu”, which is still marked Coming soon and renders nothing— the name and the plugin description now describe what actually ships today. #### 0.2.0 * Bottom bar: a slide-up panel of your own content behind a button, with the same one-at-a-time, Escape-to-close and focus-return behaviour as the search sheet. * Bottom bar: your own images instead of the bundled icons, with a separate image or library icon for the current page. * Bottom bar: per-button visibility — everyone, signed in, signed out, or named roles, read from the site’s own roles. Hidden buttons are left out of the markup, not hidden with CSS, so cached pages cannot leak them. * Bottom bar: a sideways-scrolling mode as an alternative to the More drawer. * Bottom bar: background picture with an optional colour wash, named shadow depths with their own colour, inline padding, item alignment, an explicit stacking order, and an icons-off option. * The free and Pro split now lives in one file and is stamped onto the settings schemas, so a setting can be free while only some of its answers need a licence, and a list can render its first rows free. * “Create a menu” now points at the site editor’s navigation screen on block themes, instead of a screen core never registered. * Dashboard: explanations moved into hints on their labels, groups collapse into fewer steps (the mobile menu goes from eight to five), one status chip per module card, and paid options are shown, disabled, and named rather than hidden. * Dashboard: the live preview can be switched off, remembered per browser rather than saved to the site. * Fixed: “(needs Pro)” printed as visible text beside every locked option. * Fixed: turning icons off while labels were already off left a row of blank buttons. * Continuous integration on PHP 7.4 and 8.2 plus Node 20, with render and Pro-gating tests. #### 0.1.0 * First public release. * Mobile Menu module: off-canvas hamburger menu with accordion submenus, search, social links, and swipe to close. * Bottom Menu module: app-style bottom navigation bar with More drawer, action buttons, and page visibility rules. * Dashboard with live preview, onboarding walkthrough, and settings import/export. * Classic and block Navigation menu sources with per-item icon and badge extras. * WooCommerce, YITH Wishlist, EDD, and Popup Maker integrations for bottom-bar buttons. * Gutenberg blocks, shortcodes, template tags, and optional automatic insertion for each module. ## Meta * Sürüm **0.4.0** * Son güncelleme **1 gün önce** * Etkin kurulumlar **10dan fazla** * WordPress sürümü ** 6.4 veya üstü ** * Test edilen sürüm **7.1.1** * PHP sürümü ** 7.4 veya üstü ** * Dil * [English (US)](https://wordpress.org/plugins/menuverse/) * Etiketler * [App Menu](https://tr.wordpress.org/plugins/tags/app-menu/)[bottom menu](https://tr.wordpress.org/plugins/tags/bottom-menu/) [bottom navigation](https://tr.wordpress.org/plugins/tags/bottom-navigation/) [hamburger menu](https://tr.wordpress.org/plugins/tags/hamburger-menu/)[mobile menu](https://tr.wordpress.org/plugins/tags/mobile-menu/) * [Gelişmiş görünüm](https://tr.wordpress.org/plugins/menuverse/advanced/) ## Puanlar Henüz inceleme gönderilmedi. [Değerlendirmeniz](https://wordpress.org/support/plugin/menuverse/reviews/#new-post) [Tüm değerlendirmeleri gör](https://wordpress.org/support/plugin/menuverse/reviews/) ## Katkıda bulunanlar * [ WPXERO ](https://profiles.wordpress.org/wpxero/) ## Destek Söyleyeceğiniz bir şey mi var? Yardım mı lazım? [Destek forumunu görüntüle](https://wordpress.org/support/plugin/menuverse/)