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.
When the metatags field is used with node entities, it makes sense to have the Metatags fieldsset appear in the "advanced" section, which usually appears on the Right-Hand-Side of the node.
I am not sure if I am the only one who thinks this way, but I will make a patch to see if you guys like it as well.
Comment | File | Size | Author |
---|---|---|---|
#4 | metatag-n2630068-4.patch | 583 bytes | DamienMcKenna |
Comments
Comment #2
jaxxed CreditAttribution: jaxxed at Wunder commentedHere is a quick patch to the field widget (firehose) that just adds the entire metatags form elements to the node "advanced" group. If desired, I could add a quick checkbox to the widget configuration, so that the decisions about where to put the fieldset can be made per field.
A note about the implementation:
- this is accomplished by adding '#group' => 'advanced' to the widget form element.
- the node already has an "advanced" group
- if adding the field to an entity that has no advanced group, the setting is ignored (test it with user or something)
* if attaching the widget to an entity that has an advanced group, but into which it doesn't make sense to have the metatags added, then maybe we have a problem.
Comment #3
DamienMcKennaI didn't do this already on purpose - the Metatag form will have so many meta tags that I thought it would be a bad UX. I'd be willing to accept this if there was a global setting controlling it, but not as-is.
Comment #4
DamienMcKennaRerolled as-is.
Comment #5
DamienMcKennaLets just go with this as-is.
Comment #8
mvwensen CreditAttribution: mvwensen commentedUX follow up: #2902251: Make forcing the form field into advanced region optional