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.

CommentFileSizeAuthor
#4 tvi-1908618-4-notice.patch1.4 KBSimon Georges
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

wimberb’s picture

After 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.

uno’s picture

Same 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.

areikiera’s picture

I'm seeing the same error, as well as a couple extra errors, on all new term pages:

    Notice: Undefined property: stdClass::$status in tvi_get_term_info() (line 282 of /home/visitr/public_html/sites/all/modules/tvi/tvi.module).
    Notice: Undefined property: stdClass::$inherit in tvi_get_term_info() (line 292 of /home/visitr/public_html/sites/all/modules/tvi/tvi.module).
    Notice: Undefined property: stdClass::$status in tvi_get_term_info() (line 303 of /home/visitr/public_html/sites/all/modules/tvi/tvi.module).

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!

Simon Georges’s picture

Status: Active » Needs review
FileSize
1.4 KB

Is it better with this patch?

Simon Georges’s picture

And ... 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.

DuaelFr’s picture

Status: Needs review » Fixed

Thanks again :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.