Weave Code
Media Bundle Laravel Package
kunstmaan/media-bundle
KunstmaanMediaBundle adds media management to Symfony CMS applications, letting editors upload, organize, and store images and files through an admin interface. It includes thumbnail generation, media folders, and integration with the Kunstmaan admin bundle for managing assets across your site.
KunstmaanMediaBundle adds a complete media management layer to Symfony applications, letting editors upload, organize, and reuse images and files through a tree-based folder structure. It is part of the Kunstmaan Bundles ecosystem and integrates cleanly with the CMS and admin UI.
The bundle supplies form types for selecting existing media, server-side thumbnail generation and cropping (via LiipImagineBundle), and a backend interface for browsing and managing uploaded assets.
- Tree-based folders with drag-and-drop organization
- Image thumbnails and cropping via LiipImagineBundle
- Reusable media form types for your own entities
- Unified upload and management of images and files
- Seamless integration with Kunstmaan Bundles and Symfony
Frequently asked questions about Media Bundle
- Is kunstmaan/media-bundle compatible with Laravel?
- No. It is a Symfony bundle, not a Laravel package: it registers through AppKernel, ships a DI container extension and Configuration tree, and uses Doctrine annotation entities, Symfony Form types and Twig templates that extend Kunstmaan AdminBundle layouts. There is no service provider, facade, publishable config or migrations, and none of those touchpoints have shimmable Laravel equivalents — a bridge would mean running a Symfony and a Laravel kernel in one process.
- Can I install kunstmaan/media-bundle with Composer in a Laravel app?
- You can run composer require, but the package will not boot or be usable inside a Laravel application. Requiring it also pulls the wider KunstmaanBundlesCMS graph (NodeBundle, AdminBundle, Symfony 2 components, Doctrine), which conflicts with Laravel's HTTP kernel and container. Treat it as reference source, not a dependency.
- Which Laravel and PHP versions does kunstmaan/media-bundle support?
- It has no Laravel version support at all. The last release, 2014-09-19, targets PHP 5.x and Symfony 2.3–2.8, both long past end of life. On PHP 8 you will hit fatal errors from Doctrine annotation reader changes, removed functions such as each() and mcrypt, and deprecated syntax.
- Is kunstmaan/media-bundle still maintained and safe for production?
- It is effectively abandoned: last release September 2014, 38 GitHub stars, zero dependents, and no security patching or maintainer activity. Its headline in-browser editing feature depended on Aviary, retired by Adobe in 2018, so that UI is non-functional with no abstraction to swap it. Do not expect fixes or patches if you run it in production.
- What license is kunstmaan/media-bundle released under?
- GitHub reports the license as NOASSERTION, meaning it could not identify a license file or headers. It is likely MIT given the Kunstmaan family, but likely is not legal approval. Have counsel read the actual LICENSE and file headers before shipping any code derived from it.
- What are the best Laravel alternatives for media uploads and a media library?
- For uploads and thumbnails, use spatie/laravel-medialibrary with Intervention Image v3, Storage disks (local or S3) and queued conversions — mature and maintained. For full digital asset management (folders, metadata, search, renditions) use a hosted DAM such as Cloudinary, Filestack or imgix. Both cover the use case without a frozen Symfony dependency.
- Can I reuse any part of kunstmaan/media-bundle in a Laravel rebuild?
- Yes — the domain model is the reusable part. Port the Media entity fields (name, UUID, location, MIME type, size, dimensions, metadata), the MediaFolder tree, a handler registry keyed on media type, and named thumbnail set definitions to Eloquent models, Storage::disk() paths, a MediaHandler interface and config/media.php. That is roughly a one-to-two week spike, not an integration.
- Does kunstmaan/media-bundle still support in-browser image editing?
- No, not in any usable form. In-browser editing was delegated to Aviary, acquired by Adobe in 2014 and retired with the Creative SDK in 2018, and the bundle offers no way to plug in a replacement. Budget for Pintura or a hosted service such as Cloudinary or Filestack if editing is a hard requirement.
- What dependencies does kunstmaan/media-bundle pull in?
- It drags in the KunstmaanBundlesCMS stack — Kunstmaan/Bundles, NodeBundle, AdminBundle — plus Symfony 2 components, Doctrine ORM with annotation mapping, and Twig. That is a large, equally frozen dependency graph with no Laravel-compatible pieces. The transitive weight alone rules it out for a modern Laravel app.
- Should we adopt kunstmaan/media-bundle or rebuild it in Laravel?
- If the target is actually an existing Kunstmaan/Symfony CMS, keep the bundle and isolate it. If the target is Laravel — which the package listing implies — reimplement the media model; a scoped rebuild takes about one to two weeks and wins on total cost of ownership versus adopting dead code. Confirm who owns maintenance for the next three years before deciding.
Weaver
How can I help you explore Laravel packages today?