Hi,
This looks like an awesome module but i'm having problems with the set up.
I am trying to create a custom search with 2 parameters a) business type and b) location.
I have set up taxonomy terms for both and created a view with nodequeue of my nodes.
I then set up finder with Views Finder, tick both page and block options, find items from this view > 'nodequeue/1', select element type > 'select list', then find items by this field > 'Taxonomy: Term' .
I then repeat the element set up for the second parameter, save and check the URL and get the following error message
Fatal error: Call to a member function get_option() on a non-object in views/includes/view.inc line 1679
What am i doing wrong?
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #24 | finderbug.PNG | 6.14 KB | Anonymous (not verified) |
Comments
Comment #1
danielb commentedWhats a nodequeue? Can you try this without that and see if it makes a difference? I've found a few modules that plug in to views and what not have caused a few problems.
Comment #2
cside commentedNodequeue module just takes any number of nodes which you can specify and creates a list from it
I haven't tried with a self generated view as yet .... will create a view of all content and let you know what happens ....
Comment #3
cside commentedI may being a dummy here but i have set up a simple view listing all nodes. I have 2 x taxonomy vocabularies - Business type and Location
Then i have created a finder ,selecting my view from the 'existing views' option. Then created an element type 'select list' and then the 'find element by field' option 'taxonomy term'.
I still get the error message .....
But where do i let the finder know which taxonomy term i am looking for .....
Thanks
Comment #4
feuillet commented*subscribe*
Comment #5
danielb commentedI can't replicate this problem.
And yes it seems there is no way to restrict the term options by vocabulary without specifically hooking in and changing the choices :/ Would be great to have a field for each vocab as well as the one that is already there.
Comment #6
danielb commentedI wonder if I can make the separate vocabs thing possible by allowing different elements to be calculated from different view displays.
Comment #7
danielb commentedok it seems like this is working now, give it a crack in rc4
What you'll have to do is go into your Views admin thing and edit the view. Then you have to add more 'displays' to it (you know the 'page_1' 'page_2' things down the left?). So add a display per each vocabulary or finder element. Then go into the 'filter' settings of the display and hit 'override' so you can configure it seperate to the rest of the view - then add a filter for your vocabulary.
Then in Finder, in the element settings, pick the appropriate display to use the filters from that.
There is also an option to use a particular display when calculating the results - so you can add some filters on the results that don't affect the select lists and autocompletes choices. Don't know what you'd use that for, but it's there.
Comment #8
danielb commentedthis doesn't work as a solution when nodes have multiple terms, which is a frequent use case :(
looks like creating a filter for each vocab is going to have to happen
Comment #9
feuillet commentedSame problem here, i have Nodes with three different Taxonomies, each node can have multiple terms of each taxonomy...
Would like to have three groups of checkboxes, wher users can select the terms they are looking for and get a filtered search result with only nodes wich contains that particular terms...
Comment #10
danielb commentedThere is a solution to use hooks/themes to remove options from a particular element - but yeah it's not very practical.
I assumed views would let you pick "terms of vocab x" which was possible in Views 1 but they've changed how it works.
So I reckon the easiest thing would be to manually add those fields in with Finder Views somehow.
Also I will add CCK/taxonomy support to the Node Finder too - it's just useless without it.
Comment #11
danielb commentedtaxonomy terms for vocab added to views options
Comment #12
skizzo commentedI am updating the issue status rather than opening a new issue. Using version 1.2 (2009-08-05) and trying to set up a Finder select list element for vocabulary VocabName. Question: now that you have added "taxonomy terms for vocab" to views options, is it still required to define and use the extra view display as described in #7 ? With or without the extra display I have a problem: the select list dropdown does not show the VocabName terms, two usernames are shown instead... My setup:
Finder Type: views finder
Provides block
Find items from view (Node view, VocabName assigned to nodetype)
Element Select List
Find items by: Taxonomy: terms for VocabName
Thank you for this cool module!
Comment #13
danielb commentedNo, I don't think so, only if you believe that this is in some way useful for you.
I have no idea why you are seeing usernames in the terms field :/ I haven't had anything like that happen. Can you try resaving the element page?
Comment #14
danielb commentedHave you had any success skizzo?
Comment #15
skizzo commentedNot really... I have tried resaving, disabling other modules, changing module weights, etc... to no avail. One extra bit of info: some VocabName's terms (not all of them) are displayed correctly in the select list (instead of usernames) IF I pick the "frontpage" view instead of my user-defined node view. I will be back doing some more testing in a week or so. Again... thank you
Comment #16
skizzo commentedhi there... it must be something related to my view/display, as the very same finder will work fine (displaying the expected vocabulary terms) if I force it to use the stock "frontpage/default" view, it will stop working (displaying usernames etc... in select list) if I make it use "my_custom_view/default". I don't understand what is "wrong" with my custom view, as it's a simple table view with taxonomy fields and multiple tabbed displays, which I have been testing without problems. I also tried to play around with the view definition, and using non-default display, to no avail. Thank you.
Comment #17
danielb commentedPerhaps if you show an export of your view and of your finder (using the new version) I may see a problem?
Comment #18
skizzo commentedI can send you both exports so that you can take a quick look, I don't want to take too much of your time really... Could you please temporarily enable your contact form (or provide e-mail through my Contact)? Thanks.
Comment #19
danielb commentedYou can paste them here in a code block or use drupalbin.com or pastebin.com - just have a quick look through the output make sure there is nothing confidential on there...
Comment #20
skizzo commentedWhile trying to simplify the view for export I found out that the problem is caused by field User:name. Moving this issue's status back to fixed. I have opened a new issue: http://drupal.org/node/557094
Comment #21
Anonymous (not verified) commentedHello,
I hope you don't mind if I join in and ask a question: my goal is to have a Taxonomy filter, similar to what sandroz wants in post #9. My problem is: I'm not seeing any of my vocabulary terms in the block!
I've just installed the current version of "Views" and didn't configure anything except activating the "taxonomy_term" view (I figured I need that one? Everything is still "default" though).
Now, I have four vocabularies, and I want filtering checkboxes for all terms, grouped by my voabulary. So I set up ONE finder:
Type: Views finder
Provide block
Find items from this view: taxonomy_term
Show results on results page even before the form has been completed: yes
Match any element: yes
and have four "Check boxes/radio buttons"-elements (for each vocabulary):
Find items by this field: "Taxonomy: terms for xxx"
Allow multiple values: yes (I want to filter, matching any term)
So, from my understanding (I'm pretty new to Drupal, views, etc) this is correct. I put the finder block to the right sidebar, and I'm seeing the titles for each element, but no terms, checkboxes whatsoever, it's just blank space.
I would greatly appreciate any help, I'm really stuck here, and it looks like this wonderful module is exactly what I need... I just need it working ;)
Thank you very much!
Comment #22
danielb commentedThat sounds right :/ Have you got nodes in those categories?
Comment #23
Anonymous (not verified) commentedYes I do, I have a couple of articles, each tagged with several terms of different vocabulary. If I click on one of the terms for example (separate from any finder/view), I see all articles of that term.
So the path "taxonomy/term/" is working for each of my terms.
Comment #24
Anonymous (not verified) commentedUpdate: I'm desparate... I just don't find anything I'm doing wrong.
I attached a picture how it looks like. I DO have terms in that vocabulary, and several articles categorized with those terms.
I'm more and more thinking it has something to do with the Views, but you said yourself the default "taxonomy_term" view should do just fine, correct? Besides, for a filtering I wouldn't know how to modify that view..
Please help :(
Used: views-6.x-2.6, finder-6.x-1.3
Edit: I'm using the German language whereever possible and AutoPath, but since that doesn't effect the site structure I don't think it's relevant.
Comment #25
Anonymous (not verified) commentedAnother update: it is about the View I'm using.
Like I said I was using the "taxonomy_term" default view. Which isn't working. If I take out the arguments from that view (Taxonomy: Term-ID, Taxonomy: Term ID depth modifier), which act like a filter, I see at least my terms with checkboxes in the block. BUT, the filtering doesn't work at all, I get error messages and weird path-URLs like "/, ,,,, ,,".
Could the author please tell me how the View has to look like so that the filter works? Thank you!
PS: I tried Taxonomy browser, which is similar to what I want, but it doesn't have an auto-submit on selecting terms, so I still prefer a working Finder :)
Comment #26
danielb commentedThe view just has to display all the items you want to be findable. If you are using arguments in your view, make sure the view shows all items when no argument is supplied.
It might be better to create a custom view if taxonomy_term has some strange behaviours.
Finder doesn't use filters, it modifies the view's SQL query to add WHERE conditions.
Comment #27
skizzo commentedwill the underlying view's caching policy still be in effect?
Comment #28
danielb commentedI have no idea what that is. Got a link about that?
Comment #29
skizzo commentedI was thinking about the "Caching" setting provided in any view's Basic Settings configuration, which can be set to "none" or "time based", allowing to achieve a performance/freshness trade-off for the given view. Will a Views Finder have the same caching properties of the underlying view? About caching in general: link1 link2. Maybe developer views documentation is more specific...
Comment #30
Anonymous (not verified) commentedThank you so much danielb! It helped, I got closer.. a lot closer.
First problem was indeed that my taxonomy arguments in the view didn't show anything if there was no result. I changed it in a new view to "show all". Then I found out that those arguments do nothing at all, I can remove them from the view. I thought they are necessary..
But that alone wasn't it. My main problem was arguments that were showing in the URL. I got results like "/finder/2/ / , , / , /myterm, , , , " in the URL and hence lots of error messages.
So I enabled "Hide URL arguments on results page" in the advanced settings, and now I see the clean URL and my results!
BUT please, can you help me out with two more problems?
1. First of all, I would like to see ALL terms in the block, even if I have NO nodes associated with them. I hope that is possible?
2. I would like to use the option "Show results on results page even before the form has been completed", without a submit button. I even prefer AHAH with effects. But unfortunately, it's not working! Nothing happens when I click the checkboxes in the block, I have to have a submit-button and click it.
Any suggestions? Do I need any other modules for that? I'm just confused because that option looks like a core function of Finder.
Thank you again! i won't bother you much more then ;)
Comment #31
danielb commentedNot for a node or node view finder. The point of the node / node view finder is to find nodes - so including values that lead to no nodes doesn't work. It's actually a bit more involved than that, but effectively finder doesn't just show you a list of terms in the form, it does a search for nodes and gets all the possible terms for those nodes. I realise this design is not suitable in some cases, and is a little slower than just showing a list of terms, and it is something I may try to add more flexibility to in the future.
It is possible to manipulate the options via hooks, so you can actually add more options to the list in this way, but this requires knowledge of PHP and the Drupal API.
Another option, if you're clever you may try to use two different views displays, one that shows a few extra 'dummy nodes' you've created just to enable all the terms and is used in the finder element, and another which does not show such nodes and is used in the results.
This is a bug I think I will file a new issue.
Comment #32
danielb commentedAlso I believe there is code in Finder Views which I stole from the CCK Node Reference module that removes the cache on the view. If you can give a good reason to remove this code, please start a new issue. I don't think the views cache affects the query results, it just enables the view object to be built faster?
Comment #33
Anonymous (not verified) commentedOk thank you! That explained a lot, and I will think about this issue and how I will handle it. I like your Views suggestion.
Also, thank you for taking care of the bug! I can imagine it will work like a charm with an actual AHAH implementation.
Comment #35
shv_rk commentedHello,
I am new to drupal, can't understad the whole view thing!
I need step by step tutorial for setting up finder.
I want to create search/ filter for products based on 3 vocabularies:
Product type, Location, conditions
I am very confused with above posts! :(
would please help me?