Weave Code
Fork Sonata Project Classification Bundle Laravel Package
paysera/fork-sonata-project-classification-bundle
A Paysera-maintained fork of the Sonata ClassificationBundle for Symfony, providing taxonomy and classification management for categories, tags, collections, and contexts, with Sonata Admin integration for organizing and reusing content classifications.
Symfony SonataClassificationBundle
Frequently asked questions about Fork Sonata Project Classification Bundle
- What is paysera/fork-sonata-project-classification-bundle?
- It is a Paysera-maintained fork of the Symfony SonataClassificationBundle, which provides taxonomy primitives such as Context, Category, Tag, and Collection as Doctrine ORM entities. It includes optional Sonata Admin integration for managing and reusing content classifications. It is a Symfony bundle, not a Laravel package.
- Is this package compatible with Laravel?
- No. The package relies on Symfony bundle and kernel registration, the Symfony DI container, Doctrine ORM mappings, and typically SonataAdminBundle and SonataCoreBundle. It has no Laravel service providers, Eloquent bindings, config publishing, or facades. In a Laravel application, you would need to reimplement the taxonomy model with Eloquent or use a Laravel-native package instead.
- How do I install paysera/fork-sonata-project-classification-bundle?
- It is intended for Symfony applications that already use Doctrine ORM and Sonata Admin. You would require a pinned commit through Composer, register the bundle in your Symfony kernel, and configure entity mappings and Sonata admin services. Because the repository is archived, avoid floating version constraints and pin an exact commit hash.
- Which Laravel versions does this package support?
- None. This is a Symfony bundle and does not target Laravel at any version. There are no Laravel service providers, configuration files, or Eloquent models. If you need categories, tags, and collections in Laravel, evaluate spatie/laravel-tags or a nested-set package instead.
- Which Symfony and Sonata versions are supported?
- The supported Symfony, SonataAdmin, and Doctrine version ranges are defined in the fork's composer.json and are not documented in the overview. Sonata bundles are typically tightly coupled to specific SonataAdmin and Symfony minor versions, so you must inspect the constraints before adopting it. Expect PHP, Doctrine DBAL/ORM, and transitive sonata-project dependencies to be binding constraints.
- Do I need SonataAdminBundle to use this bundle?
- Sonata Admin integration is optional in the upstream bundle, but this fork is primarily useful inside a Sonata-based Symfony application. Without SonataAdmin, you would manage the Doctrine entities and taxonomy logic yourself. Adding SonataClassification solely for taxonomy is disproportionate if your application does not already run Sonata.
- Is this package actively maintained?
- No. The repository is archived, which means no security patches, no Symfony major-version tracking, and no upstream parity. It also has zero stars and zero dependents, so there is little community validation or incidental bug-finding. Treat it as a pinned internal dependency at best, not a generally consumable library.
- What are the production risks of using this archived fork?
- An archived fork will not receive security fixes or compatibility updates for new Symfony, Sonata, or Doctrine releases. Its divergence from upstream SonataClassificationBundle is undocumented from the outside, so the patch surface is unknown until you diff it. Doctrine entity mappings also create schema-level commitments that are expensive to reverse through migrations.
- What are good alternatives for taxonomy management in Laravel?
- For Laravel, implement categories, tags, collections, and contexts with Eloquent models or use packages such as spatie/laravel-tags for tagging and a nested-set package for hierarchical categories. Treat SonataClassificationBundle only as a reference model for the four-entity taxonomy. There is no viable direct integration path for this Symfony bundle in Laravel.
- How do I migrate off SonataClassificationBundle if I already use it?
- Export the taxonomy tables and map Context to a tenant or scope concept and Category to a hierarchical taxonomy in the target model. Preserve the closure or nested-set structure to avoid path recomputation churn during migration. Because the bundle is archived, plan the migration deliberately rather than sequencing it as a first-week integration.
Weaver
How can I help you explore Laravel packages today?