Weave Code
Fork Sonata Project Sonata User Bundle Laravel Package
paysera/fork-sonata-project-sonata-user-bundle
A Paysera-maintained fork of the Sonata User Bundle, adding user and group management to Symfony applications with SonataAdminBundle integration. It provides admin screens, forms, and FOSUserBundle compatibility for handling accounts, roles, and profiles.
Integrates the UserBundle into the Sonata Project
Frequently asked questions about Fork Sonata Project Sonata User Bundle
- What does paysera/fork-sonata-project-sonata-user-bundle do?
- It is a Paysera-maintained fork of the Sonata User Bundle for Symfony. It integrates user and group management into SonataAdminBundle, providing admin screens, forms, and FOSUserBundle compatibility for accounts, roles, and profiles.
- Can I use this package in a Laravel application?
- No. This is a Symfony bundle built on Symfony's dependency injection, SonataAdminBundle, and FOSUserBundle, so it will not work with Laravel's service container or Eloquent. For Laravel user and role management, look at packages such as spatie/laravel-permission combined with Breeze, Jetstream, or Filament.
- How do I install it with Composer?
- Run composer require paysera/fork-sonata-project-sonata-user-bundle and then register the bundle in your Symfony bundle configuration, such as config/bundles.php. Because it is a fork of sonata-project/sonata-user-bundle, you will usually need to replace or alias the upstream package and follow the README dependency notes. Check the fork's composer.json for required SonataAdminBundle and FOSUserBundle versions before installing.
- Which Symfony versions are supported?
- Support depends on the branch and the version constraints in the fork's composer.json, not on the upstream Sonata documentation alone. Review those constraints and the repository's commit history before upgrading a Symfony application. If you are on an older Symfony release, confirm the fork still receives compatible fixes.
- Does it require FOSUserBundle?
- It provides FOSUserBundle compatibility, so it is designed to work with an application that uses FOSUserBundle for authentication and user storage. You should expect to configure FOSUserBundle alongside SonataAdminBundle for the admin screens to work correctly. If your app uses a different user provider, verify the integration points in the README first.
- Why would I use this fork instead of the official Sonata User Bundle?
- Paysera maintains the fork to keep the bundle working with its own Symfony stack and to ship fixes that may not be available in the upstream release you depend on. The trade-off is that maintenance, compatibility guarantees, and release cadence follow Paysera rather than the Sonata Project. Compare both repositories' recent activity and version constraints before choosing.
- How is it configured in a Symfony app?
- Configuration typically involves enabling the bundle, setting up sonata_user and fos_user options, and adding user and group admin services to your SonataAdmin dashboard. Exact keys depend on the bundle version, so copy the configuration reference from the repository README. Then clear the cache and verify routes, firewall rules, and admin access.
- Is it safe to use in production?
- It manages user accounts, roles, and group membership, so treat it as security-sensitive code. Restrict the generated admin routes to trusted roles, review the default access control rules, and test privilege escalation paths before deployment. Also confirm that the fork is actively maintained for the Symfony version you run.
- What are the alternatives?
- The upstream sonata-project/sonata-user-bundle is the direct alternative if you do not need Paysera's changes. For Symfony applications you can also build user administration on Symfony Security with EasyAdmin or custom controllers. Laravel teams should instead evaluate Laravel-native tools such as Breeze, Jetstream, Filament, and spatie/laravel-permission.
- How should I test an application that uses this bundle?
- Write functional tests for login, user creation, group assignment, and admin access control using Symfony's KernelTestCase or WebTestCase with a test database. Mock or override third-party services where possible and seed roles and groups with fixtures. Include a test that confirms non-admin users cannot reach the Sonata admin routes.
Weaver
How can I help you explore Laravel packages today?