Issue 2194: updateEvent should accept change in end date and all-day
Status:  Released
Owner: ----
Closed:  Dec 2014
Reported by rrmg...@gmail.com, Jun 26, 2014
I am currently using fullcalendar 2.0.2 and I've noticed a bug with the method updateEvent.  Apparently anytime I externally (outside of the calendar widget) update the start/end date of an event by using the updateEvent method it removes the end date.  I've created an example on jsFiddle: http://jsfiddle.net/fjavier/LDNKR/.

Instructions to reproduce:
1. click on an existing event.  The event id, start, and end date will be populated in the form above the calendar.

2. change either of the dates and click save.

Expected Results:
event should reflect new date range.

Actual Results:
event ends up only on the start date.  If one outputs the event object the end date is null.

Jun 26, 2014
Project Member #1 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Reproducing
Labels: Type-Bug
Aug 13, 2014
#2 rrmg...@gmail.com
any estimate as to when this bug will get looked at?
Nov 12, 2014
#4 ManuelMo...@gmail.com
I think it's a problem on the parsing. Using moment() works fine
http://plnkr.co/edit/og2Qbo?p=preview
Nov 25, 2014
Project Member #5 adamrs...@gmail.com
I can confirm this. The problem here is that anything coming from the vanilla `moment()` constructor will always produce a moment that has a time. See http://fullcalendar.io/docs/utilities/Moment/#ambiguously-timed

The workaround is to use just the raw string, or to use $.fullCalendar.moment(), without the second format string argument.

Will keep this ticket around so I can fix the underlying bug at some point.

NOTES TO SELF:

When the event is assigned new dates that have times, the event will suddenly become "timed" (IE, not all-day anymore). This is desired behavior.

However, the bug here is that when re-assigning the start/end time of an all-day event to be timed dates, the end time is not processed. It is set to null instead. This does not affect you but might affect others.

Other notes to self:
- clearing the end date should only happen for DnD, not through programmatically updating an event 
- $.fullCalendar.moment() should work with a format string second arg
Summary: updateEvent should accept change in end date and all-day (was: calling updateEvent removes the end date from event object.)
Status: Accepted
Nov 25, 2014
Project Member #6 adamrs...@gmail.com
 Issue 2199  has been merged into this issue.
Dec 29, 2014
Project Member #7 adamrs...@gmail.com
v2.2.4/2.2.5 has just been released and updateEvent's behavior is much more intuitive now. This bug should be solved.
Status: Released