Weave Code
Sonata Sylius User Bundle Laravel Package
libre-informatique/sonata-sylius-user-bundle
Integrates Sylius user management with Sonata Admin, giving you admin screens for customers and users inside a Sonata project. Provides the wiring needed to browse accounts and manage user data from the Sonata dashboard alongside your existing Sylius entities.
Symfony bundle providing a bridge between SonataAdmin and SyliusUser (an alternative to SonataUserBundle)
Frequently asked questions about Sonata Sylius User Bundle
- Is libre-informatique/sonata-sylius-user-bundle a Laravel package?
- No. It is a Symfony bundle that bridges SonataAdminBundle and the Sylius user model, so it has no place in a Laravel application and cannot be installed with a Laravel service provider workflow. If you arrived here looking for a Laravel user-management package, this is not it and should be struck from your roadmap. It belongs only in a Symfony project that already runs SonataAdmin and Sylius.
- What does SonataSyliusUserBundle actually do?
- It exposes the Sylius User entity as a CRUD-manageable resource inside SonataAdmin, giving you admin screens to browse accounts and edit user data from the Sonata dashboard. It is positioned as an alternative to SonataUserBundle, which bridges to FOSUserBundle instead of Sylius. The value is a thin integration layer, not a full admin suite.
- Which Symfony, PHP, SonataAdmin, and Sylius versions does this bundle support?
- There is no published compatibility matrix in the README, so the only reliable source is the composer.json on the repository's default branch. SonataAdmin and Sylius both churn on major versions, and a thin, low-activity bridge tends to lag behind those releases. Check the require constraints against your exact target versions before assuming it installs, and confirm whether any tagged release matches the branch you are reading.
- What license is this bundle released under?
- The package metadata reports NOASSERTION, which means the license could not be automatically determined and is effectively unresolved. There may be no LICENSE file at all, and that is a hard blocker for enterprise shipping or redistribution without legal review. Get written clarification from the maintainer or record a documented internal licensing decision before you depend on it.
- Is it a drop-in replacement for SonataUserBundle and FOSUserBundle?
- It replaces the SonataUserBundle approach by pointing Sonata's admin user class at the Sylius user entity instead of the FOS-based one, but that is not a like-for-like bundle swap. Moving from FOSUserBundle means migrating the user model itself, including users, roles, groups, and any FOS-specific fields, which is the real cost center of the change. Plan it as a data migration project with a rollback path, not a Composer update.
- How do I install and wire it into an existing Sonata Admin project?
- The general shape is to require the package with Composer, register the bundle in your kernel, and then configure Sonata's admin user class and your security user provider to use the Sylius user entity. The README is minimal, so the exact service and configuration keys must be read from the bundle's own config files rather than from documentation. Expect to spend most of the effort reconciling Sonata's expected UserInterface with the Sylius UserInterface contract.
- Should I use this with Sylius AdminBundle or instead of it?
- It is an alternative to Sylius AdminBundle, not a companion to it. Sylius AdminBundle is resource and grid based, while Sonata uses a block and CRUD model, so running both gives you two competing admin philosophies over the same user data. Adopting this bundle only makes sense when you have deliberately chosen SonataAdmin as your back office, for example to consolidate admin across several applications.
- How does it handle password hashing, user providers, roles, and impersonation?
- That behavior is not documented, so it must be proven in a spike on your exact Symfony, SonataAdmin, and Sylius versions. Verify password hashing on create and update, login through Sonata's security integration, role and group handling, and whether impersonation is supported at all. The admin panel plus the credential model is a privilege-escalation surface, so treat any gap here as a blocker rather than a nice-to-have.
- Is this bundle production-ready and actively maintained?
- Community signals are essentially absent: roughly one star, zero known dependents, a single maintainer, and no visible release cadence or CI. There are no known production users, so you would be the de facto first adopter with a bus factor of one. Treat it as a reference implementation or reading material, not a supported dependency, unless you are prepared to own an internal fork.
- What are the alternatives to SonataSyliusUserBundle?
- For greenfield Sylius projects the default is Sylius AdminBundle, which already manages users through its native resource and grid system. If you are committed to SonataAdmin, the alternatives are maintaining a small in-house admin class over the Sylius user entity or forking this bundle under your own maintenance. SonataUserBundle with FOSUserBundle remains an option only if you are not standardizing on the Sylius user model.
Weaver
How can I help you explore Laravel packages today?