Weave Code
Crud Bundle Laravel Package
opifer/crud-bundle
OpiferCrudBundle provides configurable CRUD screens for Symfony applications, generating list, create, edit, and delete actions for Doctrine entities from bundle configuration. It can speed up simple admin interfaces, but expect limited documentation and community support.
Opifer CrudBundle is a Symfony bundle for rapidly building CRUD interfaces over Doctrine entities. Rather than hand-writing controllers and templates for every admin resource, you declare actions in configuration and let the bundle wire up routing, forms, and rendering.
Its extensible action system lets you reuse, override, or replace default list, show, create, edit, and delete behaviour, while Twig templates with overridable blocks keep the UI adaptable without touching the scaffolding.
- Configuration-driven CRUD definitions
- Doctrine ORM integration
- Reusable and custom actions
- Overridable Twig templates
- Extensible base classes for resources
Frequently asked questions about Crud Bundle
- Is opifer/crud-bundle a Laravel package?
- No. Opifer CrudBundle is a Symfony bundle for building configurable CRUD interfaces, and it has no Laravel service provider, facade, config publishing, or package auto-discovery. Adopting it in Laravel would require embedding Symfony components or reimplementing the CRUD scaffolding natively. For Laravel CRUD work, use a Laravel-native package such as Filament or Nova.
- How do I install opifer/crud-bundle?
- You would install it with Composer as a Symfony bundle, then register it in the Symfony kernel and configure Doctrine entities, routing, and forms. There is no composer require-and-go path for Laravel because the package does not support Laravel package discovery or the Laravel service container. The repository is archived and last released in September 2015, so installation on modern stacks is likely to fail without a fork.
- Does opifer/crud-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony 2.x-era APIs and was last released in September 2015, long before Laravel 10 and 11 existed. Its Symfony bundle and Doctrine assumptions are incompatible with Laravel's container, routing, middleware, and Eloquent ORM. There is no maintained compatibility layer for modern Laravel versions.
- What PHP and Symfony versions does opifer/crud-bundle require?
- The bundle dates from the PHP 5.x and Symfony 2.x era, with the last release in September 2015. Exact constraints are not documented in the overview, but its dependency graph will conflict with modern PHP 8.x and Symfony 5, 6, or 7 projects. Expect to fork and refactor if you need it on a current stack.
- Is opifer/crud-bundle still maintained?
- No. The GitHub repository is archived, the last release was September 2015, and the package has about 2 stars and 0 dependents. That means no security patching, no PHP version updates, and no dependency maintenance. Treat it as abandoned software rather than an active dependency.
- Can I use opifer/crud-bundle in production?
- It is not advisable. Archived, unmaintained code has no CVE response process and will likely conflict with modern Composer dependency graphs, which is difficult to clear in security-reviewed or regulated environments. If a legacy Symfony app already uses it, time-box a fork with pinned dependencies and plan a replacement. For new Laravel work, choose a maintained CRUD package instead.
- What are the best alternatives to opifer/crud-bundle for Laravel CRUD?
- For Laravel, consider Filament or Laravel Nova for admin panels and CRUD scaffolding, or build a native CRUD layer with Eloquent, form requests, and resource controllers. If you are actually on Symfony, EasyAdmin or API Platform are the maintained equivalents. The right choice depends on whether your target stack is Laravel or a legacy Symfony application.
- How do I migrate from opifer/crud-bundle to Laravel?
- Do not extend the bundle. Identify the specific CRUD screens and admin workflows it provides, then map them to Laravel-native patterns or a maintained admin package such as Filament or Nova. If a short-term bridge is unavoidable, vendor-fork the bundle into a private namespace, pin transitive dependencies, and set an explicit removal date. This is a strangler-style replacement, not a direct integration.
- Can I test opifer/crud-bundle with Laravel's testing tools?
- Not meaningfully. The bundle assumes Symfony's kernel, forms, routing, and Doctrine entities, so Laravel's HTTP tests, factories, and database testing helpers do not apply. You would be testing a hybrid framework footprint that is hard to onboard and upgrade. Native Laravel CRUD code or a Laravel-native package is far easier to test.
- What is opifer/crud-bundle used for?
- It is a Symfony bundle for scaffolding configurable admin-style create, read, update, and delete interfaces with reusable controllers, routing, forms, and list views. It was intended for Symfony 2 projects using Doctrine ORM, not Laravel applications. Because it is deprecated and archived, it should only be relevant to legacy Symfony maintenance or migration planning.
Weaver
How can I help you explore Laravel packages today?