Issue 1741: Object [object Object] has no method 'fullCalendar' ONLY IN CHROME
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by Zachary....@gmail.com, Mar 15, 2013
Please include a demonstration of your bug (URL or ZIP attachment), as well as a detailed description.

In firefox, I am able to drag and drop events on the calendar without any problem. I can also modify the names of the events through a custom dialog (also only in firefox) using 'renderEvent' (click once on an event to open the dialog).

However, in the chrome browser, when I try to drop a draggable event onto the calendar, I get the error "Uncaught TypeError: Object [object Object] has no method 'fullCalendar'". 

Not only this, but it seems that chrome also can't get the information stored in the DOM element from $.data(...), giving the error "Uncaught TypeError: Cannot read property 'title' of undefined" (I set an alert to appear that gives me the event title when I drop it onto the calendar, for testing purposes), whereas firefox works just fine.

Here is the URL to the page: http://cyclingtoendms.com/GRAD/sched.php
Mar 15, 2013
#1 Zachary....@gmail.com
UPDATE: the drag and drop functionality works perfectly in chrome IFF the page is run in the browser, NOT online. 

I tried the demo page from the fullcalendar website for this as well. The same problem occurs (as described in the original report). The problem is resolved if the page is not opened online (i.e. tested in the browser). However, this obviously isn't practical for a website.
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-Defect Type-Bug