Magento 2 Mega Menu

Welcome to Magepow Magento 2 Mega Menu! Our free module helps you create a user-friendly navigation experience and improve the usability of your online store.

For merchants who need professional assistance and reliable ongoing support, we recommend purchasing the module from Magepow. Our support service helps you get the most out of the module, resolve technical issues, and ensure a smoother experience when integrating it into your Magento store.

Magento 2 Mega menu extension is an indispensable component, and plays the role of website navigation to help customers easily categorize and find information. Without a menu, visitors to the page will have to spend time searching for each content on your website, thereby making them find it difficult, difficult to access and do not know what your website has main content. This will increase the user's bounce rate, thereby reducing the SEO quality of the website.

[image: Magento 2 Mega menu extension]

Mega menu, dropdown menu and mobile menu for Magento 2 / Adobe Commerce.

The module replaces the default store.menu block with a configurable navigation that supports
mega menu layouts, plain dropdown menus, an extra (custom) menu and a sidebar accordion menu.

Get started

• Quick start install
• Requirements Magento Open Source / Adobe Commerce
• Magento 2 Mega Menu Pro

Installation

composer require magiccart/magicmenu
bin/magento setup:upgrade
bin/magento setup:static-content:deploy -f
bin/magento cache:flush

Manual installation: copy the module to app/code/Magiccart/Magicmenu and run the commands above
without the composer require line.

Need Professional Support?

Magepow Magento 2 Mega Menu is free and open-source, allowing you to build intuitive and user-friendly navigation for your Magento store.

If you need professional technical assistance, help with configuration, troubleshooting, or ongoing support, you can purchase the module with our support service directly from the Magepow website.

Get professional support and make the most of your Magento 2 Mega Menu.

• 👉 Purchase Mega Menu Pro with Support

Highlight features

1. Mega menu, dropdown menu or both

Mega menu

The mega menu saves horizontal space and gives every top category its own panel made of CMS
static blocks placed on the top, left, right and bottom of the category list.

[image: Mega menu]

Dropdown menu

A dropdown menu shows the sub categories on hover or on click. It fits catalogs with many
categories and keeps the navigation compact.

[image: Dropdown menu]

2. Extra menu

Magiccart > Magic Menu > Extra Menu adds standalone entries to the navigation. Each entry shows a
link, a CMS static block, or both.

[image: Extra menu]

3. Responsive and mobile menu

The menu adapts to the screen: the desktop navigation is replaced by a mobile menu below the
breakpoint defined in the configuration. The sticky option keeps the menu visible while scrolling.

4. Category label, image and thumbnail

Each category can show a label, a thumbnail and an image inside the mega menu. The values are set
in Catalog > Manage Categories and are stored as the magic_label, magic_thumbnail and
magic_image category attributes.

Configuration

Stores > Configuration > Magiccart > Magic Menu

Category configuration

Catalog > Categories > <category>

• Label – comma separated list of labels rendered next to the category name.
• Thumbnail / Image – uploaded to pub/media/magiccart/magicmenu/thumbnail/<id>.png and
  pub/media/magiccart/magicmenu/images/<id>.png.

Mega menu / extra menu configuration

Magiccart > Magic Menu > Menu binds a top category to a layout made of CMS static blocks
(top, left, right, bottom) with configurable proportions.

Magiccart > Magic Menu > Extra Menu adds a standalone entry to the navigation. It renders either
a link or a CMS static block.

The values stored in the top, left, right, bottom and ext_content fields are CMS block
identifiers, not block IDs.

Proportions of the mega menu

The width of the mega menu is shared between the category list, the left block and the right block.
The three proportion fields are weights: the total of the weights is used to calculate the width of
every part.

Example: Proportion: Category = 2, Proportion: Block Left = 1 and Proportion: Block Right = 0
give 67% of the width to the categories and 33% to the left block.

Extension points

Use the repository instead of loading or saving the model directly:

$menu = $this->magicmenuRepository->getById($id);
$menu->setName('New name');
$this->magicmenuRepository->save($menu);

Upgrade notes (2.0.0)

• The module moved from setup_version / InstallSchema / InstallData to declarative schema
  (etc/db_schema.xml) and a data patch (Setup/Patch/Data/AddCategoryMagicAttributes.php).
  The patch is idempotent: existing category attributes are not recreated.
• The CMS static blocks are now resolved by identifier (Magento\Cms\Block\BlockByIdentifier)
  instead of the deprecated Magento\Cms\Block\Block.
• Magiccart\Magicmenu\Helper\Data is deprecated, use Magiccart\Magicmenu\Model\Config instead.
• The Registry based transfer of the edited entity between controller and form block was removed.
• The exclude_html_desktop and exclude_html_mobile settings were removed, the attributes they
  rendered were never read by the JavaScript.

Development

