Strange calendar widget behavior.

[TBriggs]

I have 3 date fields in my database, which I want to show in mm/dd/yyyy format. As recommended in other posts, I have added functions to the file's delegate class:

Code: Select all

    function adoption_date__display(&$record){
        return date('m/d/Y', strtotime($record->strval('adoption_date')));
    }
   function adoption_date__pullValue(&$record, $element){
    return date('m/d/Y', strtotime($record->strval('adoption_date')));
   }

and now the date displays as I wish. When first entering a date with the calendar widget it displays as yyyy-mm-dd, but after pressing "Save" it displays correctly. This I can live with. (I've tried using widget:ifFormat = "%m/%d/%Y", but his doesn't seem to make any difference).

However, the odd thing is that when the date field has an existing value of, say, 9/22/2009, when I click on the calendar icon it opens up at 31st March 2016!

Any idea what's going on?

Thanks.

[TBriggs]

I've also just discovered that when the date field in the database is null, it now displays as today's date - and loads this into the database when you update.

This is NOT good!

Anyone got any ideas, or do I have to take off the date formatting?

Thanks.

[TBriggs]

I've had to remove the data formatting in order to prevent corruption of the database.

It's a shame I've had to sacrifice user-friendliness in this way.

[shannah]

You should never implement an xxx__pullValue() method without an accompanying xxx__pushValue() method that performs the inverse operation. This will yield unexpected results.

[TBriggs]

I wouldn't have thought that that would have caused null dates to display as today's date, because the record had only been read at that point. It also doesn't seem feasible that this would cause the data widget to interpret the date in the field into some seemingly arbitrary future date.