- Is presta/cms-contact-bundle compatible with Laravel?
- No. Despite being listed alongside PHP packages, PrestaCMSContactBundle is a Symfony 2-era bundle built for PrestaCMS, a Symfony CMF-based CMS, and it has no relationship to Laravel's service container, Eloquent, Blade, middleware pipeline, or package discovery. You cannot install or autoload it in a Laravel application, and there is no adapter path. The only realistic way to use it in a Laravel project is as a reference for requirements, then rebuild the functionality natively.
- How do I install PrestaCMSContactBundle?
- Installation only makes sense inside an existing PrestaCMS application running Symfony 2.1 to 2.3 on PHP 5.x. You would add presta/cms-contact-bundle to composer.json and register the bundle in the legacy AppKernel. On modern PHP runtimes Composer resolution will fail on constraint conflicts long before any code executes. The repository is archived with a last release in February 2014, so there is no supported install path for new projects.
- Which Symfony and PHP versions does PrestaCMSContactBundle support?
- The bundle targets Symfony 2.1 through 2.3 and Twig 1.x, which corresponds to PHP 5.x-era runtimes. It was not designed for Symfony 4, 5, 6, or 7, and it does not run on PHP 8. Because the dependency tree is effectively frozen in 2014, satisfying its constraints pulls in pinned Symfony 2.x components and contemporaneous mailer libraries.
- Does PrestaCMSContactBundle save contact form submissions to the database?
- Yes. The bundle stores contacts and messages and exposes them for administration through Sonata, so editors can review inquiries inside the CMS admin rather than relying solely on email. The functional scope is deliberately small: capture the submission, persist it, and surface it in the admin UI. If you rebuild this in Laravel, the equivalent is an Eloquent model plus a Filament or Nova resource for administration.
- Can I customize how PrestaCMSContactBundle handles messages?
- Yes. The bundle is designed so you can implement your own strategy to fit your needs, for example custom persistence, routing, or notification behavior around the captured contact data. That extensibility is one of its few genuinely useful ideas. In a modern rebuild, the same flexibility comes from a Form Request for validation, a Mailable for notification, and an interface or action class for the storage and routing strategy.
- Does PrestaCMSContactBundle protect contact forms against spam and CSRF?
- The bundle predates most of the anti-abuse tooling developers expect today, and its 2014-era implementation does not give you a patching path for CSRF, input validation, mail header injection, spam abuse, or rate limiting. Contact forms are a security-relevant surface, and unmaintained form handling is exactly where you do not want to be. If you adopt the concept, add rate limiting, a honeypot or CAPTCHA, strict validation, structured logging of submission failures, and delivery observability in your rebuild.
- Is PrestaCMSContactBundle still maintained?
- No. The repository is archived, the last release was 2014-02-26, it has around two stars and zero dependents, and there are no active maintainers or issue backlog. There is no one to ask about security patches, and no fork with momentum to rely on. Treat it as a frozen historical artifact rather than a dependency.
- How do I migrate a PrestaCMS contact form to Laravel?
- Use a reference-then-rebuild approach: read the bundle's block template and controller to extract the functional spec, including the field set, validation rules, persistence behavior, notification recipient configuration, and editor-facing block options. Then reimplement natively in Laravel with a Form Request for validation, a Mailable plus queued notification, a Blade or Livewire component or Filament block for the editorial side, and a rate limiter with honeypot or CAPTCHA middleware. The scope is small enough that this is measured in hours, not sprints. Do not pin or vendor the original package.
- Can I install PrestaCMSContactBundle on Symfony 6 or PHP 8?
- No. The bundle targets Symfony 2.1 to 2.3 and Twig 1.x, so it is not compatible with Symfony 6 or 7 or with PHP 8. Even inside the Symfony ecosystem, adopting it would be a port or rewrite rather than an integration exercise. Modern Symfony projects should use a FormType, symfony/mailer, and a CMS block type instead.
- What should I use instead of PrestaCMSContactBundle in a new Laravel project?
- Build the contact flow with native Laravel tooling: a Form Request for validation, a Mailable with a queued notification for delivery, a Blade or Livewire component for the public form, and a Filament block or custom CMS block for editor placement. Add rate limiting and spam mitigation such as a honeypot or CAPTCHA, plus logging around submission and delivery failures. This gives you a maintained, patchable implementation that matches the bundle's concept without inheriting its 2014 dependency chain and security exposure.