CiviCRM Community Forums (archive)

If a custom date is set at the format YYYY, advanced searches automatically default to today.  In other words, if I do a search on a custom date field that is set as YYYY, I can select 2009 (and of course the month/day b/c the pop-up requires a day), and the search uses "March 8, 2010, time..."  This is true for "search by ranges" as well, in which case both searched dates are today, about a minute apart.

I have confirmed this on the demo.drupal site.  Do a search for a contact using the "Marriage Date" field, which I have set to YYYY.  It will default to the day you select the search, not the day you actually selected.

An additional problem I am having, though I am not sure it is related and I have not confirmed this on the site, is that when a contact updates a profile with this custom date in it, the date defaults to the day they updated the profile, even if they did not enter a date.  If they had a date in the field, it updates it automatically.  The settings on the field do not require a default date.

So, something appears to be very wrong with the YYYY default setting.  Any ideas?  I kind of need that field!  This was not a problem on 2.2.8, and I don't recall it on 3.0.x, but I am seeing it on 3.1.1 as well as my test version of 3.1.3.

Thanks,
Maria

I've run into some issue with this as well. All the date fields are stored as a full date type value (yyyy-mm-dd hh:mm) -- which is fine, except the interface needs to handle the different display formats in different ways. With the current structure, the yyyy format is pretty much unusable.