This seems to be a regression that was introduced recently.

After a fresh install of File Entity:

I am now seeing no Enabled displays for 'Default' 'Teaser' or 'Preview' for the Image file type.

For Video, I see an Enabled display for 'Default' but nothing for 'Teaser' or 'Preview'

For Audio and Document, this seems to be fine.

Comments

saltednut’s picture

FWIW, I have tried this both inside the DF and Lightning profiles AND on a standard Drupal 7.28 install enabling just ctools and file_entity manually. So it doesn't seem to be anything related to Features or what-have-you.

devin carlson’s picture

Status: Active » Fixed
Related issues: +#2266039: Library and thumbnail not generating images

Related: #2266039: Library and thumbnail not generating images.

Commits a74c013 and 13fa2b0 from issues #2104193: Default file entities are not exportable by features (Media File Entity Overridden) and #2192391: Default file entities are not exportable by features (Sibling Issue) broke the default display configurations for File Entity and Media so I've reverted them for now.

As we discussed at NYC Camp, file displays are ctools exportables like many other configuration objects in D7. However, when it comes to views, modules are able to provide/alter default views, which users can override and then export to features without issue. I'm not exactly sure what the cause is (is there a problem with File Entity's ctools integration or does Features do some special casing for views) but it seems like there should be a solution that would allow file displays to work in the same manner as views without requiring modules/installation profiles to do all of their customizations and cleanup in hook_install() hook_uninstall().

sylus’s picture

I think the removal of these commits is going to cause a few problems for people. Particularly for anyone that was running with them as in the system table it will now point to one higher schema then it should be. Can we at least keep an empty schema for both file_entity and media to mitigate this immediate issue.

As for the regression I believe this was tested in the other issue by both Brantwynn and myself. There might have been something missed but I still think the hook_install route is the way to go. Particularly because the primary maintainer of features mpotter said this in the other issue:

In general, using the media_file_default_displays_alter() method is just the wrong way to handle this. The Media module should not be dictating what the file display modes should be. The Media module should set the *default* display modes, perhaps when the module is enabled.

saltednut’s picture

RE: #3 - yes, its quite strange because the when we were running with the patches everything was working. Once the commits went in and we switched to the dev version this problem came about.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

dsnopek’s picture

@brantwynn: Can you post steps to reproduce this on a vanilla Drupal 7.28 site?

Here's what I tried:

  1. Install Drupal 7.28 with the "standard" profile
  2. Download ctools 1.4
  3. Checkout file_entity 7.x-2.x from Git and apply this patch: https://drupal.org/node/2192391#comment-8878469
  4. Install using: drush en -y file_entity
  5. Then looking at the UI, under /admin/structure/file-types/manage/image/file-display as well as for the "Teaser" and "Preview" displays, I see "Image" checked with the correct "Image style" and "Link image to" values. Also, looking at the "file_display" table in the database shows all the correct entries.

So, I'm not able to reproduce your experience here. Does it depend on 'file_entity' being installed as part of the profile? I'm actually going to try that next just in case...

dsnopek’s picture

Hrm. I just modified the "standard" profile to have "file_entity" as a dependency, and it came up correctly on install, looking at both the UI and database. :-/ Could you try again with the newer patch?