Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After installing the latest dev 7.x-1.0-beta1+6-dev (2013-Feb-04) I'm getting tons of errors.
Notice: Undefined property: stdClass::$inherit in tvi_get_term_info() (line 292 of /home/***/public_html/sites/all/modules/tvi/tvi.module).
Also, I have TVI configured to default to the View "taxonomy_term" with the view display "taxonomy_term - Page [page]".
Part of the problem is that TVI will not hold the setting for the View display. I would set it to Page but it would switch to Feed. The only way I could get it to hold the Page setting was to disable the Feed page within the view.
Comment | File | Size | Author |
---|---|---|---|
#4 | tvi-1908618-4-notice.patch | 1.4 KB | Simon Georges |
Comments
Comment #1
wimberb CreditAttribution: wimberb commentedAfter investigating further it appears that TVI will only use the last page in the list if there are multiple pages defined in a View. For instance if View "Test View" has Page-1, Page-2, and Page-3 then TVI will only use Page-3 no matter what page is selected.
Comment #2
uno CreditAttribution: uno commentedSame here, after extensively using TVI in D6, could not get it to work properly in D7, so I used context to exclude main content (on taxonomy page url where needed) and display a view.
It's a pitty that this fine module is so buggy.
Comment #3
areikiera CreditAttribution: areikiera commentedI'm seeing the same error, as well as a couple extra errors, on all new term pages:
I have multiple vocabularies, some using TVI, and some not. The above error is showing up on term pages where I don't have 'Use view override' checked on either the term or its vocabulary. The only way I can get it to go away is to edit the vocabulary, check 'Use view override' and save, then edit it again, uncheck it and save. Then, I have to do that for every term as well. This is a major problem particularly if auto-tagging is being used (in my case, for a blog), since I can't edit the term every time a new one is created by a client to use this workaround.
I would really like to know if others are experiencing the '$status' problem as well. Thanks!
Comment #4
Simon Georges CreditAttribution: Simon Georges commentedIs it better with this patch?
Comment #5
Simon Georges CreditAttribution: Simon Georges commentedAnd ... The problem referenced by #1 should be the same as #1907394: View display settings do not reflect actual setting. Let's address it there to clean the patches focused.
Comment #6
DuaelFrThanks again :)