| Issue 1761: | Uncaught TypeError: Cannot read property 'eventSources' of undefined | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Hi,
I just added fullcalendar 1.6 to my rails project.
Verified using:
Jquery-UI-1.10.2
jquery-1.9.1
Simple Coffee script:
jQuery ->
$('#calendar').fullCalendar()
View Form:
<div id='calendar'></div>
Problem:
Uncaught TypeError: Cannot read property 'eventSources' of undefined fullcalendar.js line 148
Was able to 'workaround' by just initializing the variable
jQuery ->
$('#calendar').fullCalendar ->
eventSources
Not a big deal, just hurts out of the box experience. I am going to use eventSources for json feed anyway; I was just was expecting to see the calendar before moving forward.
Hope helps someone,
Bryan
Jun 9, 2013
#1
sarapop...@gmail.com
Jun 9, 2013
Did you run into the problem? Are you using fullcalendar with rails? What versions? So far I have only been one to complain. I added the above to my correlating controller coffee script file; app/assets/javascripts/home.js.coffee Bryan
Jun 9, 2013
Hi again,
I actually ran into the problem (Same error message), meanwhile no calendar never showed up.... with the following environment environment :ruby 1.9.3p429, rails 3.2.13, Jquery-UI-1.10.2,jquery-1.9.1
I'm basically trying to set-up/run a "demo" site using static pages....
Here is the content of file static_pages.js.coffee
$(document).ready ->
calendar = $('#calendar').fullCalendar(
)
I figured out (failed) that I should implement your 'workaround' in this file, but I'm not sure how or it should practically be implemented... in this static_pages.js.coffee file? Or how/where else?
If you know of any "tutoria/guidelinesl" that would allow me to achieve such a static page site, tell me, I might as well go for it...
The only one that I could find is unfortunately published by a French guy (http://www.corgumolax.fr/2012/12/fullcalendar-et-ruby-on-rails/#comment-1236), which may a familiar language to you... Some guys also faced the issue, obviously.
Thanks for your time.
Chris
Jun 19, 2013
I ran into this error as well, but was able to correct it by just passing an empty object: $('#calendar').fullCalendar({});
Aug 15, 2013
(No comment was entered for this change.)
Status:
ReproTemp
Aug 25, 2013
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 |