Re: "save" oddity

2008-05-01 Thread annie.r.knight
ValidKeys - thanks very much for your helpful answer. On May 1, 2:20 am, validkeys <[EMAIL PROTECTED]> wrote: > p.s if you dont update, > > change your code to this: > function add() { > > if (!empty($this->data)) { > $this->Closeddate->create(); >

Re: "save" oddity

2008-04-30 Thread validkeys
p.s if you dont update, change your code to this: function add() { if (!empty($this->data)) { $this->Closeddate->create(); $this->cleanUpFields(); if ($this->Closeddate->save($this->data)) {

Re: "save" oddity

2008-04-30 Thread validkeys
hey annie, I may be mistaken, but I dont believe it makes a difference if you are running $this->cleanUpFields() on $this->data vs. $this->data[Model]. The $this->cleanUpFields() will turn all of the date inputs into a db compliant variable. If you are using 1.2, just update to the latest nightly

Re: "save" oddity

2008-04-30 Thread annie.r.knight
Thanks for the reply. I print_r'ed the $this->data and I noted that it's split into a number of array elements. That's fine. But why is it necessary to 'clean up' when referring to the data as $this->data['Closeddate'] when it is not necessary with $this->data? On Apr 30, 2:22 pm, djiize <[EMAI

Re: "save" oddity

2008-04-30 Thread djiize
try a pr($this->data) in your controller and you'll the date is not "DB compliant" (it is split in several parts) do a $this->cleanUpFields() before Model->save() On 30 avr, 13:13, "annie.r.knight" <[EMAIL PROTECTED]> wrote: > I'm very new to CakePHP so please do bear with me. > > I've used the s

"save" oddity

2008-04-30 Thread annie.r.knight
I'm very new to CakePHP so please do bear with me. I've used the simple blog application from the manual as a crib for a small application that I'm creating. I ran into a problem when simply trying to deal with some date inputs in forms. The dates would insert ok, but if I tried to edit them I'd