I fixed this in [30123]. It's really old, goes back to the restart of sfDoctrineGuardPlugin. It's surprising that it never crashed for anyone else. I couldn't reproduce your error, which is strange, because it seems like Symfony can't know what task names exist without loading all of the task classes, which should have triggered the duplicate class error for everyone. But at any rate guard:create-admin is now a functioning task which is identical to guard:create-user except that it sets the superadmin flag. (And it has a different class name. (: )
On Tue, Jul 6, 2010 at 10:55 AM, Thomas Rabaix <[email protected]> wrote: > Hello, > > Please review this ticket http://trac.symfony-project.org/ticket/7877. for > now the branch 1.3 is broken and cannot be used ... > > It will take 15 secondes to fix for someone who have the write permission on > this plugin ... > > thanks > > -- > Thomas Rabaix > http://rabaix.net > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.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 > -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.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
