Hi,

I did unset the widgets, but that wasn't enough. Francois helped me then on the 
propel list. I simply forgot to unset the validator, which caused some weired 
behaviour.

Regards,
Christopher.


> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:symfony-
> [email protected]] Im Auftrag von Tom Ptacnik
> Gesendet: Dienstag, 24. August 2010 07:42
> An: symfony users
> Betreff: [symfony-users] Re: created_at gets deleted on edit
> 
> Try to unset it in the form class (configure method) . . . . .
> unset($this['updated_at']);
> 
> On 18 srp, 15:15, Christopher Schnell <[email protected]>
> wrote:
> > A part of it, I can answer myself:
> >
> > the updated_at column is set to null if I press "save" in the Form
> and do not really make an update (i.e. leave all values, as they are).
> However, updated_at is written if I really update a value.
> >
> > Seems to me like a problem in Propel 1.5.
> >
> > I guess, it will be better to ask in the propel list then.
> >
> > Regards,
> > Christopher.
> >
> >
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: [email protected] [mailto:symfony-
> > > [email protected]] Im Auftrag von Christopher Schnell
> > > Gesendet: Dienstag, 17. August 2010 09:49
> > > An: [email protected]
> > > Betreff: [symfony-users] created_at gets deleted on edit
> >
> > > Hi all,
> >
> > > currently, I am facing a strange problem. My created_at and
> updated_at
> > > values get deleted when editing an object via its form.
> >
> > > Everything should be straightforward, both fields are in my
> schema.yml.
> > > I customize the corresponding Form class via $this-
> > > >useFields(array(...)), so that created_at and updated_at are not
> used
> > > and displayed. But anyway if I update the object, both values are
> set
> > > to null.
> >
> > > I user Symfony 1.4.7-DEV (Trunk as svn External) and
> sfPropel15Plugin.
> >
> > > Did anyone experience such a problem?
> >
> > > Thanks and regards,
> > > Christopher.
> >
> > > ------------------------------------
> > > Christopher Schnell
> >
> > > MdA Business Communications AG
> > > Unterer Rheinweg 86
> > > 4057 Basel
> > > Schweiz
> >
> > > Tel: +41 61 273 44 69
> > > Fax: +41 61 273 44 68
> >
> > > --
> > > 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 users" 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-users?hl=en
> 
> --
> 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 users" 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-users?hl=en

-- 
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 users" 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-users?hl=en

Reply via email to