- Is lag/adminbundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. v1.0.3 confirms this with Symfony-native constructs such as config/bundles.php registration, DI extension loading, tagged services, Twig templates, and an AdminDataCollector for the Symfony profiler. The Laravel admin-panel description in the blurb does not match the shipped artefact.
- Does Lag AdminBundle work with Laravel 11 or Laravel 12?
- Not out of the box. v1.0.3 is on the legacy 1.x line and centers on Symfony 3.4 compatibility, which targets PHP 5.5.9 through 7.4, while Laravel 11 and 12 require PHP 8.2 or newer. Dependency resolution will likely fail unless the Composer constraint spans Symfony ^3.4 through ^7.0, which is implausible for a 1.0.x bugfix release.
- How do I install lag/adminbundle in a Laravel app?
- There is no supported Laravel installation path. The package expects Symfony bundle registration via config/bundles.php and Symfony DI extension loading, not a Laravel service provider or package discovery. You would be building an adapter or port rather than running composer require and publishing config.
- What Laravel version support does lag/adminbundle provide?
- None is documented or evidenced. The shipped 1.x release line is Symfony 3.4-oriented, and the documented PHP 8.4 and Symfony 7.0 target appears to live on an unreleased feat/v2.0 branch. Laravel compatibility is not part of the shipped compatibility matrix.
- Can I use lag/adminbundle CRUD scaffolding with Eloquent models?
- Only with significant adapter work. The bundle data layer is almost certainly Doctrine-oriented, and its ProviderInterface, ProcessorInterface, and ResourceInterface services are tagged Symfony services. A realistic Eloquent adapter would need to implement those contracts against Eloquent, which is the deepest incompatibility in the package.
- What is the difference between lag/adminbundle v1.0.3 and feat/v2.0?
- v1.0.3 is a cosmetic bugfix release on the legacy 1.x line, re-adding Symfony 3.4 support for the Flex recipe and fixing an AdminDataCollector. feat/v2.0 is documented as targeting PHP 8.4 and Symfony 7.0 but is unreleased and possibly abandoned. Packagist currently ships the legacy line, not the modern rewrite.
- Is lag/adminbundle safe for production admin panels?
- Risk is high. The 1.x line pulls in Symfony 3.4 and 4.4, which are end-of-life and carry unpatched advisories, into the highest-privilege part of your application. You would also own fork maintenance and security patching, with no clear upstream owner for the Laravel use case.
- How do I test lag/adminbundle in a Laravel application?
- Testing is not straightforward because the bundle relies on Symfony's event dispatcher, Twig, and profiler data collectors. You would need a Symfony kernel or a substantial bridge layer before meaningful feature tests. Unit-testing the portable PHP 8 attribute metadata layer is the only low-friction option.
- What are alternatives to lag/adminbundle for Laravel admin panels?
- For Laravel, evaluate Filament, Laravel Nova, or Backpack, which are Laravel-native and maintained against current PHP and Laravel versions. For modern Symfony, EasyAdmin is the natural fit. Ruling out an off-the-shelf alternative should happen before considering a port of this bundle.
- Is lag/adminbundle maintained, and will there be a Laravel-native version?
- The project shows signs of a stalled rewrite. Release activity on 1.x has been cosmetic, and feat/v2.0 is documented but unreleased, which is the classic signature of an abandoned 2.0 effort. There is no announced Laravel-native version, so you should not plan adoption around one.