- Is presta/cms-media-bundle compatible with Laravel?
- No. It is a Symfony bundle built for PrestaCMS on the Symfony 2.x stack, using Sonata Admin, Symfony CMF, and typically PHPCR-ODM. There is no service provider, facade, config publishing, or Eloquent and Blade integration, so there is no Laravel surface to wire into. Laravel teams should treat the source as a design reference only.
- What does presta/cms-media-bundle actually do?
- It adds media block types to PrestaCMS so editors can embed images and files into page and block compositions. It plugs into PrestaCMS block registration and the Sonata Admin layer rather than exposing a standalone media library API. Its value depends entirely on already running PrestaCMS.
- How do I install presta/cms-media-bundle?
- Historically you install it via Composer into a PrestaCMS application, register the bundle in the Symfony kernel, and configure the block types through the CMS admin. It is not installable into a Laravel application. Expect dependency conflicts against modern PHP, symfony, sonata-project, and Doctrine versions during resolution.
- What Symfony and PHP versions does presta/cms-media-bundle require?
- It targets Symfony 2.x-era components along with a compatible Sonata Admin generation and PrestaCMS core, typically on PHP 5.x. Those runtimes are long past end-of-life. Modern Symfony 6 and 7 releases and PHP 8.x are not supported.
- Is presta/cms-media-bundle still maintained?
- No. The last release was in February 2014 and the repository is archived. There is no upstream maintainer, minimal community around eight stars and zero dependents, and no CVE monitoring. The MIT license allows forking, but you would inherit full ownership.
- Is presta/cms-media-bundle safe to use in production?
- Adopting it means importing an unpatched, end-of-life Symfony 2.x and PHP 5.x dependency surface with no security backport path. With an archived repository and no dependents, there is no community canary or third-party patching. Treat it as high technical risk and avoid it for new deployments.
- What is a good Laravel alternative for CMS media blocks?
- In Laravel the same requirement maps to a media library with attachable media through polymorphic relations. Mature maintained options include spatie/laravel-medialibrary and similar packages, combined with a Blade component or block-renderer registry for output. Storage adapters over Laravel's filesystem cover local and S3 uploads.
- Can I install presta/cms-media-bundle with Composer in a new project?
- Only against a legacy Symfony 2.x dependency set, since modern resolution will almost certainly fail on symfony, sonata-project, and Doctrine constraints. Workarounds like ignore-platform-reqs or manual constraint overrides void supportability. It is not a package to add to a greenfield codebase.
- How would I migrate PrestaCMS media blocks to Laravel?
- Treat the bundle source as a design reference by reading its media-block data model and rendering contract, then reimplement the capability natively. Use a media table with a polymorphic pivot to content blocks, a Blade component keyed by block type, and Laravel filesystem adapters for storage. Migration is a rebuild, not a code port.
- How do I test media block uploads if I rebuild this in Laravel?
- Use Storage fake and UploadedFile fake to simulate uploads, then assert the media record and polymorphic pivot are created correctly. Add feature tests that render the block component and verify the expected output. The original bundle has no Laravel test harness, so any testing story is one you build yourself.