Enabling disabled modules causes error: Invalid argument supplied to element_children()

Please provide steps of how to recreate on a fresh install of drupal core only.

He described the steps, no?

Take any non-core module which has different entries in the modules list, say A and B, where A requires B. Enable B only. The system will correctly enable A as well, but it will throw the above error.

This happens with every possible module that I've tried on this website, so it's definitely not some module-specific problem.

Thanks for the info but I can't recreate on a local install which version of php are you using?

PHP Version 5.3.2-1ubuntu4.17
Apache/2.2.14 (Ubuntu)

The suggested fix only hides the actual problem.

If $elements is not an array, then some module is declaring a child element in a form array or an render array that is not an array.

The guilty module has to be fixed instead.

Sorry, thread status was set to "closed", re-opened. Will test patch in #7 tomorrow and provide feedback. Thanks for your prompt response.

Fresh install D7.15
PHP 5.3.10-1ubuntu3.2
Apache/2.2.22 (Ubuntu)

Error:
Warning: Invalid argument supplied for foreach() in element_children() (line 6300 of /var/www/SPG/includes/common.inc).

Patch in #7 works for me.

It was set as works as designed because this is not a core bug.

No I don't get any errors either on the you need enable to parent screen or the module screen after confirming. This is also on php 5.3.8.

For me this error is intermittent. I usually get it whilst in the admin overlay - I notice the error on the website underneath the overlay. On page refresh the error is gone and I've not yet been able to track down exactly which of my installed modules is causing the error.

I´m using MAMP with two instances of Drupal, local and dev, and I (git) push and pull between them. I´m getting the error on local but not on dev. Weird :/

How can I debug this?

I just got this error when installing a feature. There were a number of other modules that were being added on at the same time that were dependancies.

Ditto.

I think it might be the Advanced Help module causing this.

#1086990: Invalid argument supplied for foreach() when asking confirmation to enable required modules

I can confirm this post. I have tested multiple times and did not receive an error until after Advanced Help module was installed and I received the identical error message.

Not so sure about #19. I don't have advanced help installed or even on my server!

On a fresh installtion of 7.16 I could not reproduc the issue by following the steps specified at #1711256-3: Enabling disabled modules causes error: Invalid argument supplied to element_children()

Hello,

I have the same issue with the "external link" module in drupal 7.16 .

Best regards
Frank

Got this again enabling panels. Have to look at foreach ($elements as $key => $value) { to see what module might be causing this to happen.

http://api.drupal.org/api/drupal/includes!common.inc/function/element_ch...

I received this issue too.
I had enabled, disabled then re-enabled clientside validation module.

Warning: Invalid argument supplied for foreach() in element_children() (line 6300 of /home/e-smith/files/ibays/sota3/html/includes/common.inc).
Warning: Invalid argument supplied for foreach() in element_children() (line 6300 of /home/e-smith/files/ibays/sota3/html/includes/common.inc).
Warning: Invalid argument supplied for foreach() in element_children() (line 6300 of /home/e-smith/files/ibays/sota3/html/includes/common.inc).
Warning: Invalid argument supplied for foreach() in element_children() (line 6300 of /home/e-smith/files/ibays/sota3/html/includes/common.inc).

I am having this issue as well. I am not sure what caused this, but I updated ctools and metatag to the latest dev. I am getting these messages:

    Warning: Invalid argument supplied for foreach() in element_children() (line 6300 of //includes/common.inc).
    Warning: Cannot use a scalar value as an array in drupal_render() (line 5767 of /includes/common.inc).
    Warning: Cannot use a scalar value as an array in drupal_render() (line 5822 of /includes/common.inc).
    test

I had the same issue half an hour ago. Reading this issue and the one for advanced help, I have given it a try to disable 'advanced help' module, and the warning is gone!!

Having this very annoying issue as well. Started after installing 'Inline Form Errors' module, and disabling the Adv. Help module did nothing for me.

If there's a working patch, why wasn't it included in the latest minor update? :-(

@Tobias Jonch until clear steps to reproduce are provided the issue can not be solved.

Updating to the latest dev of Advanced Help fixed this for me. It was fixed in this issue: http://drupal.org/node/1086990

Disabled advanced help. Warning went away.

Curiously, I just re-enabled Advanced Help and there still is no warning?

#7: drupal-Casting-null-array-1711256-7.patch queued for re-testing.

I had a site where I upgraded from D6 to D7 and I received the same error on product dependencies edit tab. I did this patch and it worked.

Muhammad
www.app-desk.com

Also experienced this issue which happened to come from Advanced Help (thank you #31).

• Disabling Advanced Help made the warning go away
• Re-enabling Advanced Help made the warning go back

Looks like this could be a duplicate of #1086990: Invalid argument supplied for foreach() when asking confirmation to enable required modules indeed.

I'm seeing this problem on a site I just moved from one host to another. The problem did not show up on the old host, and does on the new host. I have made no changes to drupal files or the database.

The PHP version has changed, and presumably aspects of the apache setup.

My guess is that $elements has sometimes been null for some time, but that newer PHP versions complain while older ones didn't. That seems to be born out by Eksempel #2 (example) at the following url. (note that the /en/ version is different, but in fact the text is mostly english anyway).

http://docs.php.net/manual/da/language.types.array.php

The increase in writes to the watchdog table is not particularly welcome. The patch in #7 therefore has some value besides papering over the problem. Also, the meaning of the warnings is fairly obscure. It'd be better though if it also recorded a single more helpful warning, even if that is still an interim solution.

I cannot reproduce this issue with Advanced Help, or under the circumstances posted by the original reporter in comment #3 with Drupal 7.24 or 7.x.

As stated in #8, #7 is not a fix for the problem.

It looks like this was a duplicate of #1086990: Invalid argument supplied for foreach() when asking confirmation to enable required modules which was fixed in advanced_help-7.x-1.1

If you are still seeing this problem and aren't running an older version of advanced_help then please reopen the issue with clear steps to reproduce that can be followed by another developer. Ideally this means starting with a fresh installation of the latest version of D7. If those steps involve installing one or more contrib modules, then you should file a new bug for that contrib module, but mention this one so the maintainer can see how this was fixed.

There is no point reopening this issue without adding steps to reproduce, as there is not enough information to fix any potential bug.

It's because foreach expects an array and gets passed a null value.

On our system it wasn't because $elements was null, it was because it was empty. Enclosing the foreach with this fixed it.

if ( ! empty($elements) ){
......
}

I know hacking core is discouraged but I've included a patch anyway.

Relating issue to #1086990.