Missing symfony1 plugin model generation strategy.

[alanbem]

In symfony1 every model class in plugin consisted - through inheritance - of base model, plugin model and application model on top. I really miss that as it allowed to add application specific logic to 3rd party plugins. These days when using 3rd-party bundle, it is not possible.

This issue is not feature request per se, but rather a question why propel bundle abandoned that behavior.

Cheers

P.S. I know that Symfony2 application architecture does not conform easily to this legacy model generation strategy, but I think that with few modifications and new conventions it could be done.

[havvg]

Well, this is nothing that was done by the propel plugin itself, but the 3rd party plugins followed a convention, to add their business logic in a class in between the base and model class. Once they got the model class, with different inheritance, Propel didn't touch those, that's why it worked the way it did (and still works with Symfony2 bundles, if they apply those rules).