Meta tags are not output in the HEAD

Do you have fresh install of 1.2 or upgrade from previous version?
In case this is upgrade, please run update.php - meta_name should be filled automatically.

Other steps that can help (while I still cannot reproduce this bug):
1. Clean drupal cache: admin/config/development/performance
2. Enter field configuration screen and press save.
If this does not help, I will need more info...

Hej,

I had the same message but after I've deleted the cache, the message was gone. Now I have only the problem that I have created a taxonomy meta description. I do not know if it has to do with the error message, but the meta description does not appear he always takes the meta description of a node.

I hope I've done everything right. The data are stored in the newly created field. just not displayed.

what is more interesting perhaps, I have an update done by metatags_quick 7.x-1.0-beta4 to metatags_quick version 7.x-1.2

A link to my site is in my profile. I hope this helps a bit further.

nice greetings
drew

Is that issue still actual?

sorry my late response,

the error message is gone for me now but I still have the problem with the meta description for the taxonomy as I said I don't know if it has to do with this problem.

nice greetings
drew

I have a similar problem, and it stems from the way that the module is iterating over the entire entity looking for meta tag fields, rather than just getting a list of the fields to iterate over and then iterating over those fields if they exist on the entity.

Patch is on its way...

I've attached a new style patch file, and a --no-prefix option for those of us that use drush make.

Thanks Steven.
I think your approach is better than currently existing.
Regretfully, I cannot tell if patch helps to solve this particular issue, since I cannot reproduce it on my PC even before applying the patch. Did it solve it for you?
Also, I change issue title to better describe the problem.
Regards,

My meta tags were printed correctly for the node I tested, and it was no-longer causing errors with my user object that had properties that looked like fields enough to cause an error.

Submitted. Once again, thanks Steven