Needs review
Project:
File Entity (fieldable files)
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Nov 2013 at 21:16 UTC
Updated:
23 Aug 2015 at 20:48 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
coredumperror commentedI just ran into this exact issue, and it was very frustrating. It appears that a database update aught to have been implemented for the alpha2 to alpha3 upgrade, changing all the existing
image__<view_mode>__file_imagerules toimage__<view_mode>__file_field_image. I'm not sure how that would interact with formatter settings saved in Features, though.Comment #2
coredumperror commentedWhoops, didn't mean to change the title like that.
Comment #3
bennybobw commentedI also ran into this issue where the file_image formatter is still enabled and lighter than file_field_image. When file_view_file is called, it takes precedence over the file_field_image formatter. I assume the easy fix is to simply disable the file_image formatter in the db.
Comment #4
rwohlebEven a simple hook_requirements() that warned the user that the deprecated file_image formatter was still enabled would be helpful. This is especially true when it has a low weight value as @bennybobw discovered. It could then link to a doc on D.O that describes how to manually fix it. This would then avoid having to mess with potentially nasty upgrade code for something that might only affect a small number of people.
Comment #5
OnkelTem commentedSame here.
I noticed that a newly created view mode (I use Display Suite for that) lacks this file_image formatter in "file_display" table, while my old view modes have it and there is no way to delete them.
Comment #6
OnkelTem commentedLet's do what was suggested in the Summary.