When I go to Administration » Reports » Field list, I see these errors...
Notice: Undefined index: comment_node_panel in _field_ui_bundle_admin_path() (line 325 of /home/workfl5/public_html/drupal/modules/field_ui/field_ui.module).
Notice: Undefined index: comment_node_panel in field_ui_fields_list() (line 35 of /home/workfl5/public_html/drupal/modules/field_ui/field_ui.admin.inc).
Notice: Undefined index: comment_node_blog in _field_ui_bundle_admin_path() (line 325 of /home/workfl5/public_html/drupal/modules/field_ui/field_ui.module).
Notice: Undefined index: comment_node_blog in field_ui_fields_list() (line 35 of /home/workfl5/public_html/drupal/modules/field_ui/field_ui.admin.inc).
Notice: Undefined index: blog in _field_ui_bundle_admin_path() (line 325 of /home/workfl5/public_html/drupal/modules/field_ui/field_ui.module).
Notice: Undefined index: blog in field_ui_fields_list() (line 35 of /home/workfl5/public_html/drupal/modules/field_ui/field_ui.admin.inc).
Is there a fix for this?
Kerke
Comments
You are probably getting this
You are probably getting this because of field types that were added, then deleted?
If that is the case you can try running cron a few times to see if it clears out the deleted fields - I've found it's spotty but sometimes works. In the end I've usually resorted to manually deleting the field instances marked as deleted in field_config and field_config instance.
See these for more info:
http://drupal.org/node/1357792
http://drupal.org/node/1530812
http://drupal.org/node/686938
,,,and lots of others. just google https://www.google.com/search?q=+site:drupal.org+Undefined+index:+commen...
I'm unique, just like everybody else.
If I helped, please pay it forward, backward or sidelong.
Thank you NotGoddess, I've
Thank you NotGoddess, I've read many of the Drupal forum and Google posts on these errors from as long back as 2010 and 2011. But I've found lots of conflicting info and workarounds on how to handle these field errors. Being relatively new to Drupal, I'm not sure if I should just ignore these errors as I see many many users reporting the same issue consistently for the past few years and not finding a definite clear fix for it.
Kerke