warning: Invalid argument supplied for foreach() in .../cod_session.module on line 713.
warning: Invalid argument supplied for foreach() in .../cod_session.module on line 740.

There are no warnings when the user has added items to their schedule (flagged items).

Thanks

CommentFileSizeAuthor
#7 1272254_avoid_notices_empty_schedule.patch13.33 KBgreggles

Comments

coltrane’s picture

coltrane
he/him
commented
Status: Active » Postponed (maintainer needs more info)

Can you try beta2 and report whether this error still exists?

ltrain’s picture

ltrain
She/her
Location Toronto
commented

I downloaded and tried the packaged beta2 version - no warnings (there were warnings in packaged beta1).

But then I upgraded the support modules to beta2 (which I am using with an existing drupal site), and I still get the warnings there.

Thanks

smerth’s picture

smerth commented

Hi there,

I am using the beta 2 version as well and I can confirm an identical error message. (other than that - what a nice piece of work!)

ltrain’s picture

ltrain
She/her
Location Toronto
commented
Version: 6.x-1.0-beta1 » 6.x-1.0-beta2
Status: Postponed (maintainer needs more info) » Active

There are two confirmations of the error with beta 2.

Thanks

rachel_norfolk’s picture

rachel_norfolk
Primary language English
Location UK
commented

yes, having same issue in beta2.

Is there anything anyone would like me to look at to help analyse?

dc_marc’s picture

dc_marc commented

Same or similar issue. Installed beta2 fresh and performed only the security upgrades for the modules. Created one event, one time slot, five rooms, and one schedule item. Edited the Program page as well. Just having done this alone, the error shows up 6 times on /program/session-schedule logged in as user1. The first five all indicate line 713 is the error, while the sixth indicated line 740. My assumption is that 713 related to the 5 rooms (it's the only thing I have 5 of), while line 740 relates to either the event or the time slot or probably the schedule item. In any case, is there a workaround?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Needs review
StatusFileSize
new 1272254_avoid_notices_empty_schedule.patch13.33 KB

I can confirm this and have a proposed fix. It looks like a lot of changes, but it's really just a few lines of empty checks that looks like a lot because of indentation changes.

ezra-g’s picture

ezra-g commented
Status: Needs review » Fixed

Looks good - thanks!

http://drupalcode.org/project/cod_support.git/commit/8f3a238

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.