Weave Code
Menu Bundle Laravel Package
kunstmaan/menu-bundle
A menu bundle for Kunstmaan CMS that provides flexible, tree-based navigation menus you can configure and render in your templates. It lets developers define menu structures and integrate them into pages for consistent site navigation.
[READ-ONLY] Subtree split of the Kunstmaan MenuBundle -- master at Kunstmaan/KunstmaanBundlesCMS
Frequently asked questions about Menu Bundle
- Is kunstmaan/menu-bundle compatible with Laravel?
- No. kunstmaan/menu-bundle is a Symfony bundle split out of KunstmaanBundlesCMS, and it expects a Symfony kernel, Symfony's DI container, Doctrine ORM, knplabs/knp-menu-bundle and the sibling kunstmaan/admin-bundle and kunstmaan/node-bundle. Laravel's Illuminate foundation does not boot Symfony bundles, so there is no supported way to register it in a Laravel application.
- Can I install kunstmaan/menu-bundle with Composer in a Laravel project?
- Composer may resolve the package, but installing it does not make it usable. There is no Laravel service provider, no config bridge and no route integration, and the bundle's admin screens and menu entities depend on Kunstmaan CMS base classes. A wrapper would require a second container, Doctrine and the Kunstmaan admin asset pipeline, which is weeks-to-months of work with a high chance of failure.
- Does kunstmaan/menu-bundle support Laravel 10 or Laravel 11?
- No. The bundle family targets older Symfony and PHP lines and is effectively sunset, so its constraints conflict with modern PHP 8.2+ applications. There is no Laravel 10 or 11 support and no release path that would add it.
- What does kunstmaan/menu-bundle require to run?
- It needs a full Symfony application plus Doctrine ORM, Symfony routing and YAML config, knplabs/knp-menu-bundle, the Gedmo/DoctrineExtensions tree layer, and the Kunstmaan admin and node bundles for its entities, security roles, form types and translations. Those dependencies are not optional extras; the bundle cannot be consumed as a self-contained library.
- Is kunstmaan/menu-bundle still maintained?
- It is a read-only subtree split of the KunstmaanBundlesCMS monorepo with roughly 3 stars and zero dependents, and the wider bundle family has been effectively abandoned. With no downstream users there is no realistic path to regressions being caught or security issues getting a CVE response. Treat it as frozen legacy code, not a dependency to adopt.
- What is the best Laravel alternative to kunstmaan/menu-bundle for tree menus?
- Build it natively: a menus table, a menu_items table using an adjacency list with parent_id and position (or a nested set if you need subtree queries), and a menu_item_translations table for localized labels and URLs. Add reorder and nesting in Filament, Nova or your own admin, then render with a Blade component backed by a MenuResolver service and a cache keyed per menu and locale. That keeps the bundle's only real asset, its data model and UX ideas, at a fraction of the lifecycle cost.
- Can I use kunstmaan/menu-bundle with Filament or Laravel Nova?
- No. Its admin surface is Kunstmaan's own Symfony admin UI, built on a Bootstrap-3-era front-end, and it is not portable to Filament, Nova or any Laravel admin panel. There is no abstraction boundary you could reuse.
- How do I migrate an existing kunstmaan/menu-bundle setup to Laravel?
- There is no migration path from the bundle to Laravel because nothing in it is framework-agnostic. If you already run it inside a Symfony or Kunstmaan CMS application, freeze it: pin exact versions, add a composer.lock audit gate, and put your own menu-resolver interface in front of it so a replacement can be swapped in without touching templates. Do not add new features on top of it.
- Is it safe to fork kunstmaan/menu-bundle for a Laravel project?
- Forking is not a shortcut here. Making the bundle boot outside Kunstmaan CMS means standing up a Symfony container, Doctrine, the Gedmo tree layer and the admin asset pipeline, and even success leaves you owning the CMS's operational surface. A two-day timeboxed spike is the most anyone should commit before deciding no, and no fork should be approved without a named internal owner.
- Does kunstmaan/menu-bundle support multilingual menus and drag-and-drop ordering?
- Yes, in the context of Kunstmaan CMS: menus are administrable, localized through translation entities, linkable to page nodes, and ordered with a drag-and-drop admin UI. Those are also the only genuinely non-trivial parts of the feature and amount to roughly two tables plus an admin resource in Laravel. That is a feature to build, not a dependency to import.
Weaver
How can I help you explore Laravel packages today?