- Issue created by @poker10
- 🇺🇸United States thejimbirch Cape Cod, Massachusetts
I don't think metatag defaults can be provided from this recipe for unknown views and webform entities. It would be up to the recipe that provides the views or forms to provide the metatag default config.
I am updating this issue to be a meta issue. We should create child issues for each of the recipes that are missing the configuration.
- 🇦🇺Australia pameeela
All of these pages will ideally be nodes, we are just blocked by a core issue. See ✨ Listing pages Active
But if we can't get this done then yes we should action the child issues.
- 🇦🇺Australia pameeela
Did this only apply to the views pages? If so I think it can be closed, since all of the child issues are addressed elsewhere, but the title seems broader than that.
- 🇸🇰Slovakia poker10
My original report was about views (these are already replaced) and contact form (there is an issue to replace it too). Not sure if it is missing anywhere else. Metatags are configured for "content" with this
[node:field_seo_title|node:title], so unless we have any other config pages like the views were, I think this should probably be OK now.
