gravityBites → created an issue.
Thanks again for all your help. Everything is fixed and now working as expected. However, I had to uninstall the recipe module in order to uninstall the RDF module, as the recipe module was dependent on it. But I managed to recreate the recipe content type and am pretty happy with it. I now have to start re-entering the recipes, but fortunately, I have only had twelve entered so far, so it won't be a huge task.
Thank you so much for your help in this matter.
I will do as you suggested, add default configurations for each content type and remove the RDF module.
If I run into any further issues with Metatags, I will be sure to ask.
As an added question:
I've noticed the Schema.org module outputs in the<script type="application/ld+json"></script>both the "@type": "Recipe", and "@type": "Article", in the Article and Recipe content types. This causes errors in my Rich Results Test. For example, an article will contain the "@type": "Recipe", and then provides empty recipe tags that Rich Results Test doesn't like. How can I stop the module from producing both the "@type": "Recipe", and "@type": "Article", in all content?
gravityBites → created an issue.
You are correct. I figured it out last evening. I created a parent term, "Blog Tags," in the "Tags" Vocabulary, then added "PersonalBlog" as a subterm under "Blog Tags," and everything works now.