Also have problems with "command.pre_command" (see http://trac.symfony-project.org/ticket/7185)
It appears that command events are not very usable :) On Oct 3, 6:00 am, Tom Boutell <[email protected]> wrote: > I'm trying to take advantage of the command.post_command event, which > is posted by all tasks after they complete their business. The goal > was to extend project:permissions to handle an additional folder. > > I couldn't figure out why registering a handler for this event from > the config.php file of a plugin had no effect. > > Finally I tried putting blatant typos (things that should produce a > PHP parse error) in the config.php file of a known-good plugin, > sfDoctrineGuardPlugin. > > I found that Symfony tasks still didn't fail. While 'php > web/frontend_dev.php' did fail. > > By doing a bit of testing on web/index.php, I determined that > require_once(dirname(__FILE__).'/../config/ProjectConfiguration.class.php'); > doesn't load > the plugin configuration classes and config.php files. That doesn't > happen until we get to: > > $configuration = > ProjectConfiguration::getApplicationConfiguration('frontend', 'prod', > false); > > It appears that the sfCommandApplication class used for tasks never > does the equivalent. So no plugin configuration code is ever run by > tasks. > > Is this a bug in Symfony 1.2.9-DEV? If not, is there any way for a > plugin to register an event handler so that it can do something useful > with events posted by a task? > > Thanks! > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.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 -~----------~----~----~----~------~----~------~--~---
