Issue 317: Odd Interaction Between refetchEvents and View Changes
Status:  Duplicate
Merged:  issue 240
Owner: ----
Closed:  Feb 2010
Reported by katie.e....@gmail.com, Feb 2, 2010
In an application where fullcalendar is used to display events (passed as
JSON) from a back-end DB and a form adds those events to the calendar,
editing is done via either the form, drag and drop, or resize.  Events can
repeat (and have the same IDs as the calendar requires).  On save of an
event via the form, drag and drop, or resize, events are refetched (because
otherwise rendering each individual event of a repeating chain runs into
the slow rendering of Issues 178 big time).

When a month view has been rendered, then the user switches to the week
agenda view - which is where the user can, say, edit an event's start time
by dragging and dropping - and the user changes an event in that week, then
switches back to the month view, odd behavior happens.  fullcalendar.js's
fetchEvent method isn't called.  Instead, because the view's events are
marked as dirty, only the current week's worth of events (which were pulled
via refetchEvents) is called.  If the refetchEvents hadn't happened, this
would make perfect sense.  However, that refetchEvents in between causes an
odd interaction where the events array is changed but the month view
doesn't know it.

Is there some way in the API to address this?
Feb 3, 2010
#2 katie.e....@gmail.com
After further investigation, believe this issue should be closed as a duplicate and
merged into  Issue 240 .
Feb 4, 2010
#3 bibendus...@gmail.com
I made a temporary fix for fullcalendar v1.4.4 to force events refetching while
changing view or day.

Take a look here:
https://code.google.com/p/fullcalendar/issues/detail?id=323&sort=-id&colspec=ID%20Type%20Status%20Milestone%20Summary%20Stars
Feb 5, 2010
Project Member #4 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Duplicate
Mergedinto: 240