I've built a community site using Organic Groups, with a number of custom fields. While prepping to upgrade my D7 core to the latest release, I attempted to disable all modules.
After disabling all active (black checkmarked) modules, there are a number which remain grey-out, making it impossible to disable, and so continue on to the upgrade. Research suggests there is a file field dependency issue, but it's impossible for me to determine which is the base cause.
I did check the field_config table, as some forum entries suggested. There were 30 items there, all using Field SQL Storage as the storage type and module. The listed module which implements the field type echoes (in part) the modules which cannot be disabled ; I've marked those below with an asterisk ( * )
Present core is 7.14
Modules which cannot be disabled:
Chaos tools
Entity API
Entity reference *
Field
Field SQL storage
File *
Filter
Image *
List *
Node
Options
Organic Groups *
System
Taxonomy *
Text *
User
While the references suggest I simply delete all entries on the field_config to clear the item, I am not confident enough of my understanding of the situation to do so just as an experiment.
Help or advice would be greatly appreciated.
Comments
Usually when its grayed out
Usually when its grayed out means there is dependency which should be specified in ()
You can also go to admin/modules/uninstall and remove modules from there.
Pedja
Drupal Geek at New Target Inc.
http://www.newtarget.com
Uninstall Modules
Thanks, but unfortunately, as it says on the Uninstall page: "To uninstall a module, you must first disable it on the main Modules page".
Since I cannot disable the modules in question, I can't uninstall them. Nor am I positive of the source of the dependency.
=-=
you DO NOT need to disabled non core modules for a D7 to D7 update. There is a difference between a minor update and a major upgrade. Minor updates are within the same major version D 7.10 to D 7.14. a major update is moving from one major version to another D6.26 to D7.14
major upgrades require disabling because those modules which were D6 won't work on D7 which is the same issue with themes and why one would switch to a core theme before a major upgrade.
Site updated
VM, thanks much. I had understood that module upgrades didn't require them disabled, but had thought minor core updates of any type required it.
So the site has been updated... but I'm still looking for a fix for mentioned issue, as I may wish to do a major upgrade at some point (D8).
=-=
it's important to note that simply unchecking a checkbox doesn't disable a module. One must uncheck the checkbox and then save the form. This sets the module to off in the DB. At that point, the other modules which were greyed out and couldn't be unchecked should not be able to be unchecked and disabled when the form is saved.
Unchecking
I understand the need to save after unchecking the selection box, and have already done so.
The modules I listed remain greyed-out after the save, making it impossible to disable them.
=-=
I've never seen that happen and without seeing it it's difficult to suggest what the issue is. A complete screenshot of the entire modules page may aid.
Screenshot
Quite understandable. You can see the screenshot at: http://tameshigiri.ca/screenshot.jpg
=-=
very odd .....
Looks to me like there is a circular dependency somewhere. a module that is listed as dependent on itself or dependent or a module which is dependent on another module which is also dependent on it.
looks to me that it's field sql storage since it's listed as required by itself. A search of the core issue queue may uncover an issue.
edit: found it: http://drupal.org/node/896698 iti is field sql storage
Thanks much! I'm note a
Thanks much!
I'm not a great coder, so the dependency issue eluded me. It seems they've purposely left the dependency in, for the reasons stated in your link. Oh well, I can either edit it out myself, or just disable the mod through the database.