Taxonomy argument not valid: Error "Notice: Undefined index"

Same error: taxonomy argument not valid =>
Notice: Undefined index: nid in views_handler_field_term_node_tid->pre_render() (Line 80 of publicweb/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).

pre_render shouldn't be runned for empty views.

The real bug behind this issue should be solved in 6.x-3.x first and ported later.

The patch was created against 7.x, but the changes was in a file which shouldn't have changed.
You can mark this issue as "needs work" if the patch didn't applied.

Works great - no more errors.
Thanks

I have the same problem with Views 7.x-3.x-dev.
Is the mentioned patch already in the newer devs or do I have to use the patch?

Before asking whether this patch is for 7.x-3.x, too you should

a) Test the patch with 7.x-3.x
b) If the patch applies you could mention it
If the patch doesn't apply you could mention it too.

Patch tested with Views 7.x-3.x-dev from Mar-14:
Error message "Undefined index: nid in views_handler_field_term_node_tid->pre_render()" is gone.
No other negative effects found.

when will be this patch committed?

Assign to review.

Hi,

I'm also having this problem and will apply the patch.

However, for all new users of this module, do we have a date to get this patch committed ?
How can we help to make this happen ?

Thanks

Just in general there is no a HARD date when something is commited but sure you can help.

• Test the patch, whether it works as expected
• Review the patch and have a look whether the code looks right
• Make it easy to reproduce the bug, for example by providing a detailed step-by-step guide.

You know there are SOOO many issues in views, a notice, which is not an php error, isn't that mission critical :)

I love the idea that it's a notice and harmless but I also love the idea that it's easy to fix... => quick win?

This is the only patch I have to manually merge to ensure our system doesn't break due to the 'notice'. It's an incredibly bad experience for users/admins to see 'error looking' messages whenever editing or creating a view.

Note: this also happens on the latest dev version (7.x-3.x-dev).

I have tested this patch on 7.x-3.x-dev and it works fine.
Works for #13 , #8 and #5 ==> RTBC

@dynamicdan #13: at admin/config/development/logging (path for D7) , you can set the watchdog-messages that appear on screen - so you can avoid notices showing up.

@dereine #4: IMO bugs should be fixed against latest version ,and then backported? You state otherway around.

Sadly the patch doesn't apply for me to 6.x-3.x anymore.

I don't have time to setup a clean diff, but here's how to manually fix this based on the patch supplied by deriene in #2

Note: Tested and works marvelously with views-7.x-3.1

1) Open up /views/includes/view.inc

2) Search for the lines
"// Initialize the style plugin.
$this->init_style();"

3) Add this statement directly below:

if (!empty($this->result)) {

4) Search for "$this->display_handler->output = $this->display_handler->render();"

5) Add this curly bracket directly above

}

6) Hit reload on your view. If you get a white screen of death, you haven't put the if statement in the right spot. Try again.

Josh

Thanks joshmiller, it's working for me

The patch from #2 is outdated with latest -dev.
I am not sure if it is necessary anymore, given the fact that is is from March 2, 2011.

This appears to be fixed in 7.x-3.x -- can't reproduce the error and I find more logic here than last I saw...

see Line 985 in views/includes/view.inc:

   // Arguments can, in fact, cause this whole thing to abort.
    if (!$this->_build_arguments()) {
      $this->build_time = microtime(TRUE) - $start;
      $this->attach_displays();
      return $this->built;
    }

I believe this fixed the original issue.

error still there

Same here, choosing as Action to take if filter value does not validate Display content of "No results found"

#16 This works for me . Is it going to be commited?
thanks

I created a patch based on #16.

I have tested the patch for 7.x-3.x-dev and 7.x-3.5.

I seem to be getting this error message when trying to write a custom validation function for an exposed taxonomy term in a view.

The error is the same as above and having googled it this is the only thread I can find with the same error and the above patch doesn't solve on views 7.x-3.7+22-dev

Thanks

Getting same error on taxonomy term view page. I looked at patch #16 and for version 7.x-3.8 the if statement in view.inc is not necessary. A simple check took care of this issue.

if(isset($this->aliases['nid'])){
      $this->field_alias = $this->aliases['nid'];
    }

Although this is the less intrusive approach, dawehner explicitly says in #2 that pre_render should not run at all for empty results.

The patch from #29 still applies to the latest release (and solves the issue for me), so setting to RTBC.

I ran into issues with #29 on a site. Views pages that did not return any results turned into white pages. I haven't fully debugged yet, but the result for the menu callback was null with the patch, resulting in the entire page to not be generated.

Actually, #29 does *not* implement #16. #16 says to put the line $this->display_handler->output = $this->display_handler->render(); outside the if statement, thus executing this line also when the result set is empty. The patch puts this line within the if(), hence the empty page callback result, presumably. Attached is an alternative patch that puts the render-line outside the if. It solves my issue.

+1 on #34 - worked for me - thanks

The 3 year old patch in #34 to view.inc applied cleanly to the latest views 7.x-3.x-dev

Version change only

Attached patch for views 7.x.3.22

i am getting this error on exposed_validate() function and not pre-render() function

Notice: Undefined index: field_study_project_tid in views_handler_filter_term_node_tid->exposed_validate() (line 340 of /var/www/html/sites/all/modules/contrib/views/modules/taxonomy/views_handler_filter_term_node_tid.inc).