| Issue 1076: | Unix timestamp ignoreTimezone support | |
| 7 people starred this issue and may be notified of changes. | Back to list |
Scenario: fullcalendar version 1.5.1 ignoreTimezone is set to true. my local time zone is set to GMT+2 event start date is a unix time stamp: 1312988400 (10/08/2011 15:00:00 GMT) event end date is a unix time stamp: 1312999200 (10/08/2011 18:00:00 GMT) the event is shown from 17:00 to 20:00 no matter the setting of ignoreTimezone variable. I've changed parseDate function to obtain the desidered behavior (with ignoreTimezone true the event must be rendered from 15:00 to 18:00 ). in the attachment my modified version of parseDate function and the git patch for date_util.js from github (from 1.5.1 tag).
Feb 12, 2013
Thank you for your solutuion, this bug still present in Fullcalendar.
Aug 13, 2013
(No comment was entered for this change.)
Summary:
Unix timestamp ignoreTimezone support
(was: unix timestamp ignoreTimezone support)
Labels: Type-BehaviorMod
Aug 14, 2013
(No comment was entered for this change.)
Labels:
-Type-BehaviorMod Type-Behavior
Sep 1, 2013
(No comment was entered for this change.)
Labels:
milestone-date
May 25, 2014
ignoreTimezone is no longer present in v2. timezone support has been completely rethought. http://arshaw.com/fullcalendar/wiki/Upgrading-to-2/ will be released soon
Status:
Implemented
Jun 2, 2014
version 2 has been released with this change. http://blog.arshaw.com/1/post/2014/06/fullcalendar-2-released.html
Status:
Released
|
|
| ► Sign in to add a comment |
Status: Accepted