vendor/bin/phpcs --standard=Magento2 --severity=10 app/code/Magiccart/Magicmenu
vendor/bin/phpcs --standard=Magento2 --extensions=php,phtml app/code/Magiccart/Magicmenu
vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/Magiccart/Magicmenu/Test/Unit

License

OSL-3.0 / AFL-3.0. See LICENSE.

Donation

If this project help you reduce time to develop, you can give me a cup of coffee :)

Our Magento 2 Extensions

• Magento 2 Recent Sales Notification

• Magento 2 Categories Extension

• Magento 2 Sticky Cart

• Magento 2 Ajax Contact

• Magento 2 Lazy Load

• Magento 2 Mutil Translate

• Magento 2 Instagram Integration

• Magento 2 Lookbook Pin Products

• Magento 2 Product Slider

• Magento 2 Product Banner

Our Magento 2 services

• PSD to Magento 2 Theme Conversion

• Magento 2 Speed Optimization Service

• Magento 2 Security Patch Installation

• Magento 2 Website Maintenance Service

• Magento 2 Professional Installation Service

• Magento 2 Upgrade Service

• Magento 2 Customization Service

• Hire Magento 2 Developer

Our Magento 2 Themes

• Expert Multipurpose Responsive Magento 2 Theme

• Gecko Premium Responsive Magento 2 Theme

• Milano Fashion Responsive Magento 2 Theme

• Electro 2 Responsive Magento 2 Theme

• Electro Responsive Magento 2 Theme

• Pizzaro Food responsive Magento 2 Theme

• Biolife organic responsive Magento 2 Theme

• Market responsive Magento 2 Theme

• Kuteshop responsive Magento 2 Theme

• Bencher - Responsive Magento 2 Theme

• Supermarket Responsive Magento 2 Theme

Our Shopify App

• Magepow Infinite Scroll

• Magepow Product Zoom

• Magepow Size Chart

Our Shopify Themes

• Uminex - Fastest Shopify 2.0 Theme
• Dukamarket - Multipurpose Shopify Theme

Our WordPress Theme

• KuteShop - Marketplace Elementor WooCommerce Theme

Changelog

All notable changes to the Magiccart_Magicmenu module are documented in this file.

The format is based on Keep a Changelog and this project
adheres to Semantic Versioning.

[2.0.0] - 2025-10-21

Added

• Service contracts: Api\MagicmenuRepositoryInterface, Api\Data\MagicmenuInterface and
  Api\Data\MagicmenuSearchResultsInterface with a Model\MagicmenuRepository implementation.
• Model\Config as a dedicated scope configuration reader.
• Declarative database schema (etc/db_schema.xml) with etc/db_schema_whitelist.json.
• Idempotent data patch Setup/Patch\Data\AddCategoryMagicAttributes for the category attributes.
• declare(strict_types=1) and the copyright header in every PHP and template file.
• ADMIN_RESOURCE constant and HttpGetActionInterface / HttpPostActionInterface on every admin
  controller.
• Unit tests for the repository, the configuration reader and the model.

Changed

• The Registry based transfer of the edited entity between the controller and the form block was
  replaced by the repository.
• CMS static blocks are resolved by identifier with Magento\Cms\Block\BlockByIdentifier; the
  deprecated Magento\Cms\Block\Block is no longer used.
• All frontend output is escaped with the Magento\Framework\Escaper.
• The frontend JavaScript no longer logs vendor branding and no longer depends on the missing
  easing RequireJS module.
• The file system access in the frontend block uses Magento\Framework\Filesystem\Driver\File
  instead of the native file_exists() function.
• The admin comment block that linked to an external product was replaced with a plain comment.

Removed

• The exclude_html_desktop and exclude_html_mobile settings of the Top Menu and Vertical
  Menu groups, together with their default values and the data-exclude_html_* attributes they
  rendered. Nothing in the JavaScript or the LESS ever read these attributes.
• Setup/InstallSchema.php and Setup/InstallData.php (legacy install scripts).
• Model/Category.php, an unused model.
• Block/Adminhtml/System/DynamicComment.php, an external link in the admin.
• etc/frontend/routes.xml, there is no frontend controller.
• The unused Block/Menu::getLogo() method.

Fixed

• The admin edit layouts (magicmenu_menu_edit.xml, magicmenu_extra_edit.xml) did not declare the
  form child block of the form container. The container calls getChildBlock('form') and threw
  Call to a member function setData() on bool, so the Add New / Edit pages were broken and the
  tab fields were rendered outside of the edit_form element. The unused
  Block\Adminhtml\{Menu,Extra}\Edit\Form blocks are now wired into the layouts.
• The Block grid renderer resolved CMS blocks by ID although identifiers are stored. Both the
  renderer and the frontend block now use the identifier.
• The admin delete action no longer tries to delete a record when no valid ID is provided.
• The accordion menu no longer passes an unsupported easing name to jQuery.
• The frontend JavaScript no longer depends on the easing RequireJS module, which does not exist
  in Magento and made the whole magicmenu module fail to load.