Can't disable the module (due to fields) [#2132817]

Okay, need help trying to figure out how to disable this module. I can't uninstall it since I can't disable the Media module, and I can't disable it is because drupal (7.22) says there are fields that require it. I tried to remove such a field through the node type editor and got a big fat no no. I created one test content (with the media gallery module which itself is now disabled), removed it and can't see a trace of any other content that might be linked and blocking.

Anyone got any ideas on what I'm not doing right?

Comments

Comment #1

tierso CreditAttribution: tierso commented 11 November 2013 at 00:26

Title:

Can't disable (due to fields)

» Can't disable the module (due to fields)

Comment #2

ParisLiakos CreditAttribution: ParisLiakos commented 18 November 2013 at 10:28

so if you check under admin/reports/fields you see no Media fields?

Comment #3

Devin Carlson CreditAttribution: Devin Carlson commented 21 November 2013 at 19:51

Status:

Active

» Fixed

As ParisLiakos mentioned in #2, you should check the field report page to see if any media fields exist.

Comment #4

tierso CreditAttribution: tierso commented 23 November 2013 at 16:09

Well, I kept looking while waiting for an answer and it seems to be related to this issue:
https://drupal.org/node/1967932
..and no, I had no media fields listed whatsoever (I had previously uninstalled Media gallery and completely removed it). There is the field_tags for Image, Video etc (but it belongs to the Taxonomy module as far as I can see). All the reported fields belong to content types created prior to either Media module was installed.
This is what the module manager reports for Media:
Required by: Drupal (Fields pending deletion), Media Internet Sources (disabled)
(I have not installed Media Internet Sources, so I'm guessing it belongs to Media?)
Anyhoo, the question now is, if it's Media and/or Media Gallery bug?

Comment #5

tierso CreditAttribution: tierso commented 23 November 2013 at 17:00

I dunno if I would call the issue fixed btw, but maybe you see the current behaviour as a feature rather than a bug. Ignoring that, after manually disabling the module as per described in https://drupal.org/node/1967932 is it safe to uninstall the module (and not swiss cheese the site in some way)?