Helllo,
I tested this module as we want it to use for one of our future projects.
What i found:
1, Contextual filters
1.1 -> Contextual filter not works with integer values it takes only strings.
1.2 -> Contextual filter not takes more values, normally the views contextual filter can take value1,value2 or value1+value2 so i can filter the view results by more criteria with OR it not works now :S
We used views in this way in past ->
$views = views_get_view('your_view');
$views->set_display('your_view_display');
//Set some arguments for contextual filter
$view->set_arguments(array($geo_args));
//Set view filter for name
$filters['name'] = $activity->name;
//Set date criteria
$filters['start_date'] = $activity->field_date['und'][0]['value'];
$filters['end_date'] = $activity->field_date['und'][0]['value'];
//Set our exposed filters by criteria
$views->set_exposed_input($filters);
$views->execute();
Then we used view results in our custom module...
Can we achieve similar to this with this module? We started to use your module, because we pushed all the fields to MongoDB so it would be good to fix this bugs.
2, Exposed filters not filtering integers, not filtering date values i tried normal date values no timestamps. Maybe the timestamp works better?
Thanks Greg
Comment | File | Size | Author |
---|---|---|---|
#4 | Screen shot 2013-01-02 at 4.35.57 PM.png | 102.92 KB | majorrobot |
Comments
Comment #1
chx CreditAttribution: chx commentedThanks for the report, is this a duplicate of http://drupal.org/node/1418558 ? I am planning to incorporate that patch soon (perhaps as soon as today)
Comment #2
greg_meszaros CreditAttribution: greg_meszaros commentedI tried the patch from http://drupal.org/node/1418558 but it didn't helped me, maybe there are some other changes in your module from that time. Ok, if you push out the new version of the module, i will test it and report back to you.
Thanks, Greg
Comment #3
majorrobot CreditAttribution: majorrobot commentedI'm not seeing 1.1 (in either the stable or the dev releases), but I can confirm that 1.2 is still an issue.
If I try to use a taxonomy field, for instance, as a Contextual Filter, and I select the Taxonomy validator with the Filter type "Term IDs separated by , or+", the View only filters by the first value in the submitted arguments.
For instance, if my filter value that I feed into the View is "51+52" or "51,52" — and those are valid tids — then I just get results for tid 51.
Thanks!
Comment #4
majorrobot CreditAttribution: majorrobot commentedActually, I see that 1.2 is actually user error (or is just something plain confusing about the Views interface).
It's not enough to set the Filter type to "Term IDs separated by , or+" for some reason. There's a 2nd step — checking off the "Allow multiple values" box in the "More" fieldset. It's hidden, and it's counterintuitive that you have to set it twice, but that's more of a potential Views usability issue, I suppose.
Comment #5
colanAssuming this is duplicate of #1418558: Integers for Contextual Filtering as nothing else seems to be amiss here.