- Can I install rz/classification-bundle in a Laravel application?
- No. rz/classification-bundle is a Symfony 2 bundle that depends on Symfony bundle conventions, container compilation, Doctrine ORM and SonataClassificationBundle, and it has no Laravel service provider, facade or Illuminate dependency. Composer will typically fail to resolve its Symfony 2-era constraints against a modern Laravel app. Forcing installation with --ignore-platform-reqs would introduce an unmaintained code path.
- What is rz/classification-bundle used for?
- It adds a taxonomy layer for Symfony applications, letting you define categories, tags, collections and hierarchical terms and attach them to entities. It is built as an extension of SonataClassificationBundle inside the Sonata admin and ORM ecosystem. It is not a general-purpose Laravel package, and its value is mostly Sonata wiring and configuration rather than a unique algorithm.
- Is rz/classification-bundle compatible with Laravel 10 or Laravel 11?
- No. The package targets Symfony 2 and its transitive dependencies are long past end of life, so they conflict with the PHP and framework constraints of Laravel 10, Laravel 11 and any current Laravel release. There is no Laravel package discovery, config publish tag or service provider. Compatibility with a modern Laravel stack is effectively zero without a full port.
- Is rz/classification-bundle still maintained?
- No. The repository is archived, has 0 stars and 0 dependents, and receives no issue triage or security patches. SonataClassificationBundle itself has moved on, so this extension is pinned to an old API contract. Treat it as abandoned rather than production-ready.
- Does rz/classification-bundle work with Eloquent?
- No. It uses Doctrine ORM mappings and Symfony's entity managers, not Eloquent models or Laravel's database layer. There is no adapter or bridge that maps its Category, Tag, Collection or Context taxonomy to Eloquent. You would need to reimplement the domain model natively in Laravel.
- What are the alternatives to rz/classification-bundle for Laravel?
- For simple needs, a native Laravel implementation with Eloquent models, migrations and relationships for categories and tags is usually the best fit. For a maintained package, evaluate actively developed Laravel taxonomy or tagging packages on Packagist and check their Laravel version support, test coverage and release cadence. Avoid ports of Symfony 2 bundles unless you are prepared to own a fork.
- How do I add categories and tags to Laravel models without this bundle?
- Create Eloquent models and migrations for categories, tags and any hierarchy or context tables, then define polymorphic or many-to-many relationships on the models you want to classify. Add service classes or query scopes for attaching, detaching and querying classifications. This typically takes a few days and gives you full control over behavior, validation and performance.
- Can I run rz/classification-bundle alongside Laravel as a separate Symfony service?
- Only as a legacy bridge. You could stand up a Symfony 2 and Sonata instance and integrate over HTTP or a shared database, but that means maintaining an end-of-life framework and an archived bundle. For most teams the cost of that bridge exceeds a native Laravel taxonomy implementation. If data already lives in a Sonata instance, a one-time ETL is usually the better path.
- Is it safe to use rz/classification-bundle in production?
- No. The bundle is archived, has no dependents and receives no security updates, and its Symfony 2 dependency graph is end-of-life. Installing it with platform requirement overrides in a Laravel app would put an unmaintained and incompatible code path into production. Use it only as a read-only reference for the taxonomy domain model.
- How do I migrate classification data from SonataClassificationBundle to Laravel?
- First document the classification entities and relationships you actually use, such as categories, tags, collections, contexts and their associations. Export the existing records and write a one-time ETL into equivalent Laravel Eloquent models and tables. Then reimplement the query and attachment behavior natively, rather than trying to port the Symfony bundle itself.