Closed (fixed)
Project:
Timeline
Version:
6.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
28 Jul 2009 at 06:38 UTC
Updated:
10 Sep 2009 at 06:40 UTC
Jump to comment: Most recent file
Historical dates no longer function as they once did for timeline views. They show up incorrectly on the timeline, stacked on top of each other.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | timeline.txt | 4.55 KB | bomarmonk |
Comments
Comment #1
xamanu commentedWhat kind of cck date fields are you using? Date, Datetime or Datestamp? Are you using From and To dates? Could you please specify. For me older dates working okay. So need more information in order to be able to rebuild this error.
Comment #2
bomarmonk commentedI am using a date field with "from" and "to" dates. This field is in a field group called "life span." In my view, I entered the from and to dates as separate fields. Thank you for the help.
Comment #3
bomarmonk commentedYou can check out what is happening at http://cmccully.com/authors. Also, I'll attach a text file of my exported view. Thanks for your help.
Comment #4
bomarmonk commentedBasically, it looks like the "from dates" are somehow all the same in the timeline view, even though the date field has a completely different date entered. Any help?
Comment #5
bomarmonk commentedWell, it looks like all of the timeline nodes are pulling up the same start date of 1901, which is not one of the dates entered in for the nodes themselves. Arg!
Comment #6
wayne57 commentedI have the exact same behavior. All dates stacked on 1901?
I am sure I managed to to get them to display in an earlier version. Trying to build a historic timeline going back to the 1500s and can't get it to work. Is there a solution to this?
Comment #7
bomarmonk commentedAnother update: this problem still exists for me after completely recreating the content type, adding new date fields, and completely rebuilding my timeline view. I thought it might have been bad date info in the old content type, but apparently not. Even the new content types end up stacked on 1901. It seems that the length of the timeline entry is perhaps correctly based on the date fields provided to the timeline view, but the actual starting point for the timeline node is always placed with the bad 1901 date. Where is 1901 coming from? Maybe it's Y2k :)
Also, I tried my new timeline view with completely separate fields for the "from" and "to" dates on the timeline (whereas my old view used a single date field with a "to" date). Either way, I get the same results.
Comment #8
wayne57 commentedI have also tried this with the Date and Datetime, but get the same problem.
Comment #9
xamanu commentedThank you for the information. I can rebuild this error and jumping into it tomorrow.
Comment #10
xamanu commentedThis was caused because of an unexpected behavior of the format_date() function. I switched internally from Gregorian (timeline's native date format) to ISO date formats in order to avoid running into this problem. So this has been fixed in the 6.x-2.0-beta2 version (Commit #256554.). Please help testing.
Comment #11
bomarmonk commentedSo far the new version seems to be working. This appears to be fixed.