Active
Project:
ImageField
Version:
6.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
11 Apr 2012 at 21:47 UTC
Updated:
12 Mar 2024 at 07:36 UTC
Jump to comment: Most recent
Comments
Comment #1
merlinofchaos commentedThis is all handled by the imagefield module, not Views.
Comment #2
Anonymous (not verified) commentedNot sure if I understand clearly.
Are you saying there is no way to instruct the view to not display a node in the query results if the ImageField is using a default image in place of an actual user uploaded image... because views can't tell the difference?
Is there another solution if that's the case?
Comment #3
merlinofchaos commentedI'm saying that data provided by modules also has its Views integration provided by that module.
Views core does not know any specifics about the data provided by modules -- so any features *about* that data has to be provided by the module. Does that make more sense?
Comment #4
Anonymous (not verified) commentedYes.
I understand. Unless ImageField supplies views with "is default" data, then Views cannot distinguish between whether the image was uploaded to the field via user interaction or automated default image binding.
sooooo... any ideas on solutions?
Comment #5
krystianbuczak commentedWhat about a solution with Filter: image FID with "not null" or ">0" option?