Hello,
after updating to the latest beta3, re-saving the calendar view, I'm getting the following warning/error:
Notice: Undefined index: field_event_date_1 in fullcalendar_plugin_style_fullcalendar->fullcalendar_parse_fields() (line 181 of /var/www/html/mysite/sites/all/modules/fullcalendar/includes/views/plugins/fullcalendar_plugin_style_fullcalendar.inc).
any idea what could be going wrong?
Thanks in advance
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | 1439026-15-undefined_index_for_date_fields.patch | 752 bytes | itangalo |
| #14 | views_error_message.JPG | 144.59 KB | Bernsch |
| #13 | Calendar-views_error.txt | 15.39 KB | Bernsch |
| #13 | ContentType_Event.JPG | 119.99 KB | Bernsch |
| #13 | ContentType_Turnsaal.JPG | 114.54 KB | Bernsch |
Comments
Comment #1
tim.plunkettSorry you're having this trouble.
Can you export your view?
Paste it into http://paste.pocoo.org and post the link here.
Comment #2
kmare commentedyes of course. Here's the link to the view export:
http://paste.pocoo.org/show/550564/
The warning is not causing a real problem as it *looks* like everything works fine. Of course I tried to build a new view getting the very same result. I also tested the fullcalendar plugin 1.5.2 and 1.5.3.
If you need anything else, don't hasitate to ask.. and thank you for all your hard work, it's really appreciated!
Comment #3
tim.plunkettAnd the error is on example.com/events_calendar? Meaning, the "Events Page" display?
Comment #4
tim.plunkettCan you open includes/views/plugins/fullcalendar_plugin_style_fullcalendar.inc in fullcalendar, go to line 178, and after
$this->display->handler->get_field_labels();putdebug($labels);? It should print out that value to the screen. The information from that would be helpful.Comment #5
kmare commentedsure, here you are
Comment #6
kmare commentedand yes it's on the "Events Page" display.. (sorry, I missed that comment before).
Thank you
Comment #7
tim.plunkettYour debug statements indicate that the view is being run twice on one page?
Once for Events Page and once for Due Dates Page. And it looks like the Events page is fine, because field_event_date_1 is clearly there. But not in the Due Dates page.
I'm not sure I understand why it's running that function twice, or why the second display's fields are showing in the debug.
Comment #8
kmare commentedhello,
after rebuilding and testing again, I noticed that the error doesn't appear as long as there's only one display on the view I create. As soon as I create a new display, the error reappears for all the displays of the view. Deleting the second display of the view leaving only the first one, makes the notice/error go away again. It doesn't really bother the functionality, as everything looks like it's working fine beside the error/warning.
Comment #9
tim.plunkettComment #10
DeNelo commentedI get it too:
And I, too, have two displays.
Comment #11
calefilm commentedI get this error when I add two date fields. I want two because I would like to use two different date formats on my view. But as was stated above it seems my pages run fine without incident (other than having to look at this after I save my view):
Comment #12
Bernsch commentedI also become this warning after I save my view:
Notice: Undefined index: field_event_date in fullcalendar_plugin_style_fullcalendar->fullcalendar_parse_fields() (line 181 of /homepages/42/d198234527/htdocs/drupal/sites/all/modules/fullcalendar/includes/views/plugins/fullcalendar_plugin_style_fullcalendar.inc).I use the FullCalendar Version 7.x-2.0-beta3 and Date Modul Version 7.x-2.5 and FullCalendar plugin 1.5.3
Comment #13
Bernsch commented@tim.plunkett:
Her is my View-export with the error message. Then you can better understand...
Pleace check it.
I think it has something to do with the filter ContentType!
Comment #14
Bernsch commentedAnd here is the View Error Message:
Comment #15
itangalo commentedThis error is caused by the view object having date fields that the FullCalendar display doesn't use.
The attached patch solves the problem.
Comment #16
Bernsch commentedThank you Itangalo!
The error message is gone! :-) --> Patch works!
edit: ups, sorry, it's RTBC
Comment #17
aspilicious commentedLets rtbc it than