I noticed something weird when working on #2269027: Cropped image not being served in WYSIWYG as "Original Size"

This is a note to investigate later...

We are creating file displays called "image__default__file_image" and "image__full__file_image". They control which image style is used for the Image entity in it's "default" view mode. However, these displays aren't controlable via the UI at all! In the UI, you actually get a display called "image__default__file_field_image", which just seems to be ignored.

Basically, this means that you're unable to change the image style used by the default view mode of images in the UI!

I'm really not sure what's going on here, but it's definitely something to try and get to the bottom of later...

Comments

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Related issues: +#2159149: 'file_display' components are always overridden (update Media / File Entity)

This issue appears to bring up the weird double image formatters: #2061531: Double 'Image' file formatter in the 'Manage file display' tab

I'm still not sure which we should be using...

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Status: Active » Closed (duplicate)

Ok, I've dug into this some and I feel pretty confident that we should really be using file_image_field, since it appears to be what Media is using by default and it's editable in the interface. Unfortunately, we can't switch to using that this Media issue is fixed: #2104193: Default file entities are not exportable by features (Media File Entity Overridden)

The Panopoly issue which tracks that is this one, which is where I'll fix this:

#2159149: 'file_display' components are always overridden (update Media / File Entity)

So, closing as a duplicate of that one!