+1,

IMO by default it should not be displayed in autogenerated fields,
because those fields are automatically filled, and should not be
overwritten normally by hand. Think of it in terms of audit reliability,
would you believe a system where those values can be changed in the
basic admin form?
Ideally for me would be an additional option in the Timestampable behavior:

  actAs:
# ...
    Timestampable:
      created:
        name: created_at
        type: timestamp
        format: Y-m-d H
        show_in_admin_form: false
      updated:
        disabled: true

And a postconfig listener would just unset the field in the admin form
if the option 'show_in_admin_form' is false (which should be the default
behavior).

Georg

Am 11.12.2009 22:47, schrieb ashton honnecke:
> I don't think that those fields should be in the form in the first
> place.  That's my point.  One of the first things that I do when I set
> up the admin generator is add this to BaseFormDoctrine::setup:
> unset($this['created_at'], $this['updated_at']);
> 
> This makes the admin generator behave the way that I want it to, and
> that way that I think most people use it for.
> 
> On Fri, Dec 11, 2009 at 11:47 AM, Richtermeister <[email protected]> wrote:
>> Hey Felix, I believe the reason is that the admin generator is the
>> wrong place to hide those fields..
>> Not displaying the fields doesn't remove them from the form, so in
>> effect you'd be submitting empty values for those fields.
>> Could be wrong, but I believe that's one of the issues..
>>
>> Daniel
>>
>>
>> On Dec 10, 1:45 pm, Felix Ebert <[email protected]> wrote:
>>> It's a miracle for me why ticket 6836 got closed. I thought that
>>> Symfony is a framework with the principle "convention over
>>> configuration" - and I don't see any usecase of displaying the
>>> created_at and updated_at fields in the auto-generated forms by
>>> default.
>>
>> --
>>
>> 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.
>>
>>
>>
> 
> --
> 
> 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.
> 
> 
> 

--

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.


Reply via email to