- Does picoss/sonata-extra-admin-bundle work with Laravel?
- No. This is a Symfony bundle built on SonataAdminBundle and Symfony's bundle registration and DI container; it has no Laravel service provider, package auto-discovery, or Artisan surface. For a Laravel back office, evaluate Filament, Laravel Nova, or a first-party Livewire or Inertia admin instead.
- What PHP, Symfony, and Sonata Admin versions does this bundle support?
- The bundle targets an older Symfony and Sonata generation, so you must verify the exact constraint set with Composer before committing. Check its composer.json for supported PHP, symfony/*, and sonata-project/admin-bundle versions, then run a time-boxed resolution spike against your target stack. Treat Symfony 6 or 7 and Sonata 4 or 5 compatibility as unproven until Composer proves otherwise.
- How do I install picoss/sonata-extra-admin-bundle?
- Install it with Composer, then register the bundle in config/bundles.php in your Symfony application. Add or create configuration under the bundle's namespace, then opt individual admin classes into its interfaces and form types. There is no Laravel package discovery step.
- What extra CRUD actions does this bundle add to Sonata Admin?
- It adds reusable CRUD actions and controller helpers for common admin workflows, plus extra form types and field widgets. Admin extensions let you customize listings and forms, and admin classes can implement interfaces such as ExportableAdminInterface and SortableInterface. The goal is less boilerplate on top of Sonata's existing conventions.
- Is this bundle maintained and safe for production?
- There is little production signal: around 18 stars, no known dependents, and no visible CI, test suite, release cadence, or security policy. Because it renders inside an authenticated privileged admin surface, unpatched code carries real consequence. Pin a version, name an internal owner for patching, and avoid adopting it without a fallback.
- What alternatives should Laravel developers use instead of Sonata Admin?
- For Laravel, Filament, Laravel Nova, or a custom Livewire or Inertia admin cover the same ground natively. Recommending this bundle to a Laravel team would imply a Symfony migration far out of proportion to a few admin conveniences. For Symfony and Sonata shops, compare it against reimplementing the same patterns natively.
- How do I configure the export functionality in Sonata Admin with this bundle?
- Implement ExportableAdminInterface on your admin class and configure the export fields through the bundle's fluent Exporter. Then expose the export action through Sonata's admin routing and templates. Verify the generated output against your data types and access rules before shipping.
- How do I make Sonata Admin listings sortable with a position column?
- Have the admin class implement SortableInterface and use the bundle's PositionType form field for the ordering column. That gives you position handling within Sonata's existing listing and form conventions. Test reordering against your Doctrine mapping and any unique constraints.
- Can I use this bundle if I'm on Symfony 6 or 7?
- Not confirmed. The bundle targets an older Symfony and Sonata generation, so Composer constraint resolution against Symfony 6 or 7 is the gating question. Run a short spike and expect a possible stop outcome rather than assuming support.
- What are the risks of adopting this bundle, and how should I evaluate it?
- Main risks are version drift, single-maintainer abandonment, silent behavioral changes on Sonata minor upgrades, and knowledge concentration in one engineer. Prefer reimplementing the small useful patterns natively, or fork and vendor with a pinned version and a named owner. Adopt behind a feature flag only if you already run Symfony with Sonata Admin and have budgeted maintenance.