- Is rz/doctrine-orm-admin-bundle a Laravel package?
- No. It is a Symfony2 bundle that extends SonataDoctrineORMAdminBundle and depends on the Symfony 2.x kernel, Doctrine ORM, and SonataAdminBundle. Laravel has no bundle system or Symfony kernel, so there is no runtime surface for it to hook into. Treat it as a Symfony/Sonata package, not a Laravel one.
- Can I use rz/doctrine-orm-admin-bundle in a Laravel application?
- Realistically, no. Composer resolution will fail against a modern Laravel and PHP 8.x stack because the package targets Symfony2-era components and old Doctrine constraints. Even a bespoke bridge would be unsupported and a permanent maintenance liability. Use a Laravel-native admin framework instead.
- What does rz/doctrine-orm-admin-bundle actually do?
- It is a thin extension of SonataDoctrineORMAdminBundle that wires Doctrine ORM entities into Sonata's admin CRUD screens for browsing, creating, editing, and deleting records. Its own code surface is small; most behavior lives in the parent Sonata bundles. It is designed for Symfony2 applications, not Laravel.
- Does rz/doctrine-orm-admin-bundle support Laravel 10 or Laravel 11?
- No. The package predates modern Laravel and is constrained to Symfony2-era dependencies that do not resolve on current PHP 8.x runtimes. There is no supported version pairing for any current Laravel LTS. Expect composer install to fail before you write application code.
- How do I install rz/doctrine-orm-admin-bundle?
- In a legacy Symfony2 project you would require it via Composer alongside SonataAdminBundle and SonataDoctrineORMAdminBundle, then register the bundle in the Symfony kernel. In a Laravel project there is no supported installation path. The repository is archived, so even legacy installs depend on unmaintained transitive packages.
- Is rz/doctrine-orm-admin-bundle maintained and safe for production?
- No. The repository is archived, has zero stars and zero dependents, and pulls in end-of-life Symfony2 and old Doctrine components. Symfony 2.8 reached end of life in 2018, so there is no upstream to patch security issues. Using it in production is a supply-chain and CVE exposure.
- What are the best Laravel alternatives to rz/doctrine-orm-admin-bundle?
- For Laravel admin CRUD, evaluate Filament, Laravel Nova, or Backpack for Laravel. All three are actively maintained, integrate with Eloquent and Laravel's service container, and support current PHP and Laravel versions. If your real target is legacy Symfony/Sonata, evaluate SonataDoctrineORMAdminBundle directly instead of this extension.
- Does rz/doctrine-orm-admin-bundle work with Eloquent?
- No. It is built around Doctrine ORM entity metadata and the Doctrine entity manager, while Laravel's Eloquent is a separate ORM with a different lifecycle and no shared metadata layer. There is no adapter that makes a Sonata Doctrine extension work with Eloquent. Porting the admin screens to a Laravel admin framework is the practical path.
- How do I migrate a Sonata Doctrine ORM admin to Laravel?
- Inventory the admin screens, filters, entity relationships, and permissions, then re-implement them on a Laravel admin framework such as Filament, Nova, or Backpack. Budget this as feature work, not as a package integration, because there is no viable bridge. This package is what you would be migrating away from, not adopting.
- Is there a Laravel bridge or adapter for Sonata admin bundles?
- No supported bridge exists. Embedding a Symfony kernel inside Laravel is technically possible but would drag Symfony2, Sonata, and old Doctrine into your dependency graph solely to run an archived admin extension. The operational complexity far outweighs any value, and your team would own the bridge forever.