Warning: Invalid argument supplied for foreach() in /modules/system/system.admin.inc on line 578
(screen shot attached)

Drupal 6.0-rc1
Basic installation, with only the update module active (to run the manual update check)

server:
Apache/2.0.61 (Unix) PHP/4.4.7 mod_ssl/2.0.61 OpenSSL/0.9.7e mod_fastcgi/2.4.2 DAV/2 SVN/1.4.2
PHP 5.23
MySQL 5.0.24a

When reviewing installing modules, I get an error on the foreach() check when running its search for dependencies. Even with all core-optional modules not selected, I still get this warning.

Screen shot is attached.

CommentFileSizeAuthor
drupal_warning.png125.11 KBcjeanson

Comments

asimmonds’s picture

asimmonds commented
Project: Drupal core » Event
Version: 6.0-rc1 » 6.x-2.x-dev
Component: admin.module » Code

A module does not have to be selected or installed to generate this warning. In your list you have the Event module suite, the warning is coming from the dependencies incorrectly declared for event_all_day and event_views.
Just remove these directories from modules/event/contrib if you are not going to use them.

It doesn't look like event_all_day has been updated for 6.x yet, and there is no usable views module for 6.x at the moment, so event_views won't be very helpful.

Reassigning to the event queue.

thrasher-1’s picture

thrasher-1 commented

I had the same error resulting from the Flash Video module. Once uninstalled and the flash_video folder deleted, the error no longer appeared. This bug is logged at the Flash Video module here: http://drupal.org/node/205656

rmiddle’s picture

rmiddle commented

I just got the same error Drupal 6 RC2 with latest 6 Events module. My site wont come up at all now I had to kill the DB and reload. This is ugle

killes@www.drop.org’s picture

killes@www.drop.org commented

I don't understand why this ought to be a event issue...

asimmonds’s picture

asimmonds commented
Status: Active » Closed (fixed)

I don't understand why this ought to be a event issue...

At the time event_all_day and event_views were the cause of these warnings because they haven't been ported to 6.x, but these warnings are not generated for non-6.x compatible modules anymore.