Weave Code
Taxonomy Bundle Laravel Package
enhavo/taxonomy-bundle
Taxonomy bundle for the Enhavo CMS, providing flexible category and tag management on top of Symfony. A subtree split of the main Enhavo repository; see the main project for documentation and support.
[READ-ONLY] EnhavoTaxonomyBundle
Frequently asked questions about Taxonomy Bundle
- Is enhavo/taxonomy-bundle a Laravel package?
- No. It is a full-stack Symfony bundle for the Enhavo CMS that registers through Symfony's kernel, dependency injection container, and Doctrine ORM mappings. Laravel consumes a subset of Symfony components but does not run a Symfony kernel or bundle registration pipeline, so this package cannot be required into a Laravel app and expected to work.
- Can I install enhavo/taxonomy-bundle with Composer in a Laravel project?
- You can run the Composer require command, but the result will not be a working feature. The bundle expects Symfony bundle registration, service definitions, compiler passes, and Doctrine entity mappings that Laravel does not provide. Installing it also pulls in Enhavo core dependencies built for a CMS you are not running, which risks confusing conflicts. Treat Composer installability as unrelated to actual Laravel integration.
- Which Laravel versions does enhavo/taxonomy-bundle support?
- None, officially. There is no Laravel support matrix, no Laravel service provider, and no Laravel documentation in the repository. The package targets Symfony and inherits its version constraints from the Enhavo monorepo rather than from Laravel releases. If you need a Laravel-compatible taxonomy package, this is not one.
- What is enhavo/taxonomy-bundle actually used for?
- It provides flexible category and tag management for the Enhavo CMS, an open-source PHP CMS built on the full-stack Symfony framework. The package is a subtree split of the main Enhavo repository, published so the monorepo can expose it as a standalone Composer package. Its purpose is taxonomy data and admin management inside Enhavo, not general-purpose tagging in arbitrary PHP applications.
- Does enhavo/taxonomy-bundle work standalone without the Enhavo CMS?
- That is unlikely and unconfirmed. The bundle is split from a CMS monorepo and almost certainly depends on Enhavo core bundles, Doctrine entities, and admin UI hooks rather than standing alone. No documentation surfaces a standalone Symfony usage path, and there is no test suite or example app demonstrating one. Verify by inspecting its composer.json and service definitions before assuming bare-Symfony compatibility.
- Is enhavo/taxonomy-bundle actively maintained and production-ready?
- It is a read-only subtree split of the main Enhavo repository, so it has no independent issue tracker, release notes, or contribution path. The package has no dependents or stars, and its maturity rating is essentially README-level, meaning no surfaced tests or external validation. Changes arrive when the monorepo changes, and tags follow the parent project rather than a dedicated release cadence. That is a weak signal for production adoption outside Enhavo.
- Can I run enhavo/taxonomy-bundle with Doctrine alongside Eloquent in Laravel?
- Technically you could install Doctrine ORM next to Eloquent, but you would be maintaining two ORMs for one bounded feature, which is a poor trade. The bundle's value is its taxonomy logic and admin integration, not a standalone Doctrine schema you can reuse cheaply. If you only want the data model, translate it into Eloquent models and migrations instead. That keeps a single ORM and drops the unusable CMS coupling.
- What are the best alternatives to enhavo/taxonomy-bundle for Laravel?
- For most Laravel applications, spatie/laravel-tags covers tags and simple taxonomies using Eloquent, while nested-set packages handle hierarchical categories. A custom polymorphic many-to-many relation with a type or vocabulary column is often the cleanest fit when your taxonomy rules are specific. All of these keep you on Eloquent and avoid dragging a Symfony CMS dependency into your application.
- How do I evaluate enhavo/taxonomy-bundle before adopting it?
- Time-box a spike in a bare Symfony application rather than in your Laravel codebase, and read the main Enhavo repository because the split ships only a stub README. Inspect composer.json for pinned PHP, Symfony, and Doctrine constraints, and check whether EnhavoCoreBundle and the admin stack are hard requirements. If the spike needs the full CMS just to boot, the package is a design reference only. There is no surfaced test suite to lean on.
- Is enhavo/taxonomy-bundle MIT licensed, and can I fork it?
- Enhavo is MIT licensed open source, so forking and internal vendoring are permitted. However, the split is read-only and has no independent issue tracker, so your fork carries the maintenance burden with no community backstop. Confirm there are no trademark or branding restrictions if you reuse the admin UI assets.
Weaver
How can I help you explore Laravel packages today?