to reproduce:

1.) install the latest media module --dev version and enable it as usual
2.) do any futher steps like provided to use its functionality as usual
3.) Create or use an existing content type and create another image field using the media file widget
4.) (Not sure if it matters) create a node of that content type (that's at least what I did)
5.) Disable media module.
6.) Navigate to your content type edit fields form. The error should be ok here for now, saying that a field can't be shown because of a missing widget. Well actually it isn't ok, but this is another issue how to deal with disabled modules in general.
7.) But now comes the funny part for us on this issue: Re-enable the media module and navigate back to your content type edit fields form again. E Viola, The error will persist. And ... the field still will not show no more. So the field will be hidden for all times, since you even can't delete it. The only chance you have is, to delete the whole content type, which will lead to a warning that all content will be lost of course. Not good.

To demonstrate the errors obscurity I added another image field using the media file widget again while the error that the widget is missing and a field is still hidden persists :-)

screenshot attached

Comments

diqidoq’s picture

Just connecting to a possible reason for this issue here (core debate)

http://drupal.org/node/1199946#comment-4659266

Dave Reid’s picture

Question is do you get this same behavior if you repeat this with another module that provides a widget for another field?

Dave Reid’s picture

Status:Active» Postponed (maintainer needs more info)
Dave Reid’s picture

Status:Postponed (maintainer needs more info)» Closed (cannot reproduce)
Dave Reid’s picture

Status:Closed (cannot reproduce)» Closed (duplicate)

Marking this as a duplicate of #1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed is probably more appropriate. There's just no way we can help resolve this ourselves in Media.

David_Rothstein’s picture

Status:Closed (duplicate)» Closed (cannot reproduce)

I couldn't reproduce this with the latest code. Drupal falls back on the default widget with no error messages. Is this still an issue?

If Image module (the module which provides the field type itself) were disabled too, then I could imagine something like this happening... but #943772: field_delete_field() and others fail for inactive fields would likely have already fixed it.

David_Rothstein’s picture

Issue summary:View changes

Updated issue summary.