When first enabling this module, it was hard to get a grip on what the checkbox "Make NAT terms in TYPE node views point to the associated node rather than the taxonomy page." really means -- and that it should not be enabled for the node type for which you select NAT vocabularies.... but rather for the vocabulary 'on the other end'.

So I did a description for that checkbox.
I also noted in that description, what vocabularies are enabled for that node type. (Not NAT enabled, but 'taxonomy settings' enabled.) That helps the overview.

Lastly: if a node type has this setting enabled, it is usually the only setting that's enabled.
So I think we should check this setting too, when deciding whether the fieldset is collapsed/expanded.

(I did similar code in http://drupal.org/node/170200#comment-3205230 , but it's really a separate issue, so I split it out.)

CommentFileSizeAuthor
nat-admin-associated.patch2 KBroderik
Support from Acquia helps fund testing for Drupal Acquia logo