Weave Code
Node Bundle Laravel Package
kunstmaan/node-bundle
KunstmaanNodeBundle provides a hierarchical, translatable node tree for Symfony applications, forming the foundation of the Kunstmaan CMS. It includes Node and NodeTranslation entities, slug-based routing, and tools for managing nested content pages.
KunstmaanNodeBundle adds a hierarchical node tree to Symfony applications, forming the content backbone of the Kunstmaan CMS. Editors can organize pages and sections as nodes, while developers define custom node types and control how each node is rendered. The bundle handles node persistence, URL/slug generation, and admin integration, making it suitable for structured site trees.
- Tree-based content management for pages and sections
- Custom node types backed by Doctrine entities
- Automatic slug and routing support
- Admin UI integration for creating, moving, and publishing nodes
- Extensible templates and services for front-end rendering
Frequently asked questions about Node Bundle
- Is kunstmaan/node-bundle a Laravel package?
- No. Despite being installable through Composer, kunstmaan/node-bundle is a Symfony bundle (package type symfony-bundle) that relies on Symfony DependencyInjection extensions and compiler passes, Doctrine ORM mappings and Twig templates. None of that surface is consumable by Laravel's container, Eloquent, Blade or router, and there is no adapter layer. Treat it as PHP code that targets Symfony 2.x, not Laravel.
- Can I install kunstmaan/node-bundle in a Laravel 10 or 11 application?
- Not realistically. Composer will try to resolve Symfony 2-era constraints such as symfony/symfony ~2.3, Doctrine 2.4-era packages and PHP 5.x, which produces an unresolvable dependency graph in any PHP 8 / Laravel 10+ project. Forcing it with --ignore-platform-reqs leads to fatal errors on removed language features. There is no partial-integration path; making it run would cost roughly the same as building a page-tree CMS from scratch.
- What PHP and Symfony versions does kunstmaan/node-bundle require?
- The bundle targets the Symfony 2.x era, with constraints around symfony/symfony ~2.3 and Doctrine 2.4, and it assumes PHP 5.x. Symfony 2.8 reached end of life in November 2018, so the runtime it was built for is long unsupported. There has been no PHP 8 compatibility work.
- Is kunstmaan/node-bundle still maintained?
- No. The last tagged release in this subtree split is dated 2014-08-05, with no security backports and no CVE response since. One caveat: the repository is a read-only subtree split of the KunstmaanBundlesCMS monorepo, so stars and release dates here understate activity in the parent project. Even so, the parent's split packages remain Symfony-only and legacy-bound, so verify on Packagist and the monorepo before quoting the numbers.
- What does kunstmaan/node-bundle actually do?
- It provides the node and page-tree foundation for the Kunstmaan CMS: a Node entity with per-locale NodeTranslation records (slug, title, online flag, hiddenFromNav, sequence), Page and PagePart composition, draft and published versioning, and per-node ACL. It also ships admin tooling built on Sonata Admin, FOSUserBundle and Symfony ACL, plus a SlugRouter route loader. The domain model is a well-shaped page-tree abstraction; the runtime is Symfony-specific.
- Can I reuse the NodeBundle data model or schema in a Laravel app?
- Yes, as a specification rather than as code. You can recreate nodes, node_translations, node_versions and page_parts tables modelled on the bundle's schema, then map them to Eloquent models. Use kalnoy/nestedset or a closure table for the tree while preserving the parent and sequence semantics. That is a concept port, not a code port, and it is the recommended path for Laravel targets.
- How do I replace the Symfony SlugRouter for multilingual page routing in Laravel?
- Replace it with a single catch-all Laravel route that resolves the localized slug from your node_translations table, scoped by locale. Keep the slug unique per locale rather than globally, and store the online flag and hiddenFromNav as queryable columns so navigation menus can filter at the database level. Draft and published versions map cleanly onto a versions table plus a published pointer.
- What are the Laravel alternatives to kunstmaan/node-bundle for a page tree?
- For the tree itself, kalnoy/nestedset or a closure table gives you parent and sequence semantics without the CMS baggage. For marketer-editable pages, Filament with a page resource and block or page-part relations is the usual Laravel-native build, and headless options such as Statamic or a licensed CMS cover the content-API case. The right answer depends on whether you need an editable page tree or a headless content API.
- Is kunstmaan/node-bundle safe to use in production?
- No. It has had no releases, security backports or CVE response since 2014, and its transitive stack of Sonata Admin, FOSUserBundle, Symfony ACL and Doctrine is equally dead. Adoption signal is minimal, with roughly 23 stars and zero dependents, so there is little third-party bug-finding. Reusing even 20 percent of the bundle drags in 100 percent of an unsupported stack.
- What dependencies and licence does kunstmaan/node-bundle ship with?
- It assumes Sonata Admin, FOSUserBundle, Symfony ACL and Doctrine ORM, along with Twig and Symfony's DI and routing components. The licence is MIT, which cleanly permits forking and commercial reuse. That makes it a fork-and-own decision rather than a dependency decision, and any fork needs a named owner with Symfony experience or it is dead on arrival.
Weaver
How can I help you explore Laravel packages today?