Closed (fixed)
Project:
Date
Version:
5.x-1.5
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
13 Jun 2007 at 19:49 UTC
Updated:
31 Oct 2007 at 13:01 UTC
Hello,
Ran into two issues using CCK 'date' field and views date arguments.
Issue 1: I have a CCK type for 'Alumni' that has a 'date' text field for the year student graduated. I then have a view that loads alumni all by default as teasers and is supposed to accept the date range arguments as outlined in http://drupal.org/node/92188
When I pass the year as '/alumni/2006--2007' I should get all alumni for 2006 and 2007. Problem is I get only 2007. I have to pass '/alumni/2005--2007' in order to get the 2006 alumni. Any ideas why?
Issue 2: Second issue is passing a single year like say '/alumni/2006' returns nothing. Not sure why.. documentation seems to say passing a single year value is acceptable?? Am I missing something in documentation or have I hit a bug?
Any help would be greatly appreciated as this is the last element of a project.
many thanks
Comments
Comment #1
merlinofchaos commentedThis issue is either date.module or daterange.module -- I'd reassign but since I'm not sure which you really mean, I will let you do that.
Comment #2
jeffrey.dalton commentedHello,
Ran into two issues using CCK 'date' field and views date arguments.
Issue 1: I have a CCK type for 'Alumni' that has a 'date' text field for the year student graduated. I then have a view that loads alumni all by default as teasers and is supposed to accept the date range arguments as outlined in http://drupal.org/node/92188
When I pass the year as '/alumni/2006--2007' I should get all alumni for 2006 and 2007. Problem is I get only 2007. I have to pass '/alumni/2005--2007' in order to get the 2006 alumni. Any ideas why?
Issue 2: Second issue is passing a single year like say '/alumni/2006' returns nothing. Not sure why.. documentation seems to say passing a single year value is acceptable?? Am I missing something in documentation or have I hit a bug?
Any help would be greatly appreciated as this is the last element of a project.
many thanks
Comment #3
chadchandler commentedI'm having a very similar problem using Date & CCK & Views.
I hate a CCK Date Field called " Expiration", with the argument being the CCK Date Field.
Pretend you submit a coupon that expires August 10, 2007 .... it's being submitted to August 11, 2007. Any ideas?
Comment #4
karens commentedI can't replicate this now, but I'm assuming it would have been fixed by a recent commit to fix up the summary handling. You can reopen if it is still an issue in the very latest code.
Comment #5
(not verified) commented