Hello Viewers!
First of all: Thanks for your work. Then: I originally wanted to set the issue category to 'support request', then I realised that this is a bug. And if not, then this could be considered a 'feature request'.
However, in my attached file (zipped flash screen-capture) I try to show you my main problem -- it seems that an exposed filter doesn't have an effect on a/any pager! Both (filter as well as pager) obviously influence the view result, but they should actually also influence each other, especially from filter/ exposed filter to/towards pager.
If you could help me out of my, hopefully temporary, confusion due to tiredness, I would be glad. I cannot see clearly any longer! If this could be considered a long term issue then we should try to find a cure for it.
I am using a set of fields in this view ... the one in the focus here is the date field, naturally. The view contains a contextual filter (for the pager) & an exposed filter (regular user GUI). The default value, btw, of the contextual filter seems to be useless -- I've returned 'foo' via 'Views PHP' without any consequence.
I am really baffled somehow since I don't have problems programming modules and whole software solutions, but I just don't seem to get this thing here! Maybe I am too tired, but it should be so easy, shouldn't it?
| Comment | File | Size | Author |
|---|---|---|---|
| views-filter-screencapture_2012-02-09.zip | 858.15 KB | Blooniverse |
Comments
Comment #1
Blooniverse commented... changing the status settings, due to the discovery that the 'Date' module doesn't seem to provide a value in the query string argument
field_date_value[min]=-- when using a date field with the form element 'select'! Golly gosh, I was really convinced this was a Views issue.Comment #2
Blooniverse commentedChanging status settings due to redundancy. No further explanation.
#1425774: array_filter() -- first argument should be an array in date_select_input_date()