Comments

hefox’s picture

Status: Active » Needs review
FileSize
561 bytes
None View

So, there may be someting more happening here --- when the field instance are later made in same request, a view was still bugged and couldn't figure out what catch to clear. But switching to this seemed to totally fix it.

hefox’s picture

FileSize
523 bytes
None View

That didn't work and had unintended conscquences (defaulting to bundle group broke), so instead how about not have views integration for a field with no bundles?

hefox’s picture

FileSize
613 bytes
None View

Various other's call this function without checking if it returns a result, so return array(); instead of null to satisfy them

joseph.olstad’s picture

Category: Bug report » Support request
FileSize
1.24 KB

oops, see next comment with new patch.

joseph.olstad’s picture

garbage in, garbage out.

use this patch to find out what the garbage is.

joseph.olstad’s picture

If someone did want to patch views, in the case that

!isset($this->definition['group'])

views should actually write a watchdog message notifying that the field named

$title

is causing the Undefined index: group in views_handler->ui_name()

usually caused by a previously deleted or invalid field that may be hidden to the UI, but shows up in the view export.

The last submitted patch, 4: debug_2411922_find_the_culprit.patch, failed testing.