Views Hacks Views Filter Selective Drupal 7 branch

so... everything BUT the taxonomy is working??

Thank you for posting @neoglez!

started testing, reporting any bugs I find along the way.

Using it with node reference fields ( http://drupal.org/project/references ) I received the following errors:

Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined property: stdClass::$nid in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 115 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined index: filter-status in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 124 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined index: views_handler_filter_in_operator in views_filters_selective_exposed_form_plugin->get_reducer_handler() (line 221 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined index: views_handler_filter_in_operator in views_filters_selective_exposed_form_plugin->get_reducer_handler() (line 221 of /var/www/html/sites/all/modules/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).

I second that using taxonomy fields (no reference fields here):

Notice: Undefined index: filter-status in exposed_form_alter() (line 124 of (...)/sites/all/modules/views_hacks/views_filters_selective/views_filters_selective_exposed_form_plugin.inc). 
Notice: Undefined index: location_handler_filter_location_country in get_reducer_handler() (line 221 of (...)/sites/all/modules/views_hacks/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
Notice: Undefined index: nid in pre_render() (line 83 of (...)/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc)

Using location country field only and avoiding taxonomy, the results are not limited. All the countries still appear in the select list. But no notices. I guess it's just not taken into account by views filters selective.
Limit "Location: Country" values to result set is checked though

Which field type is currently working?

@neoglez I wrote that I asked a php developper to help me, but unfortunately he isn't a drupal developper and he got lost in drupal's module developement. Sorry for that, appart from testing I will not be able to provide much help here.

1) That's right it works for one taxonomy field now, which is awesome !

2) It gets more complicated when using more than one taxonomy filters, just because on the first page view, all the filters are set on the first taxonomy term available, even if it's not an available term, therefore I get several messages:
An illegal choice has been detected. Please contact the site administrator.
then I select some terms, If I find an available term it's working fine.
The same thing happens when I hit reset if I enable the reset button.

3) Apparently there's no way to leave the select field on any now, is this by design? Isn't it possible to let the user leave a select list blank, when using more than one filter?

4) Side note it's important to uncheck "remember las select choice" - this seems logical. If not you have to deal with: An illegal choice has been detected. Please contact the site administrator.

5) What do you mean by Undefined index: filter-status and Undefined index: filter-type notices don't concern this module? I don't have nodereference filter and still:

    Notice: Undefined index: filter-status in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 124 of (...)/sites/all/modules/views_hacks/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).
    Notice: Undefined index: filter-type in views_filters_selective_exposed_form_plugin->exposed_form_alter() (line 124 of (...)/sites/all/modules/views_hacks/views_filters_selective/views_filters_selective_exposed_form_plugin.inc).

There's no way to reproduce the other notices mentionned above, with only taxonomy filters checked. You've made your point.

about point 2) in last comment first screenshot is on page view, second screenshot is with an user selected term. If you refresh the page, you're back to first screenshot.

first URL :
http://exposedfilters.localhost:8082/restaurants
second URL
http://exposedfilters.localhost:8082/restaurants?field_business_catering_tid=12&field_business_ambiance_tid=18&field_business_type_tid=3&field_business_prices_tid=7&city=&country=All

So the best thing would be a default behavior for the view with - any - selected for each filter when you first display the page or reset the view filters, it would correct this issue and provide an expected feature for this kind of widgets.

So in the meantime (befor this is taken into account in views) what should we do use default machine names for taxonomies? My view is still displayed as in the screenshot.
What about the - any - choice? Is it doable?

In the attached patch, I just added some cleanup, you need to provide @file blocks and to use two spaces instead of tabs. The coder module can help you to cleanup your code.

by the way what's the DAU theory?

Thank you.

Is there a problem using a menu link to the view page like this: www.example.com/restaurants
Then there's nothing in the url to trigger views filters selective like in: www.example.com/restaurants?field_business_catering_tid=11&field_busines...

Probably that's why the illegal choice hapens on first page view and page refresh. What do you think?

@neoglez: Oh yes, sorry, I had to CHECK the require checkbox ! That was it ! You did a very good work on this, than you!

I can confirm it works if :
- Require is checked (in the taxonomy term exposed filter's configuration)
- Show hierarchy in dropdown in unchecked (in the taxonomy term exposed filter's settings)
- You use taxonomy term exposed filters only, but you can use more than one of them which is great!

Hide if empty works OK!

For further improvements, the main feature requests in my opinion are:
1) Other filters:
I tried to use a country exposed filter as well but this is wired, if you select Luxembourg, it actually hides the nodes with Luxembourg instead of displaying them only, so there's a feature request for compatibility with other exposed filters but we have already your answer about in #7
2) filter not required (the - Any - option)

