- Can I install presta/cms-user-bundle in a Laravel application?
- No. presta/cms-user-bundle is a Symfony 2 bundle built on Symfony's DI container, Doctrine ORM, and FOSUserBundle, and it has no service provider, Eloquent model, or Laravel middleware. Composer resolution will fail against modern Laravel and PHP constraints before any code runs. Do not add it to a Laravel project, even in a dev branch.
- What Laravel versions does presta/cms-user-bundle support?
- None. It is not a Laravel package and predates Laravel 5, targeting the Symfony 2.x era with PHP 5.3 and 5.4 assumptions. There is no compatibility branch for Laravel 10, 11, or 12, and no upgrade path exists. Use Laravel's native auth scaffolding instead.
- Is presta/cms-user-bundle still maintained?
- No. The repository is archived, the last release was 2014-02-26, and it has zero stars or dependents with no active maintainer. There is no release cadence and no one to accept patches or security fixes. Any adoption means you own the code permanently.
- What is presta/cms-user-bundle actually used for?
- It was a PrestaCMS add-on for managing front-end site users in Symfony 2 applications, layering registration, profiles, and login on top of FOSUserBundle and Symfony security. It handles site-visitor accounts, not admin panel users. It is not a general-purpose authentication library and is not usable outside its original Symfony 2 stack.
- How do I configure presta/cms-user-bundle in Laravel?
- You cannot. Configuration in Laravel happens through config files and service providers, while this bundle uses a Symfony DI extension, Doctrine mappings, and Twig templates. There is no Laravel config file, facade, or middleware to register. Porting it would be a rewrite, not a configuration task.
- What are the alternatives to presta/cms-user-bundle for Laravel?
- Use Laravel's first-party auth packages: Breeze for a simple scaffold, Fortify for headless backend auth, or Jetstream for a fuller starter kit with teams and two-factor support. All three cover registration, login, email verification, password reset, and profile management natively. They are maintained, tested, and built for current Laravel and PHP versions.
- Is presta/cms-user-bundle safe to use in production?
- No. It is archived, unmaintained authentication code from 2014 that predates modern password hashing defaults, secure session guidance, and current CSRF and rate-limiting expectations. Adopting it means inheriting undisclosed vulnerabilities with no upstream remediation path. Authentication is the highest-consequence surface in any application, so this risk is not acceptable for production.
- Can I use presta/cms-user-bundle as a reference for designing front-end user accounts?
- Yes, as a read-only design reference only. Its entity and controller structure can inform schema and workflow decisions, such as separating admin users from front-end users. Timebox a one- to two-day review, document the domain model, then implement natively on Laravel. Do not copy code into your application.
- How do I test presta/cms-user-bundle?
- You cannot meaningfully test it in a Laravel context because it will not install or boot. There is no Laravel test harness, no PHPUnit setup for modern PHP, and no CI for current versions. If you need tested auth, use Laravel Breeze, Fortify, or Jetstream, which ship with test coverage.
- Why does composer require presta/cms-user-bundle fail?
- Composer fails on php and symfony/* version constraints because the bundle targets PHP 5.3 and 5.4 with Symfony 2.x. Those constraints conflict with any modern Laravel or Symfony application's lockfile. There is no compatible release to resolve against, so the failure happens before any package code is evaluated.