I'm using the following:
Drupal 6.6
CCK 6.x.2.1
Date 6.x.2.0-rc4
Calendar 6.x.2.0-rc4
I've created a content type called Events which has a datetime field called "time". The time field is set to have the drop-down calendar with repeats. I then created an Event that begins 11/1/2008 7:20 pm - 8:30 pm which repeats every Saturday through 12/31/2015. I know that works because I can look in the appropriate database table, and the appropriate dates and times are all there. I also created a nonrepeating event for 11/27/2008 (Thanksgiving).
Then I created a view called upcoming_events which is supposed to show the next five events (by date) that are coming up. The (non-repeating) Thanksgiving date shows up appropriately in the view, but all four other (repeating) dates in the view show a date of 11/1/2008, instead of the four sequential Saturdays after the current date. I'm certain that these four events, despite showing the 11/1/2008 date, actually are referring to correct sequential events because in the Calendar view from the same content type, it correctly places the events in the sequential Saturdays while also showing a date of 11/1/2008. (For instance, in the Calendar block for 11/15/2008, it shows an event with a date of 11/1/2008.)
Hopefully, that's not too confusing. I'm attaching screenshots that I hope will clarify.
I've tried every possible configuration alternative that I can think of, and none of them made any difference in this behavior.
| Comment | File | Size | Author |
|---|---|---|---|
| Edit Upcoming Events.png | 81.75 KB | LarryTX | |
| Time Field.png | 38.14 KB | LarryTX | |
| Event Content Type.png | 50.4 KB | LarryTX | |
| Event Repeats.png | 50.76 KB | LarryTX |
Comments
Comment #1
yched commentedDate.module handles it's own Views integration, so it should probably be filed there.
Assuming you're using Date RC4, please change version if needed
Comment #2
LarryTX commentedThanks. I wasn't sure which forum would be appropriate.
Comment #3
karens commentedThere were other issues about this already. It should be fixed in -dev and the fix will be in the next release.