My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1393: Improper end time in fetching window of events, thus missing last 6 hours of events.
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 boulderc...@gmail.com, May 4, 2012
On the non-editable display of a Google Calendar used for scheduling purposes, the events in the last 6 hours of a display window would not show.  In the following URL we have an event that happens every 1st and 3rd Saturdays of the month from 7pm to midnight.  It does not display:
http://www.avalonevents.org/fullcalendar-1.5.2/VACcalendars/Pearl-Street-StudioB.html
If you go to month view and then back you will see the event displayed.  So starting from a refreshed page you will not see "Pearl Street Swing and Blues" from 7pm to 12 on weeks starting Apr 29, May 13, May 27, Jun 10 etc.  But if you view the month and then go back, you will see the event display.  Also in month view for June you will not see the event displayed on July 7.  Advance to July and you will see the July 7 event.

Digging through the code we played with timezone stuff (we are in Devner/America TZ so is the Google calendar. We added "ignoreTimezone: false" and "currentTimezone: 'America/Denver'" to be sure.  These did not help.  We then looked at an modified "fullcalendar.js" and changed 
FROM:
function fetchEvents(start, end) {
		rangeStart = start;
		rangeEnd = end;
TO:
function fetchEvents(start, end) {
		rangeStart = start;
		rangeEnd = addDays(end, 1);
Thus adding one day to the fetched data.  This worked as a work-around.  We think that the UTC versus Denver TZ may be the reason for the missing 6 hours.  But we did not figure out where this happened.

Our work-around is at:
http://www.avalonevents.org/fullcalendar-1.5.2/VACcalendars/Pearl-Street-Studio.html
Using a modified "fullcalendarB.js" 

I hope this makes sense.  Feel free to contact me for further questions.  I greatly appreciate your work and FullCalendar.

Thank you
Chuck Palmer
303-718-4792
boulderchuck@gmail.com
Aug 18, 2013
Project Member #1 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #2 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