File/Image fields are no more handled correctly in views after commit f062a8b.

In my case the view was setup to display the Image field (field_my_image) of the retrieved entity, not the indexed one. After upgrading to the 7.16 version, such field is displayed as being always empty (also tried to re-index, but no changes in the view).
On the other hand: the indexed field is always treated as a 'File' field, and not as an 'image' field, thus no image formatters are available nor configurable.

The only noticeable difference between 7.15 and 7.16 is that the field (field_my_image) is no more listed in the default 'index fields', but needs to be added from the "Add related fields".

By reverting the commit f062a8b the issue is fixed and the view works as before.

Anyone else got the same issue?

Comments

thePanz created an issue. See original summary.

thePanz’s picture

Title: File/Image field broken after " » File/Image field broken (after commit f062a8b)
drunken monkey’s picture

I can't reproduce this problem, this still works fine for me. However, I'm not sure I understand your setup correctly.
E.g., what do you mean with "the retrieved entity, not the indexed one", why are you indexing the image field and are you sure you could add it to the index without using "Add related fields" before that commit?
Please provide a more detailed description of your setup, maybe even with screenshots!

drunken monkey’s picture

Status: Active » Postponed (maintainer needs more info)
drunken monkey’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

Ah, OK, seems I missed something there after all.
Closing here in favor of #2583263: Search API views stoped to work since 1.16. Thanks for reporting here and finding out the commit in question, that helped a lot!