Can I cut down on # of faceted search environments by using Views integration?
| Project: | Faceted Search |
| Version: | 5.x-1.0-beta3 |
| Component: | Views integration |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I am loading multiple faceted search environments on the same page using a tabs panel style mini-panel to display the guided search blocks. Unfortunately, there's a kind of "namespace collision" that's occurring since some of the faceted search environments are only set to apply to particular node types. This makes the faceted search environments farther down the page not load at all.
Currently, I'm working around this by creating special faceted search environments for the page which have all node types available to them, but which have different taxonomy vocabularies available. This is not ideal, since they could theoretically return irrelevant results; however, since I have different taxonomy vocabularies on the node types in question, this doesn't generally happen.
So I'm wondering: Is it possible to use the views integration to display multiple guided search blocks, which use the same faceted search environment, but with additional filters provided by views? Or is each faceted search environment only limited to displaying in one view?
Thanks again for this great module! Now that I've spent a month debugging the Views table prefix issue, I've really grown to appreciate (though not necessarily understand) its API.

#1
Normally, you should be able to use more than a single environment per page, but I have to admit that I haven't really tested this in the last few releases. We probably need to fix that if it doesn't work anymore.
Each environment is limited to a single view for search results.
#2
Just found this issue in the queue, which I had overlooked, which was apparently preventing multiple environments per page.
#3
Thanks for letting me know about the fix. I'll see if this allows me to cut down on the number of environments I have.
I thought that each environment was limited to a single; just wanted to confirm.
#4
It worked for me, thanks. Closing this...
#5
Automatically closed -- issue fixed for two weeks with no activity.