All Date module replacement patterns use 0:00 Jan. 1, 2007

Just now, I tried using [field_date-timestamp] and [field_date-to-timestamp]. In both cases, the resulting date code is 1167609600, which is Mon, 01 Jan 2007 00:00:00 GMT.

I also tried a couple of additional replacement patterns, and it appears that no matter what I use, the returned value will be based off 1167609600.

Wow, something is really messed up. I just created a Date field type (in addition to the previously-created Datestamp field type), and it too appears to return all values based off timestamp 1167609600.

I may have found the problem. token_cck.inc (line 263) calls date_show_date($date, 'Y'). That leads to date.inc (line 487), which has date_format_date($format_string, date_fuzzy_stamp($date->local)). The 2nd parameter of that function leads to execution of the following date.inc code (lines 531-545):

/**
 *  Create a valid timestamp that can be used for date formatting
 *  even if only partial date info is available,
 *  i.e. for an iso date with month and year only
 */
function date_fuzzy_stamp($datetype) {
  if ($datetype->timestamp) {
    return $datetype->timestamp;
  }
  else {
    return date_gmmktime(array(
      'year'   =>  ($datetype->parts['year']    ? $datetype->parts['year']    : date('Y')),
      'mon'    =>  ($datetype->parts['mon']     ? $datetype->parts['mon']     : 1),
      'mday'   =>  ($datetype->parts['mday']    ? $datetype->parts['mday']    : 1),
      'hours'   => ($datetype->parts['hours']   ? $datetype->parts['hours']   : 0),
      'minutes' => ($datetype->parts['minutes'] ? $datetype->parts['minutes'] : 0),
      'seconds' => ($datetype->parts['seconds'] ? $datetype->parts['seconds'] : 0),
      ));
  }
}

It's uncanny how the date stamp that is used ends up having the exact same values as the else clause.

Note that the date.inc line numbers are from the Aug. 8 version of 5.x-DEV.

Well, I looked more at the code, and it looks like the default date/time is only used in its entirety if the date object passed to date_fuzzy_stamp is empty?

Working backwards, it looks like this may happen if token's date_token_values's 2nd parameter ($object) is null? But grepping my entire Drupal install and searching the entire database, I cannot find any instance of use of the date_token_values function. So I am confused.

I just created a new Date field and accepted all defaults (except for the one setting I had to change due to this bug), and I still get the same behavior.

(Yes, I changed the replacement patterns to use the new date field I just created.)

(Shortening title.)

I have a gut feeling this might be a problem with the Token module. Switching to Token.

So you're saying this happens with modules other than Date?

I think you're right. I've marked this one as duplicate.