Everyone: thanks for your efforts to port and test this. Much appreciated.

@neoglez: Would you like to participate in Views Hacks as co-maintainer for the D7 branch?

subscribing

@neoglez: Thanks for your help! I gave you maintainer access to the module and added a 7.x-1.x tag. Go wild :-)

Neoglez, you rock!

+1 to certify to rock neoglez!
I opened new feature requests, following #16, to clarify the issue queue.
http://drupal.org/node/1184584
http://drupal.org/node/1184486

@neoglez: go wild further! :)

subscribe

Subscribe.

Tested the dev release and get a white screen after during enabling "Views Selective Exposed Filters". So waiting for a working release and take a look at the issues here :)

I used the dev from project page which doesn't work but I don't know how I can download the dev module via git...

And git clone the module doesn't work too...
This version is not compatible with Drupal 7.x and should be replaced.

name = Views Auto-refresh
description = Allows auto-refreshing of Ajax-enabled views.
package = Views
dependencies[] = views
core = 6.x

Should be wrong info file for D7 module...

I simple want to download views_hacks and not spend time in git... I read the version control tab page and cloned 7.x.1.x. Isn't up to date. No "update" command for git found. I'll wait for a new dev | stable release at d.o and maybe use the module later...

Thanks

Bookmarking, waiting for 7 dev projectpage release.
greetings, Martijn

Subscribing - also waiting for 7 dev project page release.

I'm not 100% sure this is the right module for my situation. I have two exposed filter dropdowns, and want to make one dependent on the other. The second dropdown lists nodes that are tagged with taxonomy terms from the first dropdown. So when someone makes a selection with the first dropdown it automatically updates the second dropdown. Is this the right module for me?

Thanks neoglez, that is an interesting use of filters, however I'm not sure if it fits my scenario. Many thanks for the link though.

+subscribe

It didn't work for me. I took a snapshot from Git. I installed the module (Drupal 7.7 - 7.x-3.0-rc1) and enabled it. Views showed the extra option for the filter. I also configured the exposed form to filter the results for the filter.

But the front-end didn't filter anything at all. It showed the full list.

It is close to working for me. Thank you very much, neoglez, for your work on this (and the original authors, of course). I am using 7.8 and the latest -dev of Views Hacks.

I changed my view's Exposed Form to Exposed form style: Selective Exposed Filters. In the Settings, I checked the "Limit values for the result set" checkbox for the taxonomy term reference field I was trying to limit.

I have two other exposed filters on this view that are not taxonomy terms.

When I enter the view, my select list for the taxonomy term field shows all values (even those not in the result set). When I enter a value in another filter (like "Name starts with"), then the taxonomy term filter shows only the values in the result. However, I get "An illegal choice has been detected. Please contact the site administrator."

Also, the "-Any-" choice has been removed. +1 on that feature request. I suspect that would solve this problem.

So close to working!!

... did anyone get this solved?

I just committed an updated method for selective filters. It's completely different from the D6 method, and it it works well I will backport it to D6. Here's how it works:

The module now creates a new selective filter for every registered filter that it finds in the system, e.g. Node: title (selective). Select this filter instead of the original and expose it.

Please try it (12 hours from now or from git directly) and let me know how it works for you!

Thanks a lot for this update. The module looks like more stable than before. I don't know if it is a bug or missing feature: If you select a filter for an entity type that is not a node you will get pdo exceptions.

@checker, please open a new issue describing the error that you get and attach the exported view. Ideally, the view would use nothing but core Drupal objects to allow me to reproduce the error.

Doesn't seem to work with taxonomy.

Using with taxonomy all I get in the list is "Actual values will be available at run-time"
Tried all the forms* of taxonomy term available through the UI and with/without choosing "Limit list to selected items."

• Field: MyVocab (taxonomy_vocabulary_#) (selective)
• Content: Has taxonomy term (selective)
• Taxonomy term: Term (selective)
• Taxonomy term: Name (selective)

Using in conjunction with BEF.

When used without BEF, the list is just empty.

Please open a new issue describing the problem you're having. This issue was created to request the porting of the module to D7.

Thanks. Done.
#1613358: Fatal error and bad query using selective filters with taxonomy terms.
Will thread BEF separately.

For me it works on Taxonomy terms BUT all that's shown in the drop down is the terms IDs and not the text. I've worked around this with a custom modules that replaces the text with hook_form_alter but there must be a more elegant way?