Undefined index

1+

same here, since upgrade to 7.x-2.2

I think that the problem is broader than just missing check in metatags_quick.
I have checked core function field_default_view() and it assumes that $field['type'] is set.
So, adding extra check in hook_field_access() implementation (line 119 mentioned in error message) won't help.
I wonder how it can be that $field['type'] is empty. Probably, it is better to find the reason, instead of suppressing error messages

if i reinstall the module from 0.......fields from content types will not dissappear???? This is not a practical solution.

Did you run update.php after module upgrade?

same issue here:

• After un-install and deinstall metatags_module the database looked clean and the tables of the module and all meta_fields where removed.
• After clean installation of the metatags_module this error appears:
  

  Notice: Undefined index: options in metatags_quick_field_instance_settings_form() (regel 386 van /home/jawiweb/public_html/sites/all/modules/metatags_quick/metatags_quick.module).

1. After clearing cache, running update script or cron; the error remains the same.
2. Creating a meta_keywords field with check_boxes give error:
   

   Warning: explode() expects parameter 2 to be string, array given in metatags_quick_field_widget_form() (regel 411 van /home/jawiweb/public_html/sites/all/modules/metatags_quick/metatags_quick.module). Warning: Invalid argument supplied for foreach() in form_type_checkboxes_value() (regel 2249 van /home/jawiweb/public_html/includes/form.inc).

3. Also when selecting standard input for the meta_keywords field these values will not be stored; and other path_bases values for this meta_keywords field don't store.

I'm trying to find out how to resolve the Undefined index error.

i run update.php since a long time, and nothing changed.

Status changed, since is not fixed.

#8: please read #2. I don't think this issue belongs to metatags_quick, but not to the core

that's it, i didn't (and don't) understand #2. XD

So it's core and not the module....

Yes, this belongs to core, not to module

Same messages here.
Just upgraded from core version 7.9 to 7.10. Still get this error with each node page display.

Same error here. I get the error when I access or edit some nodes, not all of them.

Ok, solved after running cron and clearing the cache.
---
I don`t know why it worked only that time.
I needed to uninstall this module for my site to work.