[symfony-users] Re: actAs Timestampable requiring created_at in update
Guys, I made a database/model rebuild, then reloaded the data, and the problem disappeared. Strange, uh?! I mean, I never touched the Base models, only the custom ones, but rebuilding brought my system back. I'm trying to remember if there was some part I shouldn't have messed with but did it anyway... Well, problem solved! :-) Thank you, guys! Diogo On 20 jan, 16:37, Dennis gear...@sbcglobal.net wrote: Very interesting problem. Sounds like you might need to use a debugger or a lot of 'die(got here at.__LINE__);' statements in the symfony libraray if his tip doesn't work. On Jan 20, 4:44 am, diogobaeder diogobae...@gmail.com wrote: Hi, Benoit, I'll try your tip, but it's strange because it started to happen just these days, and I've been developing the website for about a month now... and the website at a test environment works correctly, even with actAsTimestampable. At this test environment, the updated query built, seen in the log, doesn't contain the created_at field, so the update works, but at my local environment it contains the field and passes a null value in the update, and that's what makes the update fail. I searched thoroughly for diffs in the directories, comparing local to remote test folders, but didn't find the problem. Also, this problem only happens to one model in the system, the others that contain actAsTimestampable work flawlessly. Any clues of why it started to happen? Thanks! On Jan 20, 8:46 am, Benoit Montuelle benoit.montue...@gmail.com wrote: It's perfectly normal. These 2 field added by actAsTimestampable Behavior are not to be editable by users. You should remove them in your form class configure() method : unset($this['created_at']); unset($this['updated_at']); Hope this helps Regards, Benoit Le 20 janv. 2010 à 06:09, diogobaeder diogobae...@gmail.com a écrit : Hi, guys, I don't know why, but a website I'm developing started to pass the created_at field in the update query when I try to save an edited admin form with a null value, so I cannot save the data anymore. Any idea of what might be wrong? I'm using Symfony 1.4. Thanks! Diogo -- You received this message because you are subscribed to the Google Groups symfony users group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com . For more options, visit this group athttp://groups.google.com/group/symfony-users?hl=en . -- You received this message because you are subscribed to the Google Groups symfony users group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
[symfony-users] Re: actAs Timestampable requiring created_at in update
Hi, Benoit, I'll try your tip, but it's strange because it started to happen just these days, and I've been developing the website for about a month now... and the website at a test environment works correctly, even with actAsTimestampable. At this test environment, the updated query built, seen in the log, doesn't contain the created_at field, so the update works, but at my local environment it contains the field and passes a null value in the update, and that's what makes the update fail. I searched thoroughly for diffs in the directories, comparing local to remote test folders, but didn't find the problem. Also, this problem only happens to one model in the system, the others that contain actAsTimestampable work flawlessly. Any clues of why it started to happen? Thanks! On Jan 20, 8:46 am, Benoit Montuelle benoit.montue...@gmail.com wrote: It's perfectly normal. These 2 field added by actAsTimestampable Behavior are not to be editable by users. You should remove them in your form class configure() method : unset($this['created_at']); unset($this['updated_at']); Hope this helps Regards, Benoit Le 20 janv. 2010 à 06:09, diogobaeder diogobae...@gmail.com a écrit : Hi, guys, I don't know why, but a website I'm developing started to pass the created_at field in the update query when I try to save an edited admin form with a null value, so I cannot save the data anymore. Any idea of what might be wrong? I'm using Symfony 1.4. Thanks! Diogo -- You received this message because you are subscribed to the Google Groups symfony users group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com . For more options, visit this group athttp://groups.google.com/group/symfony-users?hl=en . -- You received this message because you are subscribed to the Google Groups symfony users group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
[symfony-users] Re: actAs Timestampable requiring created_at in update
Very interesting problem. Sounds like you might need to use a debugger or a lot of 'die(got here at.__LINE__);' statements in the symfony libraray if his tip doesn't work. On Jan 20, 4:44 am, diogobaeder diogobae...@gmail.com wrote: Hi, Benoit, I'll try your tip, but it's strange because it started to happen just these days, and I've been developing the website for about a month now... and the website at a test environment works correctly, even with actAsTimestampable. At this test environment, the updated query built, seen in the log, doesn't contain the created_at field, so the update works, but at my local environment it contains the field and passes a null value in the update, and that's what makes the update fail. I searched thoroughly for diffs in the directories, comparing local to remote test folders, but didn't find the problem. Also, this problem only happens to one model in the system, the others that contain actAsTimestampable work flawlessly. Any clues of why it started to happen? Thanks! On Jan 20, 8:46 am, Benoit Montuelle benoit.montue...@gmail.com wrote: It's perfectly normal. These 2 field added by actAsTimestampable Behavior are not to be editable by users. You should remove them in your form class configure() method : unset($this['created_at']); unset($this['updated_at']); Hope this helps Regards, Benoit Le 20 janv. 2010 à 06:09, diogobaeder diogobae...@gmail.com a écrit : Hi, guys, I don't know why, but a website I'm developing started to pass the created_at field in the update query when I try to save an edited admin form with a null value, so I cannot save the data anymore. Any idea of what might be wrong? I'm using Symfony 1.4. Thanks! Diogo -- You received this message because you are subscribed to the Google Groups symfony users group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com . For more options, visit this group athttp://groups.google.com/group/symfony-users?hl=en . -- You received this message because you are subscribed to the Google Groups symfony users group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
