Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Manual tests confirm that the field formatter is actually required for an entity's overridden meta tags to be rendered. Rearchitect the meta tag output so that it could e.g. run as a service that determines if the current path is an entity and looks for its meta tags.
Comments
Comment #2
sluceroBased on my initial testing it appears that without the field rendered on the page the entity-specific meta-tags are not added to the page.
Comment #3
DamienMcKennaThat might explain some of the support requests & bug reports that have come in.. I wonder if there's an easy way to force the field to always be rendered, e.g. if the display settings are changed to not render the field that it forces it back again? Maybe changing the name to something more clear would be a starting point, "Output meta tags" or something?
Comment #4
DamienMcKennaIt also seems like there needs to be some testing around the output of entity templates, Jason Want's testing seems to indicate that if {{ content }} is not output that the meta tags might not output either. Bummer.
Comment #5
DamienMcKennaLets refocus this on restructuring how the meta tags are output.
Comment #6
DamienMcKennaBumping this to a major task, but it might not get done before 1.0.
Comment #7
DamienMcKennaMarking this "postponed" as I won't be looking at it until after 1.0.
Comment #8
DamienMcKenna8.x-1.0 is out, so this is fair game again.