I have a view with these filters:

node type = a
node published = yes
domain access = current domain
taxonomy term = exposed

this works great if the exposed filter is on the view page but if I set the "Exposed form in block" to yes then the taxonomy selection options revert to ALL terms rather than displaying just the terms actually used in the nodes in the view.

Comments

joachim’s picture

joachim commented
Status: Active » Postponed (maintainer needs more info)

This works for me -- on my test setup for this module I have a taxonomy term that is not applied to anything, and it's not showing up in the exposed form block.

Are you perhaps using other modules that may clash with this?

jday’s picture

jday commented

drupal 6.16
views 6.x-2.10

Domain Taxonomy 6.x-1.0-rc1
Taxonomy Super Select 6.x-1.0

Disabling these did not fix my problem, so I set up a bare drupal install with ONLY views, taxonomy and Views taxonomy selective filter enabled, made a list of 5 taxonomy terms, made some story nodes and applied two of the terms from the list. Created a view with an exposed terms option and selected 'exposed form in a block'.

When I'm on the home page or a node page with one of the active terms it works, (the exposed drop down only displays the 2 terms in use). However, if I'm on a node page not relevant to the taxonomy in question, or my account page, or an admin page, the drop down will list all 5 terms.

I went back to my live site to check if that pattern was the same but there is no page where the exposed block worked correctly. So I'm not sure what to make of that... any ideas?

joachim’s picture

joachim commented

> However, if I'm on a node page not relevant to the taxonomy in question, or my account page, or an admin page, the drop down will list all 5 terms.

Where is your view in that situation?

jday’s picture

jday commented

?...on another page.

It is a page view with all nodes of a certain type. In the sidebar I want a drop-down of all the taxonomy terms used in those nodes so users can filter the view down to the nodes of interest. And I was hoping that this drop down would be available no matter where you were on the site. How do you lock in those values when you are not on the view page?

joachim’s picture

joachim commented

> And I was hoping that this drop down would be available no matter where you were on the site. How do you lock in those values when you are not on the view page?

I've never used the 'exposed form in a block option'. Without this module, what does that block do when the view is not visible? It seems to me it's meaningless without it.

jday’s picture

jday commented

It provides easy access to the view content with the users preferred filter applied, like a quick search function, it's a great feature.

joachim’s picture

joachim commented
Status: Postponed (maintainer needs more info) » Active

I'm not sure it's going to be possible. It all depends on how much work Views does when it's just showing you that exposed form block. You may have to do some digging to see if how much of the handler is getting run, and how much access it has to the $view object (if there even is one in this case). I'm afraid this isn't something I have free time to devote to.

jday’s picture

jday commented

can the option values created by the filter be stored as a global variable then called with a hook_form_alter?

iztok’s picture

iztok commented

Basiclly you want to output terms that are used on nodes that should be filtered by filter before?

I am looking for a sollution like that, but only to display terms that are populated.

Some work is done here: http://drupal.org/node/564052 and http://drupal.org/node/792092, I guess HS has the same problem with "Exposed form in block" feature like this module has.