I think I've uncovered a bug, or at least a possible issue with how things are described by CCK date fields.

I've got a CCK date field with hours/minutes (e.g. 'datetime')
When I am doing node validation and I ask for $field[0]['date_type'] I get told that I have a "date".

The problem is that when I use other modules (e.g. node_repeat, resource_conflict) that rely upon date_type, they see 'date' and immediately stop looking for hours and minutes.

In my particular case that's a problem because resource_conflict is looking for specific times of the day, but the incorrect value of $field[0]['date_type'] is causing problems.

Does this make sense? Seems like such a simple thing that I'm doubting my own ability to diagnose the bug. :-)

Please advise!

Comments

arlinsandbulte’s picture

arlinsandbulte commented

Not sure if it is any help, but ALL date formats actually store hours & minutes.
'date' stores the date in an ISO format (YYYY-MM-DDTHH:MM:SS).
'datetime' stores the date in the database's native date format (YYYY-MM-DD HH:MM:SS).
'datestamp' stores the value in the database as a Unix timestamp integer.
http://drupal.org/node/262066

I'm not sure why you are getting 'date' for the date_type of a 'datetime' field, though.
If you browse the database, is the correct type listed under 'date_type'?

Rob_Feature’s picture

Rob_Feature commented

Subscribing... (yes, I hate it when people subscribe to issues with worthless posts too...sorry...drupal.org issue bookmarks please!)

Rob_Feature’s picture

Rob_Feature commented

Bump...any other ideas on this?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Unfortunately the Drupal 6 version of the Date module is no longer supported. That said, we appreciate that you took time to work on this issue. Should this request still be relevant for Drupal 7 please feel free to reopen it. Thank you.