So you are suggesting that I edit the generator.yml for every admin module?
I think that following "convention over configuration" it seems wrong that I should have to jump through the same hoop every time I generate an admin module. Unless there are a bunch of people that want to edit created_at out there? On Fri, Dec 11, 2009 at 12:20 PM, Lukas Kahwe Smith <[email protected]> wrote: > > On 11.12.2009, at 19:47, Richtermeister 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. > > > for a solution have a look here: > http://trac.symfony-project.org/ticket/5296 > > regards, > Lukas Kahwe Smith > [email protected] > > > > -- > > 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.
