- Can I use GlorpenPropelBundle in Symfony 5/6/7 or Laravel? The README says Symfony2 only.
- No, this bundle is explicitly designed for Symfony2 and won’t work in modern Symfony (5+) or Laravel. If you’re on a newer stack, consider alternatives like Doctrine’s event system or Propel’s standalone tools. For Symfony2, ensure your project isn’t planning an upgrade soon, as maintenance is unlikely.
- How do I install GlorpenPropelBundle in an existing Symfony2 project?
- Run `composer require glorpen/propel-bundle` in your project root. Then enable the bundle in `app/AppKernel.php` under `registerBundles()`. Verify Propel is installed (`composer require propel/propel`) and configured in `app/config/config.yml` before proceeding. Check the bundle’s docs for Symfony2-specific configuration quirks.
- Does this bundle work with Doctrine ORM? I’m currently using both in my app.
- No, this bundle is for Propel ORM only. Mixing Propel and Doctrine in the same app can cause conflicts in event listeners, model hydration, and dependency injection. If you’re using Doctrine, you’ll need to migrate to Propel entirely or avoid this bundle. Propel’s event system won’t integrate cleanly with Doctrine’s lifecycle callbacks.
- What’s the best way to extend Propel models dynamically without modifying the base classes?
- GlorpenPropelBundle provides tools to extend Propel models via behaviors or event listeners. For example, you can attach logging, validation, or caching logic by subscribing to Propel’s `postSave`, `postLoad`, or `postInsert` events. Avoid modifying base models directly to keep upgrades easier. Test these extensions in staging first, as side effects (e.g., query performance) can arise.
- Are there any known conflicts with Symfony’s event system or other bundles?
- Yes, Propel’s event system can conflict with Symfony’s kernel events or other bundles using the same event dispatcher. For example, a Propel `postSave` listener might interfere with a Symfony `kernel.request` listener if not isolated. Audit your existing event subscribers before integrating this bundle, and prioritize testing critical workflows like model persistence.
- How do I generate Propel models and schema migrations with this bundle?
- The bundle integrates Propel’s CLI tools into Symfony2, so you can use commands like `propel:build` or `propel:schema:update` directly. Configure Propel’s schema XML files in `app/config/config.yml` under `glorpen_propel_bundle`. For migrations, Propel’s built-in tools (e.g., `propel:schema:diff`) work alongside the bundle, but ensure your `propel.ini` is properly set up for Symfony’s autoloader.
- Is this bundle compatible with Propel 2.x, or only Propel 1.x?
- Check the bundle’s `composer.json` for the required Propel version—older versions may only support Propel 1.x. If you’re using Propel 2.x, verify compatibility by running `composer require glorpen/propel-bundle` in a test environment. Propel 2.x introduced breaking changes, so conflicts are possible. The bundle’s documentation may not cover Propel 2.x specifics.
- What’s the license for this bundle, and can I use it in commercial projects?
- GlorpenPropelBundle is licensed under GPL-3.0, which requires you to open-source your project if you modify or distribute it. For commercial projects, this may not be ideal. If GPL is unacceptable, consider forking the bundle and relicensing it (e.g., MIT) or exploring alternatives like Propel’s standalone tools or custom event listeners.
- How do I test Propel model extensions in a CI/CD pipeline?
- Test model extensions by running Propel’s schema updates (`propel:schema:update`) and then executing unit/integration tests targeting extended models. Use PHPUnit with Propel’s test utilities to verify events fire correctly. In CI, ensure your pipeline runs `propel:build` before tests and checks for schema consistency. Avoid testing in production—use a staging environment with identical Propel/Symfony versions.
- What alternatives exist if I’m stuck on Symfony2 but want Propel features?
- If you’re locked into Symfony2, alternatives include Propel’s standalone tools (e.g., `propel:build`, `propel:schema:diff`) without the bundle, or custom event listeners using Symfony’s `EventDispatcher`. For modern Symfony, consider migrating to Doctrine or using Propel’s Symfony 5+ compatible forks (if available). If you’re open to Laravel, packages like `laravel-propeller` offer Propel integration for that ecosystem.