My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1718: Multiple Call will be driven, when click on Next/Previous
1 person starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Aug 2013


Sign in to add a comment
 
Reported by toguptasunil, Mar 3, 2013
Hi Adam, 

This is the very nice calender open source. Thanks to share this code with us. I have facing multiple calls, when trying to fetch different data on buttons click. 

When we fetch the data from dynamic end. There is not clear the previous call automatically. and If i will trying to use "$('#calendar').fullCalendar('removeEvents').fullCalendar('removeEventSource',sources)" then it is fetch multiple calls. and these calls are increasing automatically on each and every click.

Can we have remove the previous sourcedata, once it is populated in our calendar?

Thanks
Sunil Gupta
Mar 8, 2013
#1 toguptasunil
Any update in this reported issue?
Aug 23, 2013
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #3 adamrs...@gmail.com
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

Powered by Google Project Hosting