Closed (won't fix)
Project:
Drupal core
Version:
6.x-dev
Component:
system.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2007 at 00:03 UTC
Updated:
30 Nov 2007 at 14:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
catchpyutaros: do you have devel module installed?
also this is a duplicate of: http://drupal.org/node/190729
Comment #2
catchComment #3
pyutaros commentedI'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.
Comment #4
nathanclayton commentedIt'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.
Comment #5
pyutaros commentedCould 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.
Comment #6
catchpyutaros: yes that would cause it.
Comment #7
catchComment #8
catchComment #9
galapas commentedThe 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.
Comment #10
webernet commentedDrupal core doesn't support broken code.