| Issue 2017: | Event destroy callback on event removal | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Either have the event destroy callback get called on removal of events or make a new one that is called whenever an event is removed from the calendar. It should pass the event element just like event destroy. I have a stack overflow of me trying to do something/thinking it was a bug that it didn't get called here: http://stackoverflow.com/questions/19237815/fullcalendar-eventdestroy-is-never-called/19280757?iemail=1&noredirect=1#19280757 "Looking a bit at the code, it looks like the eventDestroy callback is only called when the fullcalendar view is destroyed. Never when you remove individual events. So that would be a current limitation of this lib." But after the explanation I realize it is more of a feature at this point.
Jun 11, 2014
(No comment was entered for this change.)
Status:
Accepted
Jul 22, 2014
(No comment was entered for this change.)
Labels:
milestone-skeleton
Jul 23, 2014
This is fixed in v2.1 (beta) http://blog.arshaw.com/1/post/2014/07/fullcalendar-210-beta.html I would really appreciate if you could verify this. Thanks a lot!
Aug 14, 2014
(No comment was entered for this change.)
Status:
Implemented
Aug 26, 2014
This issue has been resolved with the official release of v2.1.0: http://blog.arshaw.com/1/post/2014/08/fullcalendar-210-released.html Please post any follow-up bug reports or feature requests as separate issues. Thanks.
Status:
Released
|
|
| ► Sign in to add a comment |
Labels: Type-Bug