Weave Code
Media Bundle Laravel Package
enhavo/media-bundle
Enhavo MediaBundle is a subtree split of the open source Enhavo CMS, a flexible PHP project built on the Symfony fullstack framework for managing complex data structures through a clean, usable interface. See the main repository for details.
[READ-ONLY] EnhavoMediaBundle
Frequently asked questions about Media Bundle
- Is enhavo/media-bundle a Laravel package?
- No. It is a Symfony bundle and a read-only subtree split of the Enhavo CMS monorepo. Its service definitions, configuration tree and entity model assume the Symfony full-stack runtime, including HttpKernel, DependencyInjection, Doctrine ORM, Form and Routing. There is no Laravel service provider, no publishable config and no Eloquent mapping.
- Can I install enhavo/media-bundle in a Laravel application with Composer?
- Composer will resolve the split package, but the application will fail before the first request. The bundle depends on sibling Enhavo bundles such as EnhavoCoreBundle and its resource and Grid abstractions, which are not published as standalone units. Dropping it into Laravel means running two container paradigms side by side with no bridge. The realistic options are adopting Enhavo CMS wholesale on Symfony or reimplementing the media domain in Laravel.
- Does enhavo/media-bundle support Laravel 10 or Laravel 11?
- There is no Laravel version support at all, because the package is not versioned against Laravel. Its constraints track Symfony and Doctrine major versions tied to a branch alias in the Enhavo monorepo. Check the composer.json at the exact tag you would pin, and expect an upstream force-push or re-split to break your lockfile. Laravel version compatibility is simply not a meaningful question for this package.
- What Laravel package should I use instead of enhavo/media-bundle?
- The idiomatic Laravel answer is a Flysystem-backed media library such as spatie/laravel-medialibrary, with intervention/image for conversions and Laravel queues for derivative generation. That stack is container-native, ships publishable migrations and config, and carries far more dependents and maintenance signal. Treat Enhavo as an evaluated-and-rejected alternative unless a full CMS requirement is genuinely in scope.
- Why does the bundle fail after Composer install in a Laravel project?
- The bundle's service definitions reference parent bundle services that do not exist in a Laravel container, so dependency injection fails on boot. There is also no service-provider bridge, no configuration publishing and no Laravel-visible migrations. Template helpers are written for Twig rather than Blade. None of these gaps are bridgeable without a maintained adapter, which does not exist.
- Is enhavo/media-bundle actively maintained?
- It is a read-only split with around 2 stars, zero dependents and no bundle-level issue tracker. The only documentation is a logo and a pointer to the main repository, so there is no independent test signal or versioned support policy beyond monorepo tags. That means effectively a single-vendor bus factor, and you would own any patching if upstream stalls.
- Which Symfony and Doctrine versions does enhavo/media-bundle require?
- The requirements are inherited from the Enhavo monorepo branch the split was built from, not declared as an independent support policy. Expect Symfony full-stack components, Doctrine ORM entity mapping and a fixed PHP constraint for that branch. Because Doctrine entities are incompatible with Eloquent, the mapping layer cannot be reused in a Laravel application. Verify the exact constraints at your pinned tag before planning anything.
- Can I reuse Enhavo's media data model with Laravel Eloquent?
- Not directly, but the design is worth porting. The useful concepts are the separation of a media record from a file record, named conversion sets, a folder or taxonomy model and a storage adapter boundary. Reimplement those as Laravel migrations and models, for example media, media_conversions and media_folders tables. Port the schema shape, not the bundle code.
- Is enhavo/media-bundle safe to use for user file uploads in production?
- Media handling is a security-sensitive surface covering upload validation, MIME sniffing, path traversal, SVG and script payloads, and storage ACLs. A CMS-oriented uploader with unknown validation depth and no independent test signal is a poor place to accept inherited risk. That concern applies on Symfony too, but on Laravel the integration risk stacks on top of it. Prefer a library with an active security and disclosure process.
- How should I evaluate enhavo/media-bundle before committing to it?
- Cap the evaluation at a two to three day Symfony sandbox spike with no application integration. Stand up Enhavo, upload assets, inspect the media tables and trace the rendition pipeline. Confirm first whether the business requirement is media management in Laravel or full CMS authoring, because only the latter justifies adopting Enhavo as the application. If the concepts hold value, design Laravel-native schema and move on.
Weaver
How can I help you explore Laravel packages today?