After enabling TVI and setting up my vocabulary that I want to use a different view (a clone of default taxonomy view, with different fields) for, I'm getting the following error on all of the other vocabularies:
Notice: Trying to get property of non-object in tvi_render_view() (line 185 of /home/xxxxxx/public_html/xxxxxx/sites/all/modules/tvi/tvi.module).
And the view is failing with no results, title, etc.
The vocabulary that I setup is working fine with its custom view, but the rest have broken. I find this strange as the module states that it doesn't interfere with non-overridden vocabularies... and I can see that other others have the box un-ticked on the vocabulary edit page.
Any thoughts on what's causing this?
Thanks
Comments
Comment #1
Adam Wood commentedIt turns out that I have to explicitly define the default view to use for each of my vocabularies, regardless of whether the box it ticked or not.
This isn't great when you have over 50 vocabularies!
Comment #2
cllamas commentedhi, i have the same problem, did you figured it out? could you help me?
Comment #3
mmtahir commentedI am having the same problem, it is really difficult to edit all taxonomy terms and setup for default behaviours.
Has any one worked on it? or is there any work-around or a patch? Please help!
Comment #4
jerry commentedIt seems to me that line 185:
is guaranteed to fail due to this logic above at line 170:
Under the circumstances, line 185 likely should be:
Comment #5
majusz commentedHaving a similar problem here. I used TVI to assign a specific view to a vocabulary, which worked great first.
Afterwards I assigned a different view to three single terms in that vocabulary. The effect was that the rest of the vocabulary didn't show up at all when you tried to access the page.
Seems to me like if you assign a view to a single term, all views you assign to whole vocabularies won't be used - which is really annoying if you have vocabularies updated automatically, and you have to assign a view manually for each new term.
Comment #6
duaelfrCould you please fill another issue majusz, this one is quite old and may not be related as the code in #4 has been fixed in the last dev version.