Weave Code
Tagging Bundle Laravel Package
kunstmaan/tagging-bundle
KunstmaanTaggingBundle adds reusable tagging to Symfony and Doctrine projects: attach tags to entities, manage tags in the admin, and query or filter content by tag. It integrates with Kunstmaan CMS bundles and provides a lightweight foundation for tag-based navigation and search.
Kunstmaan TaggingBundle adds flexible tagging to Symfony applications, letting you attach tags to any entity via a simple Taggable interface and Doctrine integration. Tags are stored as reusable entities, so they can be shared across records, queried, and rendered consistently.
- Taggable entity support through an interface and trait
- Doctrine-backed tag storage with entity relations
- Tag management and selection helpers
- Twig helpers for rendering tag lists
- Reusable tag repository for filtering by tag
Frequently asked questions about Tagging Bundle
- Is kunstmaan/tagging-bundle a Laravel package?
- No. It is a Symfony bundle that relies on Symfony bundle registration, Doctrine ORM, and the Kunstmaan CMS entity model, so it has no Eloquent, service provider, or Blade integration. For Laravel tagging, use spatie/laravel-tags or build a custom polymorphic tag model instead.
- How do I install kunstmaan/tagging-bundle with Composer?
- You would normally install it with composer require kunstmaan/tagging-bundle, register the bundle in a Symfony kernel, and configure Doctrine. However, its last release was in April 2014 and targets Symfony 2.x and PHP 5.3-5.4-era code, so modern Symfony and PHP 8 projects will likely fail dependency resolution or runtime checks. Treat it as a legacy Kunstmaan CMS artifact, not a modern install.
- Which Symfony and PHP versions does KunstmaanTaggingBundle support?
- The package targets Symfony 2.x and PHP 5.3-5.4-era idioms. It is not maintained for Symfony 5, 6, or 7, and PHP 8.x will reject or break on its service definitions, type hints, and deprecated Doctrine calls. Expect compatibility work if you try to use it outside a legacy Kunstmaan CMS instance.
- How does the bundle store tags on Doctrine entities?
- It wires FabienPennequin/DoctrineExtensions-Taggable into Kunstmaan entities. That Taggable behavior typically stores tags denormalized in a delimited string column, so tag queries are LIKE-based and individual tags are not indexed in a normalized table. This is acceptable for simple freeform folksonomy but weak for curated taxonomy, rename/merge workflows, and reporting.
- How can I query entities by tag with this bundle?
- The bundle exposes the underlying Doctrine Taggable helpers, which generally query the denormalized tag string column rather than joining a normalized tag table. That approach can work for simple filters but has performance and consistency limits as tag volume grows. For serious tag querying, use a first-party Tag entity with a polymorphic many-to-many join table.
- Is kunstmaan/tagging-bundle maintained and safe for production?
- No. It has had no security or compatibility releases in over a decade, and its FabienPennequin/DoctrineExtensions-Taggable dependency is also effectively unmaintained. With very low stars and no observable dependents, there is no production usage base to borrow confidence from. Avoid it for new production systems and treat it as reference material only.
- What is a maintained alternative to KunstmaanTaggingBundle in Symfony?
- For generic Symfony applications, stof/doctrine-extensions-bundle ships a Taggable implementation and is the more direct maintained substitute. For a durable taxonomy with rename, merge, and reporting needs, build a normalized Tag entity plus a polymorphic many-to-many join table. The Kunstmaan bundle adds little beyond CMS-specific entity hooks.
- What should I use for tagging in Laravel instead?
- Use spatie/laravel-tags or a custom polymorphic tag model with tags and taggables tables. KunstmaanTaggingBundle has no Eloquent analogue and should not be forced into a Laravel application. A first-party Laravel implementation is usually small and fully owned.
- Can I migrate from denormalized Taggable string tags to a normalized tag model?
- Yes, but treat it as a data migration project first. Parse the delimited tag column, normalize case and whitespace, create Tag and join-table records, and define how duplicates and merges should be handled. Plan that migration before writing replacement code, especially if an existing content corpus already depends on the old tag strings.
- Is KunstmaanTaggingBundle useful as a reference implementation?
- It can be useful as a reference for how taggable behavior is wired into Doctrine and Kunstmaan entities, but not as a runtime dependency. The bundle is mostly glue code, and a first-party normalized tag model with polymorphic many-to-many relations is likely under 200 lines and fully owned. That makes reference-only use the realistic leverage point.
Weaver
How can I help you explore Laravel packages today?