Needs work
Project:
Date
Version:
7.x-2.x-dev
Component:
Views Filter
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Nov 2015 at 12:11 UTC
Updated:
28 Dec 2018 at 19:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mustanggb commentedHad problems with
empty()so changed tois_null()instead.Comment #3
mustanggb commentedOkay think I've got this figured out now, back on empty(), but now testing whether filters are exposed before using exposed/session values, which happens when you had exposed filters, however then another module (e.g. views_dependent_filters) hides/removes them.
Comment #4
mustanggb commentedSo the behaviour of #3 is:
a) Filter not exposed -> Query added with default value
b) Filter exposed -> Query added with filter value
c) Filter exposed then removed -> Query added with default value
I think in the instance of (c) the intention is that the default value is used as the default value of the exposed filter only, and if the filter is removed then the filter/default value should be ignored completely.
So the behaviour of #4 is (changes in bold):
a) Filter not exposed -> Query added with default value
b) Filter exposed -> Query added with filter value
c) Filter exposed then removed -> Query not added
Comment #5
mustanggb commentedLatest version.
Comment #6
chris matthews commentedThe 2 year old patch in #5 to date_views_filter_handler_simple.inc does not apply to the latest 7.x-2.x-dev and will need to be rerolled.