My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1453: Removing event source in viewDisplay changing from basicDay to month/basicWeek leaves events displayed
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 apilacho...@gmail.com, Jun 28, 2012
  I am using jQuery 1.7.2, jQuery UI 1.8.18, json2.js, date.js and fullcalendar 1.5.3 (added in that order).  I have modified the fullcalendar ajax function data: JSON.stringify(data) and success callback events = (typeof events.d) == 'string' ? eval('(' + events.d + ')') : events.d || [] in order to retrieve data directly from an asmx service.  Our environment is mixed IE7 and IE8.
  I have set 3 variables to hold the event source objects: holiday, overview, and day.  Overview selects aggregated totals because one day can have up to 30 events.  Day selects each event individually.  Holiday selects from a table of holidays to be displayed at all times.  Fullcalendar is initialized with month and basicWeek in the header.  Month and basicWeek display holiday and overview event sources.  BasicDay displays holiday and day event sources.
  On dayClick, I call changeView, basicDay method and gotoDate passing the selected date.  In the viewDisplay callback, I check a variable holding the last view that was used.  If the view has changed from month/basicWeek to basicDay (by clicking the day), I call removeEventSource, day and addEventSource, overview.  I have seen no issues with this part.  If the view has changed from basicDay to month/basicWeek (by clicking Month or Week button in the header), I call removeEventSource, overview and addEventSource, day.  The one specific way this breaks as described in the summary is when viewing month (i.e. July 2012) and a day from the next month is selected to view the day (i.e. August 2 2012), when going back to the month or week view (which displays the next month from what was originally displayed, i.e. August 2012 or Jul 30 — Aug 3 2012), both the day and overview event sources are displayed.  If the month/week is refreshed navigating next/previous, only the overview event source is displayed (which is what should be displayed).  There are other cases where I can make this happen but are harder to describe.
Jun 29, 2012
#2 apilacho...@gmail.com
  So the issue appears to be the cache vs eventSources (which may have to do with the start and end values being posted back).
  I found a solution that only works if gotoDate is called before changeView, it still breaks the other way around.  Just changing gotoDate to be before changeView, the overview event source was being duplicated instead of showing day and overview on the return to the month view.  I moved the removeEventSource, overview call from viewDisplay up to the click events just before I call gotoDate.  I really cannot say why the order of operations is such an issue but so far I am not experiencing the duplication any more.
Fixed code: http://pastebin.com/9pnhXsmt
Jul 3, 2012
#3 apilacho...@gmail.com
  One more situation I do not believe is able to be resolved without modifying fullcalendar.  When viewing a month (i.e. July 2012) and click a day within the same month (i.e. July 31, 2012) to change to basicDay, then navigate to the next day (Aug 1, 2012), then click the month button, the day event source is displayed until the calendar is navigated next/previous.  This also happens when viewing a month (July 2012), clicking the first day of the next month (Aug 1), navigating to the previous day (July 31), then clicking the month button.  This does not happen if the week button is clicked instead of the month button.
Aug 18, 2013
Project Member #4 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #5 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-Defect Type-Bug
Sign in to add a comment

Powered by Google Project Hosting