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.
The per content type settings should show on the content type settings forms.
Comment | File | Size | Author |
---|---|---|---|
#12 | readme_entity-1491562-12.patch | 1.15 KB | jonathan_hunt |
#11 | readme-entity.patch | 1.22 KB | knalstaaf |
Comments
Comment #1
DamienMcKennaTagging this, it should be in the 1.0 release.
Comment #2
DamienMcKennaMarked #1791252: Disable metatags for specific content type? as a duplicate.
Comment #3
DamienMcKennaClosed #1753974: Add metatag options to vocabulary settings form as a duplicate.
Comment #4
DamienMcKennaThis already works, the UI is confusing though - you have to click "add a meta tag default" and then select the bundle to configure.
Comment #5
DamienMcKennaLets keep this open but focus it on improving the UX.
Comment #6
gregglesI found this issue while trying to figure out how to do this. One idea would be just to add this to the README.txt file. I looked in there for the keyword type and when I didn't find it I moved to the queue. Maybe Configuration item 2 in the README.txt could be improved to mention node types?
Comment #7
idflood CreditAttribution: idflood commentedNice to see that this functionality is already present. I was previously "hacking" metatags in some preprocess function to do just that, I have to admit that I never paid attention to the "add a meta tag default" link.
As greggles suggest in #6 it may be a good idea to add a note about it in the README.txt. Maybe the link text can be rephrased to be less confusing, but I have no idea about something more clear here. Another option would be to add some little text in the table #prefix to explain how to do it. Or even a line at the end of the table with a link "+ Add an entity type specific metatag default" or something like this.
So there are many possibilities to make this more user friendly but I don't know which solution is better. Ideally this should be so obvious that adding an instruction about it in the readme would not be necessary.
Comment #8
knalstaaf CreditAttribution: knalstaaf commented(Specified in readme.txt)
Comment #9
DamienMcKennaComment #11
knalstaaf CreditAttribution: knalstaaf commentedFailed testing, adding new patch.
Comment #12
jonathan_hunt CreditAttribution: jonathan_hunt commentedJust had the same experience as #6. Here's the patch from #8 re-rolled to be relative to metatag module directory.
Comment #13
jonathan_hunt CreditAttribution: jonathan_hunt commentedComment #15
DamienMcKennaCommitted. Thank you.