Testing Metatag Twitter cards support on a completely clean Acquia Drupal 7.22 install. When I make changes to the Global settings for Twitter cards, the changes don't trickle down to any of the subsettings pages.
For example, I changed the global "Site's Twitter Account" field, but none of the nodes, terms, user, etc. inherited it (not even the global front page). I already checked the settings, and all of those types say they are inheriting settings from Global, and none of them have been overridden. Also tested with Twitter card "type" to see if another field was also affected. Same result.
Comments
Comment #1
damienmckennaa) Are you talking about the values shown in the form fields or in the actual output?
b) Do other meta tags behave the same way or is it just Twitter Cards?
Comment #2
archimedes commentedUpon further review, some of this may be an issue with config UX instead. I was a bit confused by the way inheritance is showing. Actual output is correct (as far as I can tell).
Something that—from a user experience perspective—might also be handy is that the section of overridden tags in each "type" (metatag config) should be labelled as overridden tags. It looks like some content has tags that are overridden by default? I didn't expect to see overridden tags out of the box, so it took me a bit to understand what was going on there...I thought the tags shown in each section were tags that were inherited (not overridden).
Another part of my confusion is that it doesn't look like defaults come through on the form fields, like when editing specific content. I tested this by adding a Content Creator's Twitter account into the Global entry, but it never showed in the edit fields when I was adding or editing content (like other things do, including the defaults for title). The output, however, was correct...inheritance was happening from those defaults.
From what I've seen, metatags and Twitter Cards both work this way.
Comment #3
damienmckennaHave not been able to reproduce this problem with the latest -dev release, though beta7 did have some known problems. Please re-open if the problem persists with the latest -dev code, or beta8.