Adding a range filter operator

This is very interesting. I'm currently overwhelmed so not looking at this Right Now, but posting a note to make sure I come back to this. Ranges have been an issue for me for a long time.

This patch contains the following problems:

1) The second patch is a reverse patch (it's removing your changes).
2) You should be able to put both files into one patch. Ideally you check out from cvs and use 'cvs diff -up' to create your patch.
3) How the ranges are used are not documented anywhere; this will confuse users to NO end. A solution to this must be found.
4) There is no need to pass the hardcoded operators in via %s; just put them in directly and remove them as arguments. (i.e, the <, >, <= and >=).

@freeman

This is wonderful. Thank you for the patch. I hope that this function is adopted in the views module.

On reflection, a couple of suggestions to make this easier for users.

First, the other filter operators (=, <=, >=, !=) are not required in the filter box. Must we* include the operator with these new range operators? Could we not use whitespace to separate the two operands?

Next, if the operators must be placed between the range operands, could the operands be added as part of the text description. e.g. "within range" becomes "within range ~"

And also, if the operands must be included between operands could we not also require the operands for the earlier filter operators and eliminate the select box?

* Yes, for now we must. For the patch requires it.

So, does that patch actually works? I installed both of them and got MySQL syntax error:

check the manual that corresponds to your MySQL server version for the right syntax to use near '~= '300000')

Also, I'm not completely sure if this will satisfy my needs when it's working - I need exposed price range filter where the min and max price limitations will be selected by user. Will this be possible with this patch?

Thanks!

I noticed that CVS apps wouldn't apply the patches, so I did it manually. I'll wait and see what you come up with. Oh, btw, there is a new post on the range filters - I haven't tried the technique yet, but looks quite promising http://drupal.org/node/164471

Subscribing! ~ ben, Agaric Design Collective

subscribing

Hi
This is a great patch, a much needed addition. I seem to have a problem though, and am wondering if someone can help me. I installed both the patches, and all works fine until you go into views and search. Rather than the serach results its throwing up an error which I dont understand. Am using Drupal 5, everything else (including other views) work just fine, so im guessing this is breaking something. Have attached a screenshot of the error on the results page.

Also, when Im searching for a value range im putting in "100-300" in the input box. This is the right format isnt it? Again this can be seen in the pic. Thanks!

subscribe

I hope this patch will be applied soon. Until then, I will manually apply it into my drupal.

I think that it will be useful to put a test in view_query.inc for the case in witch the user doesn't input a text in the form "value1 delimiter value2" and he input only one value... Something like this

if($value_range[0] == $filter['value']) //the explode function didn't explode anything
{
$query->add_where("%s.%s %s '%s'", $query->use_alias_prefix . $table, $field, $filter['operator'], $filter['value']); //old behavior
}
else
{
... //the switch statement from the patch
}

[edit] Sorry for the previous post (a problem in my browser)... Maybe someone can delete that. Thanks!

It seems that the range doesn't work for dates. Does anybody has the same behavior?

First of all thanks for providing this "hack" its what I needed on my site.

This is a hack to a hack but if you want to be able to allow the users to enter 30 to 40 (ie assuming is a date) then you can add this line of code (after you apply the patch):

$value_range = explode('~', $filter['value']); // lower-bound = [0], upper-bound = [1].

right before: $filter['value'] = str_replace(array("to"," to "),"~",$filter['value']);

Warning, I would only recommend doing this if you are going to be using this type of filter on numbers and not on text. Reason being it will replace "to" in any word, not just the one use as a delimiter. I am going to do it this way on my site because I know that the use of the ~ will be difficult for my users!

This is not ideal but hopefully a better solution can be incorporated in the next version of views that will just display two entry boxes.

Thanks and good luck!
Scott

I assume this patch is not yet in views
subscribing

I applied views_7.patch to views-5.x-1.6.tar.gz but still could not see the "Within Range" in the dropdown list when adding a view filter... I also cleared the views cache...

I then also tried searches with format: A ~= B as suggested above for inclusive, but no results.

Please is there any other patch that needs to be applied, or is there something else I need to do? Thanks.

Sorry, I was using it with the "Product:Sell Price" from ubercart... So looks like I need to make some more changes to make it work for this.

AMAZING! thank you!

And a quick question:

How can I switch the first and second parameters?

