User login

Views Exposed Filters and Range Filters Problems and Possible Solutions

First thing Agaric does of course is upgrade modules to their most recent version (Relativity 5.x-2.1 and Views 5.x-1.6). Fun, but no effect. Same return on clearing the views cache.

Two issues that seem related:

  • A relativity (parent node) filter and it doesn't seem to work.

First problem came up in the context of Views Fusion - http://drupal.org/node/147274

From my mentors own mouth: "indeed. There are a lot of problems with filters with views 1.6"

But it applies to any view that you try to expose but uses an add_where command that works in the view but not accessed through a filter or like method. Fago provided a patch: http://drupal.org/node/150094

It may or may not work for node relativity as is, but node relativity certainly uses add_where in its relativity_views.inc file:       $query->add_where("relativity.parent_nid = %d", $arg);

The second problem may be fixed just with getting exposed filters to work (haven't wrapped my head around the purpose quite) but I think it needs more.

However, solutions in the works noted below that would load views by AJAX or AHAH could fix the exposed filter issue as well, because the filtered view could be loaded exactly as a regular view.

  • I've been trying to get a exposed filter that will allow the user to filter down the list of family_info records listed in the view to records with "Date of Assessment" between [date1] and [date2]

Exposed Filters - Range search not work
http://drupal.org/node/151591

Good explanation by yched about the limitations of views filters and workarounds.

"I think this is a know limitation of views : you can't have two exposed versions of the 'same' filter."

"You can use 'Computed field' module http://drupal.org/project/computed_field to create a hidden field that simply duplicates your original "amount" field.
In order to have this field available in views, you'll have to specify that the field should be stored in the db."

Same question was raised in http://drupal.org/node/143981

according to freeman - http://drupal.org/node/151591

"I think it wouldn't be considered a bug per se, but a limitation.

I've gone ahead to make a patch (http://drupal.org/node/151989)"

As of August 26 that patch is still being worked on.

First thing Agaric does of course is upgrade modules to their most recent version (Relativity 5.x-2.1 and Views 5.x-1.6). Fun, but no effect. Same return on clearing the views cache.

Two issues that seem related:

  • A relativity (parent node) filter and it doesn't seem to work.

First problem came up in the context of Views Fusion - http://drupal.org/node/147274

From my mentors own mouth: "indeed. There are a lot of problems with filters with views 1.6"

But it applies to any view that you try to expose but uses an add_where command that works in the view but not accessed through a filter or like method. Fago provided a patch: http://drupal.org/node/150094

It may or may not work for node relativity as is, but node relativity certainly uses add_where in its relativity_views.inc file:       $query->add_where("relativity.parent_nid = %d", $arg);

The second problem may be fixed just with getting exposed filters to work (haven't wrapped my head around the purpose quite) but I think it needs more.

However, solutions in the works noted below that would load views by AJAX or AHAH could fix the exposed filter issue as well, because the filtered view could be loaded exactly as a regular view.

  • I've been trying to get a exposed filter that will allow the user to filter down the list of family_info records listed in the view to records with "Date of Assessment" between [date1] and [date2]

Exposed Filters - Range search not work
http://drupal.org/node/151591

Good explanation by yched about the limitations of views filters and workarounds.

"I think this is a know limitation of views : you can't have two exposed versions of the 'same' filter."

"You can use 'Computed field' module http://drupal.org/project/computed_field to create a hidden field that simply duplicates your original "amount" field.
In order to have this field available in views, you'll have to specify that the field should be stored in the db."

Same question was raised in http://drupal.org/node/143981

according to freeman - http://drupal.org/node/151591

"I think it wouldn't be considered a bug per se, but a limitation.

I've gone ahead to make a patch (http://drupal.org/node/151989)"

As of August 26 that patch is still being worked on.

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.