Received the above error when accessing the modules page on a fresh installation. Hope this isn't a dupe, but I couldn't find it in a search. I'm using php 5.2.2 on Dreamhost. Server is running Debian Linux. Please let me know if you need more info.

CommentFileSizeAuthor
#9 system-admin-inc.191342.patch1.02 KBgalapas

Comments

catch’s picture

Version: 6.0-beta2 » 6.x-dev
Status: Active » Postponed (maintainer needs more info)

pyutaros: do you have devel module installed?
also this is a duplicate of: http://drupal.org/node/190729

catch’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)
pyutaros’s picture

Status: Closed (duplicate) » Active

I'm not so sure this is a dupe of the issue you reference. That issue is directly related to the Devel module. This happened before any modules were enabled. I do have devel installed now (minus the themer), but it was not installed upon my first access of the modules page. I am going to switch this back to active.

nathanclayton’s picture

It's caused by one of your third-party modules (loaded or unloaded) having a malformed .info file

Instad of having "dependencies[] = ..." it has something like "dependencies = ..."

system.admin.inc is expecting an array and it isn't given one - that's what the problem is.

pyutaros’s picture

Could this be caused by having my 5.X module folders in the modules directory of 6.X? I put them there as reminders of all the modules that need to be ported to 6.X before I officially make the switch. My 5.x modules would obviously have the old style .info files.

catch’s picture

Status: Active » Fixed

pyutaros: yes that would cause it.

catch’s picture

Category: bug » support
catch’s picture

Status: Fixed » Closed (works as designed)
galapas’s picture

Category: support » bug
Status: Closed (works as designed) » Active
StatusFileSize
new1.02 KB

The attached patch address this issue by testing the dependencies to ensure it is in the form of an array. If not, an error is posting stating

"The module-name module appears to not have been upgraded to work with Drupal 6. Therefore, it is not possible to show dependencies for this module."

Optionally, a patch could be posted to explode the dependencies if they are still in the old style; however, if the .info file has not been updated then it is possible that the rest of the module wasn't either.

webernet’s picture

Status: Active » Closed (won't fix)

Drupal core doesn't support broken code.