Weave Code
User Bundle Laravel Package
runroom/user-bundle
A user management bundle for PHP applications that provides ready-made user entities, authentication, registration and login flows, password reset, profile editing, and admin integration, so you can add secure account handling without rebuilding the same foundation on every project.
SonataUserBundle fork to restore compatibility with PHP 5.6 and 7.0
Frequently asked questions about User Bundle
- Is runroom/user-bundle compatible with Laravel?
- No. It is a fork of SonataUserBundle, a Symfony bundle that wires FOSUserBundle into SonataAdminBundle, and it ships no Laravel service providers, facades, config publishing or Eloquent bindings. There is no Laravel analogue for the Sonata admin paradigm, so integrating it would mean standing up a Symfony kernel, Doctrine and Sonata admin inside a Laravel app. For Laravel projects, use first-party auth such as Breeze, Fortify or Jetstream instead.
- What PHP versions does runroom/user-bundle support?
- The fork exists specifically to hold the PHP floor at 5.6 and 7.0 after upstream SonataUserBundle dropped them. Both versions are end-of-life and receive no security patches, so any deployment inherits unfixed runtime CVEs. Expect Symfony 2.8/3.x era code and Doctrine ORM 2.x alongside it.
- Why does runroom/user-bundle exist?
- It is a compatibility fork of SonataUserBundle created to restore support for PHP 5.6 and 7.0 after the upstream package raised its minimum PHP version. Its only reason to exist is that version floor, not new features or bug fixes. That means it has no visible upstream merge path for future Sonata or FOSUserBundle updates.
- What dependencies does runroom/user-bundle require?
- It depends on Symfony's DI container and event dispatcher, Doctrine ORM, sonata-project/admin-bundle, sonata-project/core-bundle and friendsofsymfony/user-bundle. All of those must already be present and version-locked together for the bundle to resolve. Any dependency requiring PHP 7.1 or newer will conflict, and Composer will surface that as a resolution failure.
- Is runroom/user-bundle safe to use in production?
- Only as a deliberate, time-boxed stopgap in a legacy Symfony application already pinned to EOL PHP. The technical risk is high because PHP 5.6 and 7.0 get no security patches and the fork has no upstream merge path for advisories or fixes. The adopting team owns patching it outright, so you need a named owner and an SLA before shipping it.
- How do I install runroom/user-bundle?
- Install it with Composer using an exact version constraint so the full transitive graph stays locked, and commit composer.lock. It expects a Symfony application with FOSUserBundle and SonataAdminBundle already configured, since there is no Laravel-style auto-discovery or config publishing. Run composer why-not before any upgrade attempt to see the exact blocker chain.
- Does runroom/user-bundle work with Symfony 4 or 5?
- No. It targets the Symfony 2.8/3.x era and PHP 5.6/7.0, so Symfony 4 and 5 will conflict on PHP and on the Sonata and FOSUserBundle versions. Upgrading Symfony is the first step of the exit path, not something the fork supports. After the runtime upgrade you would swap back to upstream sonata-project/user-bundle.
- What is the best alternative to runroom/user-bundle for Laravel?
- Laravel's first-party auth packages, Breeze, Fortify and Jetstream, cover registration, login, password reset and profile editing without any Symfony dependency. They are maintained, documented and tested against current Laravel and PHP versions. A maintained community package is also fine if you need specific features, but avoid porting Sonata's admin paradigm.
- How do I migrate off runroom/user-bundle?
- Treat it as technical debt with a dated exit: pin the fork with an exact Composer constraint and record the rationale in an ADR. The realistic path is two steps, first upgrade PHP and Symfony off EOL versions, then swap the fork back to upstream sonata-project/user-bundle at a version supporting the new runtime. A parallel path is replacing Sonata admin with a lighter admin surface and moving to Symfony's native security.
- Does runroom/user-bundle provide registration, login and password reset?
- Yes, it provides ready-made user entities and the standard FOSUserBundle flows: registration, authentication, password reset and profile editing, plus Sonata admin CRUD over users and groups. That feature set is real, but it is delivered through Symfony's DI container, event dispatcher and Doctrine, not Laravel's auth guards. In a Laravel app you would rebuild the same features with Breeze or Fortify in far less time.
Weaver
How can I help you explore Laravel packages today?