Allowed file types on image field settings should not include non-image file types

Because File Entity allows you to create other File Types, I think we shouldn't hide the options, but always show the options where the file type allows mimetype image/*.

This is marked as a 7.x-2.0 release blocker.

Is this really necessary for 7.x-2.0 ? Or can it be pushed back to 7.x-2.1 (or a subsequent release)? It doesn't seem like this change request has generated much enthusiasm.

If I understand correctly. I have the same issue when I switched the widget from "image" to "media browser" for an Image field in a content type. I can still add non-image content using the library tab and the exposed filter.

I believe this can create a confusion for content editors, if someone tries to explicitly add non-image file type the submission takes place.

After changing an Image type field widget from Image to Media Browser and looking at the feature diff of field instance, I saw something feature diff and observed that :

'type' => 'image_image' was changed to 'type' => 'media_generic' (I am not sure if there is something exists like 'media_image' for images or 'media_video' for videos contents)

I tested the latest release from 4th Jan, 2017 (Yesterday) the issue exists. I have seen that this has been a prolonged one i community, any help here will be appreciated.

Thanks,
Sumeet

This should be closed or moved to the 'file_entity' project, as 'file_entity' is no longer part of media 7.x-2.x , it is part of 7.x-1.x however file_entity became it's own project. media 7.x-2.x uses the file_entity project. This issue sounds like it should be part of the file_entity project, not the 'media' project.

Therefore, removing this as a media 7.x-2.0 blocker.