Issue 1668: prior year failure
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by i...@iewilson.com, Jan 7, 2013
Error is that any view with prior year fails to show any events (this year or prior).

Example:
Events in JSON feed on 01/03/13 and 01/07/13

month view January - blank
week view 12/30 to 01/05  - blank
week view 01/06 to 01/12  - shows 01/07 event
day view 01/03 - shows 01/03 event
day view 01/07 - shows 01/07 event

So...any view that contains a piece of December fails to show any events but "full January" events display properly.  JSON feeding it must be correct otherwise all views would fail (right?).  

A full 2012 view (e.g. November 2012) also fails.

If I change my system date to a 2012 date I get exact same behavior except reversed with 2013 dates failing.

Please note there has been code added looking for a "refresh" flag in JSON to refresh the html page containing the calendar. This does not appear to affect the calendar functionality but it must be if no one else having this issue.

I'd like to know (please) - 

Is anyone else having this problem?

Does the description above make anyone think of an obvious place I should look?

Thank You!

Jan 8, 2013
#1 nbuan...@gmail.com
I'm having somewhat a similar problem but I'm not using JSON but events in a JS array. All events for 2012 are showing up ok, but non for 2013
Jan 8, 2013
#2 i...@iewilson.com
I was using version 1.5.3. I downloaded 1.5.4 and seems to work ok now.  Also added back the changes I mentioned above(mainly a page refresh capability) and mostly works as planned.  I think the 1.5.4 download fixed it but it could be when I finally tweak the additions I made I'll end up where I was.  Are you using 1.5.4?
Aug 21, 2013
Project Member #3 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #4 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