[symfony-users] Re: Symfony 1.3 and Blameable Doctrine Extension

2009-11-01 Thread David Ashwood
Unset those fields in the form configure method and it should save. It's failing the form validation before the behaviour has a chance to work. On Sun, 2009-11-01 at 05:24 -0800, Fabrizio wrote: > Hi, > I have installed Blameable Extension in the folder > /lib/doctrine_extensions/Blameable/ > fr

[symfony-users] Re: Symfony 1.3 and Blameable Doctrine Extension

2009-11-01 Thread Fabrizio
Hi, tranks for the reply Unfortunately adding the notnull option Blameable: columns: created: name: creato_da type: integer length: 4 options: notnull: false updated: name: aggiornato_da type: int

[symfony-users] Re: Symfony 1.3 and Blameable Doctrine Extension

2009-11-01 Thread David Ashwood
You need to create your own listener that extends from Doctrine_Template_Blameable_Listener and then grab the user id. http://www.doctrine-project.org/extension/Blameable/1_2-1_0 You have a couple of options to get the user id: 1) Use the session object of the app: session: symfony/user/sfUser

[symfony-users] Re: Symfony 1.3 and Blameable Doctrine Extension

2009-11-02 Thread Fabrizio
Hi, thanks for the tips. I have create my listener "BlameableSymfony" Blameable: listener: BlameableSymfony columns: created: name: creato_da type: integer length: 4 options: notnull: false updated: na

[symfony-users] Re: Symfony 1.3 and Blameable Doctrine Extension

2009-11-29 Thread Fabrizio
Hi, about the last problem, now I have upgraded symfony at symfony 1.4.0RC2 and sfDoctrineGuardPlugin to trunk. The problem now is slightly different. When I create a new record, all works fine ( "creato_da" and "aggiornato_da" are set with user id). But when I update a record from admin generato