Closed (outdated)
Project:
FullCalendar
Version:
7.x-2.0-rc1
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Apr 2012 at 19:33 UTC
Updated:
4 Jun 2025 at 19:51 UTC
Jump to comment: Most recent
Comments
Comment #1
rtvWebServicesLibrarian commentedClosing issue, I restored from a backup copy, re-installed the module, and the problem went away.
Comment #2
jhedstromI saw this behavior on a site that had the Fences module installed. After unchecking a bunch of defaults set by that module (on the views field settings form, specifically, changing default value to customize markup), this error went away and events once again appeared on the calendar.
Comment #3
bennash commentedthanks, I also had the same error with Fences defaults applied to my Date field. jhedstrom's suggestion worked
Comment #4
kingfisher64 commentedI wish I couldn't reproduce this!
Tried the suggestion in #3. Finally after hours of tweaking I believe i've found the culprit. I have the fences module installed and am using it.
Notice: Undefined index: raw in fullcalendar_prepare_events() (line 242 of sites/all/modules/fullcalendar/theme/theme.inc).Solution
In views fullcalendar display when adding a date field under 'style settings' uncheck "use field template". By default this is checked. As soon as this is turned off the dates reappear on the calendar.
So in essence this appears to be conflicting with fences module. Could someone confirm this, so a note could be put in either the readme or on the project homepage to make others aware of this potential conflict.
Many thanks
Comment #5
kingfisher64 commentedJust installed fullcalendar again and got this error. Luckily there is a solution (that I posted!) - don't remember that, lol.
Comment #6
jsheffers commentedYep, this solution worked for me!
Comment #7
rhym006 commentedHi there! I have the same problem with open atrium...
when changing users I have this notification:
Notice : Undefined index: raw dans fullcalendar_prepare_events() (ligne 242 dans C:\wamp\www\openatrium\profiles\openatrium\modules\contrib\fullcalendar\theme\theme.inc).
Any suggestions?
ps: I have already try the solutions above but dont work for me,
thank you
Comment #8
mchris82 commentedI was receiving this error while using FullCalendar with Organic Groups. I narrowed it down to an issue of FullCalendar wanting to load nodes that the logged in user didn't have permission to access due to the permissions set in Organic Groups. I was able to resolve the issue by adding the Relationship "OG membership: OG membership from Node" and adding a Contextual Filter of "User: Group Membership" using the aforementioned Relationship. This allows FullCalendar to load only nodes that the logged in user has permission to view via Organic Groups.
I thought I'd share in case someone experiences the same issue and stumbles upon this post while searching for a solution.
Comment #9
csc4 commentedI had this too - also have Fences module #1516850-4: Getting error message "Undefined index: raw in fullcalendar_prepare_events()" fixed it - thanks @kingfisher64
Comment #10
hunlaprovo commentedYES!!!!!!!THANKS
Notice: Undefined index: raw in fullcalendar_prepare_events() (line 242 of sites/all/modules/fullcalendar/theme/theme.inc).
Solution
In views fullcalendar display when adding a date field under 'style settings' uncheck "use field template". By default this is checked. As soon as this is turned off the dates reappear on the calendar.
So in essence this appears to be conflicting with fences module. Could someone confirm this, so a note could be put in either the readme or on the project homepage to make others aware of this potential conflict.
Comment #11
tenken commentedThe posted solution with Fences installed fixed my problem as well!
Comment #12
dcam commentedI've volunteered to help clean up the FullCalendar issue queue. As part of that effort I'm closing issues open for unsupported versions of the module as "Closed (outdated)". That includes any Drupal 7-compatible versions because no active maintainer is supporting them.
If this issue is still relevant for version 3.x of FullCalendar, then feel free to re-open it and update the issue version number.