Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This patch is a starting point for making a usable UI for the date types. Loads of problems still exist however.
Known issues:
- Day seems to be offset by -1 after going through format_date
- Time zone support is nonexistant
- Multiple values support is nonexistant
- Dependency on timestamp conflicts with the underlying ISO 8601 storage format
This patch is looking for developers to adopt it and work on it... I don't expect to be able to follow up on it.
Comment | File | Size | Author |
---|---|---|---|
#2 | cck_date.png | 2.76 KB | robertDouglass |
#1 | cck_date.patch | 17.17 KB | robertDouglass |
Comments
Comment #1
robertDouglass CreditAttribution: robertDouglass commentedOf course I forgot the patch.
Comment #2
robertDouglass CreditAttribution: robertDouglass commentedAnd a screenshot.
Comment #3
RayZ CreditAttribution: RayZ commentedI'm not sure whether to mark this as a duplicate or not, so I'll leave it, but just in case you missed it, you should also be aware of the patch by KarenS in http://drupal.org/node/50062. She did some very nice work: multiple widgets, including an optional jscalendar, etc. Unfortunately, the patches in #19 and #25 no longer apply and there has been no recent feedback from JonBob (has anyone seen him recently?).
Apparently, from the discussion at http://groups.drupal.org/node/731, the issue of what format to use for the date field in the database is still rather unsettled. Seems that's the first thing to nail down.
Comment #4
robertDouglass CreditAttribution: robertDouglass commentedLet's leave the status as is, for now. Marking as duplicate is as good as forgotten, and there are a couple juicy bits that could be harvested from my work in the worst case.
Comment #5
KarenS CreditAttribution: KarenS commentedSince there is now a separate project for the date module (http://www.drupal.org/project/date) I'm going to go ahead and close this issue.
Comment #6
(not verified) CreditAttribution: commented