Weave Code
Adminlist Bundle Laravel Package
kunstmaan/adminlist-bundle
KunstmaanAdminListBundle provides a reusable admin list abstraction for Kunstmaan bundles, letting you define list classes with configurable columns, filters, sorting, pagination, and batch actions to render consistent backend overviews with minimal code.
KunstmaanAdminListBundle provides a reusable, configurable admin list for Symfony applications. Define columns, filters, and actions once via an AdminListConfigurator and get a paginated, sortable overview with minimal boilerplate, integrating cleanly with Doctrine ORM and the Kunstmaan admin UI.
- Configurable columns for text, date, boolean, and template-rendered fields
- Filtering with multiple filter types and query builders
- Sorting and pagination with adjustable page sizes
- Bulk and row actions for custom operations
- Extensible architecture to override rendering and behavior
Frequently asked questions about Adminlist Bundle
- Can I install kunstmaan/adminlist-bundle in a Laravel application?
- No, you should not install kunstmaan/adminlist-bundle in a Laravel application. It is a Symfony bundle that expects Symfony HttpKernel, dependency injection, routing, Doctrine ORM, and adjacent Kunstmaan admin bundles. Laravel's request lifecycle, service container, Eloquent, auth, and Blade conventions do not align without a substantial adapter, which is not realistic for production use.
- Is kunstmaan/adminlist-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The composer name and repository show it is a read-only subtree split from the KunstmaanBundlesCMS, built for Symfony backend admin screens. Its architecture assumes Symfony and Doctrine rather than Laravel and Eloquent.
- What Laravel and PHP versions does kunstmaan/adminlist-bundle support?
- It has no Laravel version support because it is a Symfony bundle, and its last release was 2014-08-07. It likely targets end-of-life PHP and Symfony versions, so do not expect compatibility with modern Laravel or current PHP releases. Check its composer constraints before any experiment, but treat modern Laravel support as unsupported.
- Does kunstmaan/adminlist-bundle work with Laravel Eloquent?
- No, the bundle assumes Doctrine ORM and Symfony dependency injection rather than Laravel Eloquent. Its list filtering, sorting, pagination, inline editing, and export behavior are tied to Doctrine metadata and Symfony services. A Laravel bridge would need to emulate Symfony container, routing, Doctrine mappings, templates, and admin context, which is likely more work than reimplementation.
- How do I build admin list filters and CSV export in Laravel instead of using this bundle?
- Use a maintained Laravel admin stack such as Filament, Laravel Nova, Backpack, or Livewire with custom controllers. Implement filters through query scopes, sorting and pagination through Eloquent, and CSV/Excel export through queued jobs with streaming and storage offload. Document the Kunstmaan bundle's admin-list patterns as a design reference, then build the Laravel-native equivalent screen by screen.
- Is kunstmaan/adminlist-bundle maintained or abandoned?
- It is effectively abandoned. The last release was in 2014, it has only 20 stars and zero dependents, and there is no active upstream support expected. Treat it as a reference implementation for CRUD list patterns rather than a dependency, because your team would own security patches, PHP upgrades, and Symfony compatibility.
- What are good Laravel alternatives to kunstmaan/adminlist-bundle for admin list screens?
- For Laravel, consider Filament, Laravel Nova, Backpack, or Livewire-based custom admin panels. These provide configurable columns, filters, sorting, pagination, bulk actions, and export integrations in a Laravel-native way. Choose based on your authorization model, UI conventions, export volume, and long-term maintenance ownership.
- Can I reuse kunstmaan/adminlist-bundle code in a Laravel project under the MIT license?
- Yes, the MIT license is permissive and allows reuse of code and patterns, but operational ownership shifts fully to your team. Audit the bundle for reusable admin-list behavior, preserve license obligations, and isolate any ported logic behind Laravel services. Avoid coupling Laravel controllers or views directly to Kunstmaan classes.
- What security and production risks come with using kunstmaan/adminlist-bundle?
- The main risks are unmaintained code, stale transitive dependencies, end-of-life PHP/Symfony compatibility, and missing security patches. In production you could hit missing Symfony services, container or routing conflicts, Doctrine metadata errors, template failures, auth mismatches, export timeouts, and memory exhaustion. In a Laravel context, the most likely failure is simply that the bundle cannot boot.
- How hard is it to port kunstmaan/adminlist-bundle to Laravel?
- A direct port is unrealistic because you would need to emulate Symfony dependency injection, routing, Doctrine mappings, templates, and Kunstmaan admin context. The practical path is to run a short spike documenting the bundle's filtering, sorting, pagination, bulk action, inline edit, and export behavior. Then reimplement those capabilities with Laravel-native services, authorization, contracts, and contract tests rather than migrating Laravel into Symfony.
Weaver
How can I help you explore Laravel packages today?