| Issue 1199: | parsing ISO8601 Date does not work | |
| 3 people starred this issue and may be notified of changes. | Back to list |
I'm getting a valid ISO8601 back from a JSON string, but it's not displayed correct in the fullcalendar.
creating date format with JAVA formatter:
SimpleDateFormat df = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.sZ")
df.setTimeZone(TimeZone.getTimeZone("Europe/Berlin"))
config of calendar:
ignoreTimezone: false,
timeFormat=H:mm{ - H:mm}
JSON-Result: {"id":1,"title":"Date with Chuck Norris","start":"2011-12-02T09:30:00.0+0100","end":"2011-12-02T10:30:00.0+0100","color":"","allDay":false}
- take start-time 9:30 is the DB value but the +0100 is not recognized, so displayed time is 9:30, but that's wrong, must be 10:30. same for end date (tried this WITHOUT eventRender-functionality!)
...
(to get sure that it will be parsed correctly, I did another thing on config:)
eventRender: function(event, element) {
event.start = $.fullCalendar.parseDate(event.start); //tried also $.fullCalendar.parseISO8601()
event.end = $.fullCalendar.parseDate(event.end); //tried also $.fullCalendar.parseISO8601()
}
- tried with onEventRender and parseDate() but nothing happens
- tried with onEventRender and parseISO8601() -> but nothing happens and JS-Error (see attachement: js-error.png)
using jquery 1.6.3 and latest fullcalendar 1.5.2
Feb 19, 2013
Sorry I forgot to add the dates that I wanted to parse: start = Tue Feb 19 2013 08:15:00 GMT+0200 (SAST) end = Tue Feb 19 2013 16:30:00 GMT+0200 (SAST)
Aug 14, 2013
(No comment was entered for this change.)
Status:
New-Reproducing
Aug 14, 2013
(No comment was entered for this change.)
Status:
ReproTemp
Aug 25, 2013
This message is being bulk-sent to a number of issues, both [very] old and new.
I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:
http://arshaw.com/fullcalendar/wiki/Report-a-Bug/
Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.
If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.
I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.
Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status:
Invalid
Labels: Type-Bug |
|
| ► Sign in to add a comment |
I have the some problem, however this is just for eventDrop: eventDrop: function(event,dayDelta,minuteDelta,allDay,revertFunc) { var start = $.fullCalendar.parseISO8601(event.start, false); var end = $.fullCalendar.parseISO8601(event.end, false); alert( event.id + event.title + " was moved " + dayDelta + " days and " + minuteDelta + " minutes." + start + end ); if (allDay) { alert("Event is now all-day"); }else{ alert("Event has a time-of-day"); } if (!confirm("Are you sure about this change?")) { revertFunc(); } }