Closed (fixed)
Project:
D7 Media
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jun 2011 at 16:19 UTC
Updated:
4 Jul 2011 at 16:51 UTC
We have a pseudo multisite install, one shared code base and each site with its own separate db. Uninstalling media and its associated modules, we have been unable to uninstall File Entity EXCEPT on the first site it was uninstalled from. The File Entity checkbox on the uninstall UI is grayed out on the other two site/installs.
Hoping to clear out all cruft and re-install media/components from scratch...
Comments
Comment #1
jenpasch commentedadditional clarification:
After uninstalling File Entity from the first website, we were unable to uninstall it from the other sites as the checkbox was grayed out
The uninstall happened successfully on the db where the original installation was done, but not successful on the 2 dbs that were cloned after that installation.
Comment #2
brianV commentedsubscribing.
Comment #3
jenpasch commentednot fixed, but the issue is misstated... turns out that File Entity in grayed out (un-uninstallable) on all 3 installs
Comment #4
brianV commentedjenpasch and I both work at PINGV.
We determined that the problem was that file_entity_test had been inadvertently enabled at some point in history.
As of #1150812: Testing modules should be hidden, the testing modules were hidden from the module list. That left us in the position where File Entity was not uninstallable (greyed out on module uninstall screen) as File Entity Test depended on it, but as the test module was hidden it was not listed among the modules File Entity was a requirement for, nor was there a UI-based way to disable it.
Disabling it, and uninstalling via drush fixed the issue; it made File Entity uninstallable.
On a side note, despite having hidden module depending on it, we *could* disable File Entity, just not uninstall it. Should it be possible to disable a module which has hidden modules depending on it? If that is the case, perhaps I'll open a core issue over it.
Comment #5
brianV commentedAlso, marking as fixed so it is visible to the maintainers.