- Can I use presta/cms-core-bundle in a Laravel application?
- No. PrestaCMSCoreBundle is a Symfony2 bundle built on the Symfony full-stack framework and the Symfony CMF family, not a framework-agnostic Composer library. It registers services into a Symfony DI container, ships a DependencyInjection extension with a Configuration tree, declares routes via Symfony routing resources, and hooks into kernel events. Laravel has no analogue for any of that, so wiring it up would effectively mean running a Symfony kernel inside Laravel. That is a rewrite, not an integration.
- What does PrestaCMS Core Bundle actually do?
- It provides the foundational CMS layer for Symfony applications: page management, block-based content composition, dynamic routing that resolves CMS pages from the database, and extensible administration tools. It was designed as the core of the PrestaCMS platform and depends on symfony-cmf/routing, symfony-cmf/block-bundle, and symfony-cmf/core-bundle. Everything it offers is Symfony-coupled by design.
- Does PrestaCMS Core Bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony 2.3 through 2.8 and was last released on 2015-04-22, long before any modern Laravel version existed. Its Composer constraints pin Symfony 2.x components plus early Twig and Doctrine versions, which conflict with anything a current Laravel project pulls in. There is no bundle-discovery mechanism on the Laravel side either.
- Why does composer require presta/cms-core-bundle fail?
- Composer resolution fails almost immediately because the package constraints pin Symfony 2.x while your root project requires a modern PHP and Symfony or Laravel dependency set. The only way to install it is a frozen PHP 5.6 or 7.0 container with an isolated, legacy dependency tree. That container is itself an operational and security liability, so a failed install is the expected and correct outcome on any current stack.
- Which Symfony versions does PrestaCMS Core Bundle work with?
- It is built for Symfony 2.3 to 2.8, the era it was released in. It will not install on Symfony 4, 5, 6, or 7 because the underlying CMF bundles and service definitions do not exist in those versions. Even teams on a genuinely Symfony codebase cannot adopt it today without downgrading the entire framework.
- Is PrestaCMS Core Bundle still maintained?
- No. The repository is archived, the last release was 2015-04-22, and it has zero dependents on Packagist with roughly 26 stars. Archived status means no security patches, no PHP 8 compatibility work, and no dependency updates. Any adoption means owning a fork of the CMS and forks of the dead CMF bundles it depends on.
- Is it safe to run PrestaCMS Core Bundle in production today?
- No, especially on a public endpoint. You would be running unpatched 2015-era framework code on a PHP 5.x-era runtime, with a dependency tree that is itself end-of-life. Every future PHP upgrade, CVE, and dependency drift becomes your team's problem to fix in a fork you now maintain. The technical risk is high and terminal.
- What are good Laravel alternatives to PrestaCMS Core Bundle for CMS pages and blocks?
- For a Laravel codebase the practical options are Statamic for a first-party CMS experience, Filament paired with a page builder package for an admin-editable site, or a headless CMS such as Contentful, Sanity, or Payload consumed over HTTP. Which one fits depends on whether you need CMS-managed pages, block-based composition, or just an admin-editable site. Each of those requirements has a very different build-versus-buy answer.
- Is there a bridge package that lets me run Symfony bundles inside Laravel?
- There is no supported bridge, and PrestaCMS would be the hardest possible candidate for one. Laravel service providers are not bundles, and there is no bundle-discovery mechanism on the Laravel side. The CMF's dynamic routing is coupled to Symfony's RouterInterface and RequestContext, so a bridge would have to re-implement block rendering, page resolution, and the admin UI from scratch.
- How do I migrate an existing PrestaCMS site to a supported platform?
- There is no greenfield migration path into this package, only away from it. Inventory the existing installation including pages, blocks, media, and routes, then export content from the underlying Doctrine store and re-platform onto a supported CMS. Treat it as a data-migration project with its own budget rather than a dependency swap, and if a production PrestaCMS deployment exists, frame the work as a sustaining or exit engagement.