I've came into a problem with plugin's configuration in 1.1. I'm using propel generated forms, allong with propel behaviors. Behaviors work well in a web request context, but when running the propel:generate-forms task the plugin's config.php is not included, causing sfPropelBehavior::registerHooks and sfPropelBehavior::registerMethod calls not being called, and so an exception is thrown when Peer class is included and sfPropelBehavior::add(...)is called, because the specified behavior has not been registered.
I was discussing this with Nicolas Perriault sooner, and we came to think that plugin's having still a config.php is a leak in 1.1 new configuration system. We came to think we should have a sfPluginConfiguration class like for project and app, and replacing the config.php by a xxxPluginConfiguration. Then, initialization, finalization, paths and so on can be fine tuned in a clean way. IMHO, this plugin's config.php is the last sequel of symfony 1.0's weak configuration system. What do you all think of it? -- -=( Romain Dorgueil )=-=( Web Developer )=-=( symfony&linux addict )=- http://dakrazy.net/ http://symfony-project.org/ http://sensiolabs.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
begin:vcard fn:Romain Dorgueil n:Dorgueil;Romain email;internet:[EMAIL PROTECTED] tel;cell:+33 6 79 07 61 70 version:2.1 end:vcard
