Is Not Null doesn't work as an overridden relationship
thekevinday - March 26, 2009 - 17:48
| Project: | Killfile |
| Version: | 6.x-1.0-beta1 |
| Component: | Views integration |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
You currently have a global "disable showing of all killfiles in views".
This is not what I need in this case.
The case is, I have views that display published, unpublished, and (killfile) deleted content.
Currently, there is no way to say if content is killfile'd then etc..
I want the killfiles to appear in a separate page from the unpublished content.
So I am asking for a way to filter out killfiles.
Pretty much what I am asking for is a filter that is exactly like the "is published" filter where the choice is a boolean of "yes" or "no".
#1
First, I was not aware that specifying the relationship would provide the "is NULL" and "is NOT NULL" options.
When that was done, the "is NOT NULL" check did not seem to change the results.
It turns out that if the relationship is overridden from the default display by some page and that relationship is not provided by the default view, then the "is NULL" and "is NOT NULL" tests do not work.
Shouldn't overridden relationships work as well or is this also a misunderstanding on my part?