Weave Code
Propel1 User Bundle Laravel Package
friendsofsymfony/propel1-user-bundle
Propel1UserBundle integrates FOSUserBundle with the Propel 1 ORM, providing a Propel-backed user model and provider for Symfony apps. It lets Propel projects use FOSUserBundle’s registration, authentication, and user management features without Doctrine.
Propel 1.x integration for FOSUserBundle
Frequently asked questions about Propel1 User Bundle
- Is friendsofsymfony/propel1-user-bundle a Laravel package?
- No. It is a Symfony bundle that provides a Propel 1 persistence backend for FOSUserBundle, and it has no Laravel integration of any kind. Laravel has no bundle system, and this package registers through a Symfony Bundle class plus a DI container extension rather than a Laravel service provider. There is no seam for Laravel's HTTP kernel or auth guards to hook into.
- Can I use this package for authentication in a Laravel application?
- Not feasibly. The package implements Symfony's UserProviderInterface and FOSUserBundle's UserManagerInterface, while Laravel guards expect Illuminate\Contracts\Auth\UserProvider and Authenticatable implementations. There is no shared interface or adapter layer, so nothing is reusable as a dependency. If you need Laravel authentication, use Fortify, Breeze, or Jetstream instead.
- How do I install friendsofsymfony/propel1-user-bundle?
- It was installed with Composer in Symfony 2.3 to 2.8 era applications and registered as a bundle in the kernel, alongside FOSUserBundle and Propel 1. The bundle is archived and has no maintainer, so a fresh install is not recommended even in legacy Symfony projects. If you inherit a project that already requires it, check the pinned versions in composer.lock before attempting anything.
- Which Laravel versions does this bundle support?
- None. The package targets Symfony applications using Propel 1.x and predates modern PHP typing, so Laravel 9, 10, and 11 are entirely out of scope. Even on Symfony, only the 2.x era with FOSUserBundle is historically plausible. PHP 8.x compatibility is unverified and plausibly broken by removed behavior.
- What is the difference between Propel 1 and Eloquent for user management?
- Propel 1 generates model classes at build time from an XML schema via propel-gen, while Laravel expects Eloquent models backed by migration-driven schema. Nothing transfers between the two without a hand-written schema port plus an ETL for existing user data. Laravel's built-in user provider and manager already cover the same responsibilities natively.
- Is this bundle still maintained or safe for production?
- No. It is archived, has zero stars and zero dependents, and has no maintainer, which means no upstream fixes, no CVE triage, and no security response for code sitting in your credential path. For SOC 2 or ISO 27001 environments that is a compliance finding rather than a footnote. The only clean positive is the MIT license, which makes forking legally unencumbered if someone is prepared to own the result.
- How does password hashing work with this bundle, and is it upgradeable?
- It ships with whatever historical hashing defaults were current when the code was frozen, with no upgrade path short of forking and owning the implementation. That is a real risk for credential handling because you cannot rely on upstream to modernize algorithms. If you must keep it temporarily, plan a rehash-on-login migration to a current algorithm.
- How do I test this bundle for compatibility before planning a migration?
- Treat PHP 8.x compatibility as a hard gate rather than a nice-to-have spike. Pin the exact FOSUserBundle, Propel, Symfony, and PHP versions from composer.lock, then run the existing authentication and password reset flows in an isolated environment. If anything breaks, the realistic outcome is a rewrite in which no PHP 5-era syntax, Symfony DI wiring, or generated Propel Base classes survive.
- What are the alternatives to this bundle for Symfony or Laravel projects?
- On the Symfony side, current Symfony Security with MakerBundle replaces FOSUserBundle plus this Propel backend. On the Laravel side, Laravel Fortify, Breeze, or Jetstream provide native guards, providers, and password reset flows. Native tooling wins on every axis, including maintenance, security patching, and upgrade paths. This bundle is best treated as a dependency-inventory signal and a reference pattern for separating a user manager from a user provider.
- Should I fork this bundle to keep an inherited Symfony application running?
- Only if the requirement is genuinely to run an inherited Symfony plus Propel 1 app and someone is prepared to own security patching for the credential path. The decision to frame is freeze-and-migrate versus carrying it indefinitely, not whether to integrate it. Before forking, identify the hard cutover date, the on-call owner for patching, and any regulatory constraints such as PCI or HIPAA that make unmaintained credential handling disqualifying. A scoped port to current Symfony Security is usually cheaper than indefinite ownership.
Weaver
How can I help you explore Laravel packages today?