Weave Code
User Bundle Laravel Package
symfony2admingenerator/user-bundle
User bundle for the Symfony2 Admin Generator that adds ready-made user management to generated admin panels, including list, create, edit, and delete screens for application users. Helps integrate accounts and basic administration into Symfony2 projects with less boilerplate.
A Symfony bundle that brings ready-made user management to applications built with Symfony2Admingenerator. It supplies a user model and admin-generator configuration so you can manage accounts, credentials, and roles from a generated backend without building CRUD screens yourself.
- Ready-to-use User entity/model and admin module
- Generated list, create, edit, and delete screens
- Role and account management in the admin panel
- Designed to fit existing Symfony2Admingenerator projects
- Simple integration with Symfony’s security/user conventions
Frequently asked questions about User Bundle
- Is symfony2admingenerator/user-bundle a Laravel package?
- No. Despite being installable via Composer, it is a Symfony 2 bundle that wires FOSUserBundle entities into the Symfony2Admingenerator scaffolding system. There is no Laravel service provider, no Eloquent integration, and no Blade or Artisan surface of any kind. If you are evaluating this for a Laravel application, the evaluation ends here.
- Can I install symfony2admingenerator/user-bundle in a Laravel application?
- No. The package's 2015-era Composer constraints target Symfony 2.x and PHP 5.6/7.0 and will conflict with PHP 8.x and any modern Laravel release. Even if you forced the resolution, there is nothing for Laravel to boot or register. It is a Composer package only in the packaging sense, not a Laravel dependency.
- What does symfony2admingenerator/user-bundle actually do?
- It is a thin glue layer that exposes FOSUserBundle user entities inside Symfony2Admingenerator-generated CRUD screens. In practice it contributes generator YAML for user list and edit forms plus FOSUserBundle entity mapping. It owns no meaningful logic of its own, so its value is entirely derived from the frameworks beneath it.
- How do I install symfony2admingenerator/user-bundle?
- On a matching legacy stack you would require it with Composer, register the bundle in AppKernel, and configure the admin generator YAML for your user entity. That is a manual configuration exercise, not a simple package install. On any modern PHP or Symfony version, installation is not feasible at all.
- Which Symfony and PHP versions does symfony2admingenerator/user-bundle support?
- It requires Symfony 2.x and, in practice, PHP 5.6 or 7.0 to resolve its dependency tree. Symfony 2.x has been unsupported since 2019, and the package itself has been dormant for roughly a decade. There is no version of this bundle that runs on modern Symfony or on PHP 8.
- Is symfony2admingenerator/user-bundle still maintained?
- No. The repository has approximately 2 stars, zero dependents, and no recent activity, which means no maintainer will answer questions or fix defects. Every issue becomes an internal fork you own forever. Treat it as an archaeology artifact rather than a dependency.
- Is symfony2admingenerator/user-bundle safe to use in production?
- Not recommended. The code path it depends on is FOSUserBundle and Symfony 2 authentication, which handles credentials and sessions and no longer receives security patches. You also inherit permanent PHP runtime lock-in that blocks every other upgrade in your estate. The fact that an abandoned 2015 package is a low-value supply chain target does not make unpatched code safe.
- What are the alternatives to symfony2admingenerator/user-bundle in Laravel?
- For authentication, use laravel/fortify or Laravel Breeze. For the admin CRUD surface, use Filament, Nova, or Backpack. These cover the user management requirement with supported, maintained code on current PHP versions. The migration is far cheaper than forking a decade-old Symfony 2 bundle.
- What are the alternatives if I am on Symfony rather than Laravel?
- Move to Symfony's native security with make:user and make:auth, and use EasyAdmin or Sonata for the administration screens. FOSUserBundle itself was deprecated in favor of Symfony's native authenticator system. Migrate the user table and password hashes in place rather than upgrading the bundle.
- How do I migrate away from symfony2admingenerator/user-bundle?
- Do not attempt to upgrade the bundle; invert the problem instead. Inventory what it actually contributes, typically a few hundred lines of generator YAML and FOSUserBundle mapping, and extract any real customizations such as custom form types, role hierarchies, or password policy hooks into a documented spec. Then reimplement user administration on a supported stack and migrate the user table and hashes in place.
Weaver
How can I help you explore Laravel packages today?