Invalid argument supplied for foreach() - line 695

I am receiving the same error. I am running 4.7.3.

Any input? This looks like it is a great module.

That error indicates it wasn't able to find any layouts, which mind mean you have a broken installation. Be sure that you have your 'panels' directory with panels.module in it, and you have the 'layouts' and 'content_types' directories beneath that.

I am getting the exact same error, but I have the panels.module in the panels directory, and I the 'layouts' and 'content_types' directories beneath that. Any help?

I am using 7.3 and a fresh CVS panels install.

I am getting the same error. I installed buy wget and tar zxvf in the modules dir like I usually do. The dir structure seems ok..

Module does not work still.

Serving

I just committed code that I think will fix this.

You can quickly test this by changing line 745 of panels.module to:

    require_once('./' . $file->filename);

I just downloaded the latest panel from Drupal today.

I get the following error when I try to create a panel page. The version of microcontent is from 8/28 GMT.

My error is
warning: Invalid argument supplied for foreach() in /home/pittsfor/public_html/modules/microcontent/microcontent.module on line 241.

Of course, disabling microcontent makes the error go away. I have not done anything with microcontent except enable it.

Rich
(rl)

Hi Merlin,
I am still getting the same warning, even with the update. The warning says:

warning: Invalid argument supplied for foreach() in /var/www/html/mydrupal/modules/panels/panels.module on line 696.

Am I doing something wrong? The directories are in the correct place.

Thanks,
Sean

rl, Please don't take over issues with new problems.

The microcontent issue may or may not be related, but it wasn't in the original reports, and the error you show is completely different. And I don't know anything about the microcontent.module -- since that's the module that's giving the error, you should file an issue against microcontent (and possibly a separate issue against panels and post links from each issue to the other so that we can cross reference).

newms: Argh. I don't know why you're having that problem. :/ I'll look into it further. It's difficult because I can't reproduce it so I can only take guesses as to why it fails for you.

Are you using PHP5?

No I'm using PHP 4.3.9.

I found out what the problem was. I was entering content on the panels in node form, e.g node/3 rather than the title of the page or the NID.

Thanks for your efforts Merlin.

Ok, there are so many different people getting errors in this issue, and some are fixed and some are not.

If there are still existing errors -- and I believe there are -- please file new issues so I can keep track of what's going on?

newms: Could you please file a separate bug about the node/3 input giving that error? It should give a much more meaningful error with that input.

Thanks!

I can confirm this bug.
I'm using Drupal 5 (RC 2).
Panel version: // $Id: panels.module,v 1.10 2006/10/31 23:49:58 merlinofchaos Exp $
"warning: Invalid argument supplied for foreach() in /path/to/modules/panels.module on line 697."

On line 497: "foreach ($panels->content as $location => $list)" there's no check first if $panels-content is an array or not, so if there's no content added PHP will output a warning, since $panels->content isn't an array.

Two possible fixes:
1) turn off warnings in php.ini (ugly fix)
2) add a check in panels.module

Replace:
foreach ($panels->content as $location => $list) {
foreach ($list as $area) {
$function = $content_types[$area->type]['callback'];
if (function_exists($function)) {
$content[$area->area] .= $function($area->configuration);
}
}
}

With:
if (is_array($panels->content)) { // this line is new
foreach ($panels->content as $location => $list) {
foreach ($list as $area) {
$function = $content_types[$area->type]['callback'];
if (function_exists($function)) {
$content[$area->area] .= $function($area->configuration);
}
}
}
} // this line is new too

Cheers

The error you mention (which btw was opened in a separate issue, as I instructed when I marked the issue fixed) is fixed in Panels 1.1