Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I realize this is a problem with 4.7 - it is also a problem with Final release 5.0, updated CCK 1.2.2.2, views 1.2.2.3, calendar 5.x-1.1 dated 1/12/07.
I use a node reference in a content type that is used in another content type. I then create a calendar view. When viewing the calendar I get the error multiple times for each node in the second content type that references the first content type:
warning: Invalid argument supplied for foreach() in /home/harriska/public_html/drup/modules/cck/content_views.inc on line 149.
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedComment #2
harriska2 CreditAttribution: harriska2 commentedHi Merlin - this is most definitely an issue with the Calendar views plug in module. When not using the calendar type view and just creating a view using tables, it works fine.
Here is an example with tables:
http://teachernotes.org/drup/menu_list
Here is the same data with calendar type layout in the view:
http://teachernotes.org/drup/menu_calendar/2007/2?
The first field is a node reference (the meal), the second is the taxonomy term (breakfast, lunch, dinner) and the third is the date.
Comment #3
yched CreditAttribution: yched commentedhttp://drupal.org/node/108226 seems related, if not a duplicate.
Comment #4
harriska2 CreditAttribution: harriska2 commentedThat link above is for views fusion, a module I do not use. However, it could be related. My problem is specific to the Calendar views function when using a node reference. When not using the Calendar views function, the node reference works fine.
Comment #5
yched CreditAttribution: yched commentedRight. The 'invalid argument in foreach' error in the other thread got fixed internally in views fusion - the thread is now about something else, unrelated.
But I guess that similarly, the 'invalid argument in foreach' error you're reporting might be specific to Calendar. I'm bringing this over there.
Comment #6
KarenS CreditAttribution: KarenS commentedThis turned out to be extremely tricky to identify, but should be fixed now in latest commit, and will probably fix other errors in display non-date fields in the calendar.
Comment #7
(not verified) CreditAttribution: commented