Navigation
v2.0.2
Navigation
- Updates and support included for 12 months
- License key delivered immediately by email
- 30-day money-back guarantee
- Full documentation included
- Compatible with Hyvä themes
- Composer-ready installation
Navigation
Build your storefront menus from the Magento admin instead of editing templates. This module replaces the default Hyvä top menu with a database-driven navigation you manage entirely from the back office — create as many menus as you need, organise items to any depth, and switch between simple dropdown, full-width megamenu, or stacked layouts without touching a single line of code.
Each menu is referenced by an identifier (e.g. main_menu, footer_menu), so the same module can drive your header, your footer, and any sidebar from one screen. Labels, URLs, and SEO titles are stored per store view, which makes it a natural fit for multi-language stores where the same menu node points to a different page in FR, EN, and NL.
Who it's for
- Merchants on a Hyvä frontend who want to edit navigation without a developer
- Multi-store / multi-language shops that need per-store-view labels and URLs on the same menu structure
- Catalog-heavy stores that want a megamenu mixing curated links with live category branches
Key benefits
- Multiple menus, one screen — define unlimited menus, each with its own identifier, and render them anywhere in your theme by name.
- Three layouts per menu — Simple (dropdown panels), Megamenu (full-width column grid, 1–6 columns), or Stacked (vertical sidebar / footer). Switch layout from a dropdown; no XML edit.
- Unlimited depth — items nest to any level through a parent/child tree, with per-item position, active toggle, and "open in new tab".
- Live category branches — flag an item as a category source and its children are pulled straight from the Magento category tree (configurable root and max depth), so the menu tracks your catalog automatically.
- Per-store-view content — every item carries its own label, URL, and SEO title per store, ideal for FR / EN / NL storefronts.
- Merchandising touches — featured items, icons, coloured badges (NEW, SALE), per-item CSS classes, megamenu descriptions and hero images.
- Hover or click — choose how dropdowns open per menu; hover gracefully falls back to tap on touch devices.
Compatibility
- Magento 2.4.x / Mage-OS equivalent
- PHP 8.1, 8.2, 8.3
- Requires
wimakeit/module-core3.0 or later - Built for the Hyvä frontend (replaces Hyvä's default top menu)
Install this module via Composer. Make sure your auth.json is configured with your Wimakeit credentials.
$ composer require wimakeit/module-navigation:^2.0.2
$ bin/magento setup:upgrade
$ bin/magento setup:di:compileInstallation notes
The standard composer require + setup:upgrade + setup:di:compile flow applies. The points below cover what's specific to this module.
Required dependencies
wimakeit/module-core3.0 or later (pulled automatically from the Wimakeit registry).- A Hyvä frontend. The module declares a sequence after
Hyva_Themeand replaces Hyvä's default top menu block (topmenu_generic, slotas=topmenu). It is not intended for the Luma frontend.
There is no Stores → Configuration section for this module — everything is configured per menu and per item in the admin grids below.
ACL permission
After installation, one new ACL resource is available under System → Permissions → User Roles:
| Resource | Default |
|---|---|
Wimakeit_Navigation::menu (manage navigation menus and items) | granted to Administrator role only |
The admin screens live under Content → Wimakeit Navigation:
- Navigation Menus — create and edit menus.
- Menu Items (legacy) — flat item editor kept for backward compatibility.
Per-menu settings (defaults)
Each menu (Content → Wimakeit Navigation → Navigation Menus) ships with these defaults:
| Setting | Default |
|---|---|
| Layout type | Simple (Simple / Megamenu / Stacked) |
| Trigger | Hover (Hover / Click) |
| Megamenu columns | 4 (1–6, megamenu only) |
| Active | Yes |
| Extra CSS class | (empty) |
The frontend fetches a menu by its identifier. The default header menu uses identifier main_menu; point a template or layout argument at another identifier to render a second menu (e.g. footer_menu).
Per-item options
Each item carries: parent (for nesting), position, enabled flag, "open in new tab", CSS class, icon, badge + badge colour, featured flag, and megamenu column span. The item edit form ships preconfigured for three store views (FR = 1, EN = 2, NL = 3), each with its own Label, URL path, and SEO Title. Adjust these fieldsets if your store-view layout differs.
A node can draw its children dynamically from the catalog by setting its data source to category tree (with a JSON config {root_category_id, max_depth}, defaults 2 / 3) instead of static DB items.
Data patches (run automatically on setup:upgrade)
| Patch | Effect |
|---|---|
SeedDefaultMenu | Inserts the default main_menu (id 1) if absent, so existing items keep a parent menu. |
MigrateToTwoTableSchema | Migrates pre-2.0 single-table data to the two-table (item + per-store value) schema. |
> Note: MigrateToTwoTableSchema clears the navigation item tables before rebuilding them. On a store that already has items, back up wimakeit_navigation_item* tables before running setup:upgrade for the 2.0 release.
No cron jobs and no app/etc/env.php keys are required.
- Version
- v2.0.2
- Support
- 12 months
- Last updated
- Aug 25, 2026
- Magento
- Magento 2.4.4 Magento 2.4.5 Magento 2.4.6 Magento 2.4.7 Mage-OS 2.0 Mage-OS 2.1
- PHP
- PHP 8.1 PHP 8.2 PHP 8.3
- Hyvä
- Compatible
- Package
-
wimakeit/module-navigation
Compatibility checker
Pick your stack to see if this module fits.
Changelog
Categories: Security, Feature, Fix, Perf, Admin, Deps.
[2.0.1] - 2026-06-29
Fix
- Menu edit screen no longer throws
Call to a member function addFieldToFilter() on null— the menu form data provider now initialises its collection.
Admin
- The item editor now renders one store-view fieldset per actual store view (Label / URL / Title), instead of a fixed FR / EN / NL set — single-store and 4+ store-view installs are now handled correctly.
[2.0.0] - 2026-05-06
Feature
- Multi-menu builder — define multiple independent menus, each addressed by an identifier (
main_menu,footer_menu, …) so one module can drive header, footer, and sidebar navigations. - Three layouts per menu — Simple (dropdown panels), Megamenu (full-width column grid, 1–6 columns), and Stacked (vertical sidebar / footer), switchable from a dropdown without any XML edit.
- Unlimited nesting depth — items form a parent/child tree with per-item position, active toggle, and "open in new tab".
- Live category branches — an item can pull its children straight from the Magento category tree (configurable root category and max depth) instead of static links, so the menu tracks the catalog automatically.
- Per-store-view content — every item stores its own label, URL, and SEO title per store view, for multi-language storefronts (FR / EN / NL).
- Merchandising options — featured items, icons, coloured badges (NEW, SALE), per-item CSS classes, megamenu column span, plus descriptions and hero images.
- Hover or click trigger — choose per menu how dropdowns open; hover falls back to tap on touch devices.
- Mobile hamburger drawer — responsive off-canvas navigation for small screens.
Fix
- Menu edit screen no longer throws
Call to a member function addFieldToFilter() on null— the menu form data provider now initialises its collection like the item form. - Corrected admin listing iteration that could mis-render the menu grid.
Admin
- New Content → Wimakeit Navigation section with a Navigation Menus grid and a backward-compatible Menu Items editor.
- Two-table schema (item + per-store values); the
MigrateToTwoTableSchemadata patch upgrades pre-2.0 single-table installs andSeedDefaultMenuseeds the defaultmain_menu.
Deps
- Requires
wimakeit/module-core^3.0. - Built for the Hyvä frontend (sequenced after
Hyva_Theme; replaces the defaulttopmenu_genericblock).
Found a bug? Tell us about it.
A short form opens in a new tab — the module name and your language are already filled in. Share what you tried, what went wrong, and we will get back to you within one business day.
Report a bug for NavigationNeed help?
Our team is available to assist with integration.