Issue 1230: Calendar Events do not Render in IE9.0.8 FF 3.6.25 using jQuery 1.6.2
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by getsmart...@gmail.com, Jan 3, 2012
Hi all,

Thank you for a very useful and wonderful piece of Calendar software.

I installed the code using jQuery 1.3.2 and it worked fine on my
Asp.Net test website.
When I moved the page to my development website the Events did NOT render when using jQuery 1.6.2.

I'm not good with javascript so I didn't investigate further to compare the differences in behaviour between versions of jQuery.

Below shows the asp.net page usng 1.3.2 which works.
Note: their was a javascript error fix when clicking on events
fixed with the newer version of the  qtip js.

<head runat="server">
    <title></title>
    <link href="css/cupertino/jquery-ui-1.7.3.custom.css" rel="stylesheet" type="text/css" />
    <link href="fullcalendar/fullcalendar.css" rel="stylesheet" type="text/css" />

    <script src="jquery/jquery-1.3.2.min.js" type="text/javascript"></script>

    <script src="jquery/jquery-ui-1.7.3.custom.min.js" type="text/javascript"></script>

<%--    <script src="jquery/jquery.qtip-1.0.0-rc3.min.js" type="text/javascript"></script>--%>
    <script src="jquery/jquery.qtip-1.0.js" type="text/javascript"></script>

    <script src="fullcalendar/fullcalendar.min.js" type="text/javascript"></script>

    <script src="scripts/calendarscript.js" type="text/javascript"></script>
    
    <script src="jquery/jquery-ui-timepicker-addon-0.6.2.min.js" type="text/javascript"></script>

Happy New Year 2012, LA Guy
Aug 14, 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