|Issue tags:||views 3.x roadmap|
When you have some kind of numeric like filter, for example node: nid, field: field_name or some kind of date field
having just a pure textfield isn't enough.
At the moment people would have to write custom code to be able to do something like "4 or more" as a select option.
The solution to the problem is to provide the users to configure the options of the exposed filters.
With this patch you have an additional checkbox "grouped filters" which opens you a total new interface of allowed options.
Instead of a "single filter" you can configure each group item to use a certain operator and value.
You have several things in the userinterface you can do:
- Configure the operator of the group item, for example "between" or "greater"
- Configure the values of the group item
- Add a new group item
- Select the default group item
Fitler UI for a string filter
Filter UI for a number filter
Exposed Filter for the number filter
Tests from more users.
User interface changes
Original report by [dagmar]
I would like to implement a new kind a exposed filters into views.
I'm thinking in a combo box with like this:
Select Number Rooms:
4 or more
Of course this can be easily implemented into a custom module, and I know how code it.
However maybe this could be a more abstract feature in views 3, allowing filters to merge into a single form a combination of a filter and a operator.
User could define something like this in a UI
Operator Value Display
= 1 1
= 2 2
= 3 3
=> 4 4 or more
I understand that specially "Value" is a complex thing to define. But, maybe it is possible to implement without destroy all the filters handlers, what do you think? dereine? merlinofchaos?
I think exposed form plugins are not the better way to configure this, probably a redefinition of views_handler_filter can make this possible.
What do you think, is a very crazy idea, or not?