Weave Code
Sonata Bundle Laravel Package
smartbooster/sonata-bundle
smartbooster/sonata-bundle is a Symfony bundle that integrates SmartBooster with Sonata Admin. It provides the configuration and wiring needed to connect Sonata-based admin panels to SmartBooster services, reducing custom glue code for teams building admin integrations.
SMART BOOSTER Sonata setup
Frequently asked questions about Sonata Bundle
- Does smartbooster/sonata-bundle work with Laravel?
- No. smartbooster/sonata-bundle is a Symfony bundle built to integrate SmartBooster with Sonata Admin, so it depends on Symfony's bundle registration, service container and Sonata Admin classes. Laravel has no bundle or service-tag system, so the package cannot be installed into a Laravel application in a meaningful way. If you are evaluating it for a Laravel project, look for a Laravel-native admin panel integration instead.
- How do I install and register smartbooster/sonata-bundle?
- Install it with Composer using composer require smartbooster/sonata-bundle, then register the bundle in your Symfony application. On Symfony 4 and later this means adding it to config/bundles.php; on older Symfony versions you register it in AppKernel. After registration, check the package README and config reference for the required configuration keys and any service definitions you need to enable.
- Which Symfony, PHP and Sonata Admin versions are supported?
- Version support is defined by the require constraints in the package's composer.json and can change between releases. Check those constraints against your Symfony and PHP versions before installing, and confirm the Sonata Admin major version you run is compatible. Because Sonata Admin has had breaking changes across majors, pinning a known-good package version is safer than floating to latest.
- How do I map SmartBooster resources to Sonata Admin?
- The bundle lets you declare resource mappings in its bundle configuration, which the package uses to wire SmartBooster resources to the relevant admin classes and services. You supply the mapping for the resources you want to expose, and Sonata Admin then renders them as list, show, create and edit screens. Review the configuration reference in the repository for the exact key names and required values, since the README excerpt is not exhaustive.
- Do I still need to write my own Sonata Admin classes?
- In most cases no. The bundle ships preconfigured admin classes and service definitions so you can expose SmartBooster resources in Sonata with minimal boilerplate. You only need custom admin classes when you want fields, filters, form types or actions that differ from the provided defaults. If your requirements are standard, registration plus resource mapping is usually enough.
- How do I override or extend the preconfigured admin classes and services?
- The bundle is designed to be lightweight and extensible, so the usual Symfony patterns apply: subclass the provided admin classes and re-register the service with your own definition, or override service arguments in your application's services.yaml. You can also decorate the bundle's services if you only need to change one behaviour rather than replace a whole admin class. Keep overrides in your own bundle or app config rather than editing vendor files, so Composer updates do not wipe them.
- How do I configure Sonata Admin menu entries for these resources?
- The bundle supports flexible configuration for resource mapping and menus, so menu groups and entries can be declared in configuration rather than hard-coded. You typically add the admin services to a Sonata menu group and let the bundle's configuration define the labels and ordering. Verify the menu keys against the package configuration reference, and clear the Symfony cache after changing them.
- How should I test the Sonata Admin integration?
- Test it with Symfony's KernelTestCase and WebTestCase so the bundle and its container wiring are actually booted during the test. A pragmatic approach is a smoke test that logs in as an admin user and asserts the list and edit pages for one mapped resource return a successful response, plus a unit test around any custom admin class logic. Use a test database fixture so list pages do not depend on production data.
- Is smartbooster/sonata-bundle safe to use in production, and how is it maintained?
- It is a thin integration bundle, so most production risk comes from the underlying Sonata Admin and SmartBooster versions rather than the bundle itself. Pin the package to a specific version, review the repository's commit history, release tags and open issues to judge maintenance activity, and watch for Sonata Admin major upgrades that may require changes. Treat it as standard vendor code: lock it, test it in staging and monitor for compatibility breaks.
- What are the alternatives if I need this functionality in Laravel or another admin panel?
- For Laravel applications the alternatives are Laravel-native admin stacks such as Filament or Nova, with a custom integration to SmartBooster's API or services. For Symfony projects that do not use Sonata, you would need to build your own admin UI against the same SmartBooster services this bundle wires up. If you are already on Sonata Admin, using this bundle is generally less work than writing the service wiring and admin classes yourself.
Weaver
How can I help you explore Laravel packages today?