What I mean is this: I'm trying to make a filter search a field with values such as "-0.4" , "-0.35", etc...
These represent a percentage discount (i.e. "-40%", "-35%") which is calculated using computed fields to display "-0.4" as "-40%" in the search results (yes, user searches one field but results are actually displayed from another field).

When searching, say, size, it's logical to search "from size 1 to size 3" - from small to big - and so this patch works great!
When searching a percentage discount, it makes sense to search "from -35% to -40%".
In such a case, a user would input: "-0.35 ~ -0.4" - and will get no results, since the correct syntex should be "-0.4 ~ -0.35".

Hope this makes sense...

Thanks!

I asked this in the Apache Solr queue, but since range filter is working beautifully and not yet implemented - could it be possible to add a second field, where you can specify a +/- 'variance'?

This could be most usefull for searching decimal fields in combination with the range filter. That's actually what i need it for. I need users to be able to search "2.2cm - 5.4cm +/- 0.2cm" or even better "2.2cm - 5.4cm +/- 10%" (!!!).

This could serve VERY well on e-commerce sites. Users could search for "Price: 100$-200$ with a 10% variance" without needing to calculate what that actually means.

Most importantly, results could automatically be filttred with a 10% variance, and ensure that users are exposed to the broadest range of product while staying within (actually just a little bit out..) thier search criteria. Nifty marketing.

subscribing

I would like to see a similar patch for 6.x

Hi all,

I'm a little unclear on patching this - are two patches still required? One for the ...module and one for ...query.inc?

And it seems to need views2.module? I don't see that anywhere in module.

Thanks!

Arp

OK - I figured out how to patch, but I'm still only seeing equal/less than/great than as an option. Should there be more options, or am I doing something wrong?

how i can use this patch if i want search my user by age,...with the birthday and computed field doesn't work...

This patch works with decimal values. it doesn't for computed fields, or other non-decimal fields.

I really like this patch, but i'm finding users are having a hard time understanding how to use it.
What i would like, is to separate the range into 2 box - one for min. and one for max.
That would be way more intuitive.

Anyone know how this can be done?

I'm using custom forms to build the exposed filter, so i think this shoulden't be too hard, but i don't know how to take 2 values and make them one.

Thanks.

I really don't understand it either, but it's vital for any ecommerce shop that wants to allow people to search for price ranges.

any luck with D6 implementation?

it was working for me in D5, I was using "Within a range (inclusive)" for computed field (it was an age calculation), now I'm looking how to apply this to Views2 and D6

@czeky: Could you share with us how did you get that operator ("Within a range (inclusive)") to be available to computed fields in D5?

thanks!

well, I didn't have problems, so I cant tell You about some workaround.. manually patched using patch 7 both files.. and the option was there...

I had CCK field "birth" where user entered year, fg. 1975, and I wanted to calculate age, and I think using computed field was only option..

created computed field in node profile content type, set this to "raw input", data type "int", lenght "4", default value "0" and applied basic age calculation php snippet

it showed in views immediatelly, added to fields, in filters I set "Within range (inclusive)" value "0-99" - this will be basic option for users, age between 0-99 years, exposed that filter, labeled "Age from-to" filter setting optional on, default on, force single off, lock operator on, provided page view and it worked..

I could swear that didn't work.

I'm still a bit shocked this really works...

Thank you!

I have this instalation online, even I moved to D6 in the beginning, so its ugly, its just for a testing purposes only, but You can see it here

http://czeky.com/ekoseznamka/

its on the top of the page, labeled "Věk od-do" and in the input field is "0-99", and working, if You put "28-30" in the search field, it will list you all user in that age..

BTW: does someone know how to load CCK field from user-profile.tpl.php, or user-picture.tpl.php?

I have a field "gender", and want to change user picture according to Male/Female.. condition would be simple of course, but I can't get CCK field_gender content-profile node loaded into user-picture/user-profile...

amazing job....well done...but user friendliness as far as the usability of the exposed filters is concerned is a bit on the down side. This can be completely fixed if (range) values are entered in their own textfields....any thoughts about that...?

many kudos for the patch

Date Range allows the two dates to be entered into two different fields. Maybe it would be worth looking to see how they implemented that.

related:

#250769: Adding same filter twice doesn't work

At this time, only security fixes will be made to the 5.x version of Views.