| Issue 1014: | End date is null if on same day | |
| 6 people starred this issue and may be notified of changes. | Back to list |
I havent' debugged throughly through the code but I am loading events from json which works fine however the end dates are all null when received by click event..
Jul 13, 2011
Project Member
#1
adamrs...@gmail.com
Status:
Reproducing
Nov 1, 2012
This happens to me if the start and end date are the same, and formatted like this: start: '2012-08-18',end: '2012-08-18' I'm providing them through an event source function. allDay doesn't seem to make a difference. Apparently having the start and end date be the exact same makes the end date null. I'm working around it in my function by adding a minute if the times are the same.
Apr 22, 2013
I have the same problem, Adam, could you please fix that? When the start date and the end date are the same, the end date will be null in EventClick event.
Jun 14, 2013
Same here, to reproduce (this is one way, there might be more): - Set fetch events using json feed - Create an event in month view - Drag and drop it on another day: event.end will be null
Jun 14, 2013
Also im not sure if this is related, but i get an error on line 2724 "getDaySegmentContainer(...) is undefined"
My calendar is inside a jQuery UI dialog which is hidden at page start (by a CSS rule)
When i show the jQuery UI dialog using $(selector).dialog("open") the calendar appears to be in month view but there is no grid at all. As if something went wrong in the display during page load. Once i click on Today or actually any other button, the calendar appears fine again
Keep up the good work :) if you need any help i will be glad to aid you fix this issue
Aug 13, 2013
the problem is not with the onclick, it is with the way FullCalendar normalizes event data (meaning, in other places where you receive event data, you will see the same behavior). https://github.com/arshaw/fullcalendar/blob/master/src/EventManager.js#L366 If the event's end date is the same as the start date, FullCalendar considers it to be 1-day in duration (with a blank assumed end time), so it is one-in-the-same. It prefers to store less data than more. If it were the other way around, I bet other people would find that undesirable, so I will keep it the way it is for now. But you could simply do this as a workaround: eventClick: function(event) { var start = event.start; var end = event.end || start; }
Summary:
End date is null if on same day
(was: End date is null in clickevent)
Status: WontFix Labels: Type-BehaviorMod
Aug 18, 2013
(No comment was entered for this change.)
Status:
Duplicate
Mergedinto: 799
Jul 2, 2015
I think this issue should be fixed as lots of people are facing same issue. It's very difficult to check every where that end date is same as start date or end date is null. |
|
| ► Sign in to add a comment |