- Can I use smirik/propel-admin-bundle in a Laravel application?
- No. This is a Symfony 2 bundle built around Propel 1.x, Twig 1, and Symfony's dependency injection container and bundle registration model. It has no service providers, no Blade views, and no Eloquent or Doctrine integration, so every seam a Laravel app would need is missing. For a Laravel codebase the integration fit is effectively zero and there is no migration path short of a rewrite.
- Which Symfony, Propel, and PHP versions does propel-admin-bundle support?
- The package targets Symfony 2.x, which reached end of life in 2015, together with Propel 1.x and PHP 5.x-era language idioms. It relies on Twig 1 API surfaces and removed PHP functions such as create_function and each(). No compatible constraint set has been published for modern PHP, Symfony, or Composer 2.
- Why does composer require smirik/propel-admin-bundle fail on PHP 8 or Composer 2?
- Composer 2 will typically refuse to resolve the dependency graph, or resolution succeeds and the code fatals at runtime. The bundle uses functions like create_function and each() that were removed in PHP 8, and it calls Twig 1 APIs that no longer exist in Twig 2 or 3. There is no maintained branch that addresses either problem.
- How do I install and register propel-admin-bundle in a legacy Symfony 2 project?
- You add it to composer.json inside a frozen Symfony 2 + Propel application and enable SmirikPropelAdminBundle in AppKernel alongside your Propel and Twig configuration. Admin sections are then declared in the bundle's configuration so routing, controllers, and templates can be wired to your models. This only makes sense as a vendor artifact pinned inside an existing legacy stack, never as a new live dependency.
- What screens does the propel-admin-bundle admin generator actually create?
- It generates the standard CRUD set for each Propel model: list, create, edit, and delete screens. Columns, forms, and available actions are configurable per model, and the bundle plugs these screens into Symfony routing, controllers, and templates. The intent is to remove boilerplate for back-office and internal tools rather than to provide a full admin framework.
- How do I configure columns, forms, filters, and actions for a model?
- Configuration is declarative: you map model fields to list columns and form fields, and declare the actions available per record, with the bundle generating the corresponding templates and controller behaviour. Because the project is archived and documented mainly by example, the bundle's own config files and templates are the practical reference. Expect to read the source to understand edge cases, since there is no maintained documentation site.
- Is smirik/propel-admin-bundle still maintained?
- No. The repository is archived and the last substantive release activity was 2013-07-03. It has roughly 8 stars and 0 dependents, which means the integration path has essentially never been walked outside the original author. The v1.0.0 release note contains no changelog, compatibility statement, or security disclosure.
- Does the 1.0.0 release mean propel-admin-bundle is stable and production ready?
- No. In semver, 1.0.0 conventionally signals an API-stability commitment, but there is no upstream maintainer capacity to honour that commitment. The entire release note reads that the bundle is officially live and free to use, with no diff summary or version-constraint change. The tag should be read as decorative rather than as a stability guarantee.
- What are the maintained alternatives to propel-admin-bundle?
- For Laravel, use Filament, Laravel Nova, Backpack, or Orchid, all of which are actively maintained and Eloquent-based. For Symfony, EasyAdmin and SonataAdmin cover the same CRUD admin generator use case on supported versions. If your actual need is a one-time code-generation scaffold, reading this bundle's templates is recoverable; a maintained admin UI is not.
- Is it safe to run a propel-admin-bundle admin panel in production?
- An admin surface is the highest-privilege area of an application, and this bundle ships with 2013-era authentication, authorisation, and CSRF assumptions. Adopting it transfers ownership of every future PHP, Symfony, Propel, and Twig security patch to your team. Keep it behind an internal network in a legacy estate, or reimplement the CRUD screens on a maintained stack before exposing anything publicly.