Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
22 Jan 2015 at 00:09 UTC
Updated:
13 Mar 2019 at 23:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
hefox commentedSo, 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.
Comment #2
hefox commentedThat 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?
Comment #3
hefox commentedVarious other's call this function without checking if it returns a result, so return array(); instead of null to satisfy them
Comment #4
joseph.olstadoops, see next comment with new patch.
Comment #5
joseph.olstadgarbage in, garbage out.
use this patch to find out what the garbage is.
Comment #6
joseph.olstadIf someone did want to patch views, in the case that
views should actually write a watchdog message notifying that the field named
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.
Comment #8
mustanggb commented