Add Manage Fields and Manage Display links to the vocab dropbutton

hmm, really? I would like us to, consider the usecase before we draw this consistently line.

re Bojhan: Well, exact same use case than #552654: Manage Fields and Display Fields links from the Content Types operation table.
The only difference is that core ships with no default fields on taxonomy terms (term name or description have not been moved to be 'fields' in D7), but I don't think this makes those links less valid here than on the 'content types' list.

Well I understand, but to me that difference is fundamental. In a sense that - we probably do not need to expose these features, unless it starts making sense to use them? Ohh, darn - I will edit this later1

IMO the lack of consistency between 'content types' list and 'vocabularies lists' will be annoying pretty quick.
There's a 'Manage fields' page behind both, why isn't there a quicklink for vocabs ?

I had a discussion w/ Bojhan in #drupal about this. He brought up some good points.

In contrast to content types, which are nearly completely useless without fields, this is not true of any other entity (arguable for users). Adding additional fields to taxonomy terms and comments are both a 1% use case at best (http://drupal.org/project/usage/taxonomy_image shows ~3,500 / ~200,000 users, http://drupal.org/project/usage/comment_upload shows ~3,000 / ~200,000), where adding them to content types is at least a 50% use case (http://drupal.org/project/usage/cck shows ~115,000 / ~200,000 users... way more if you consider that on each one of those sites there are probably 90% of the content types using it). It therefore makes sense to me that the UI for adding fields for content types would be more prominent than adding fields to comments, taxonomy terms, etc.

I do share the consistency concerns, though. We don't want to bury this remarkable feature of Drupal 7 too deeply.

What about: display the links the moment *some* vocab has some existing fields ?

That could actually make sense. Have to ponder about it some more.

This seems to be resolved in the current build. I currently see the "Manage Fields" and "Manage Display" tabs in the taxonomy management screens (e.g. /admin/structure/taxonomy/1), regardless of whether or not any fields have been assigned to any vocabularies. I'm a little new at this but am assuming that marking "needs review" is the right action.

"Needs review" is for patches.

We should actually do this now that it's a dropbutton.

Attached adds that, plus cleans up the other dropbutton items to use Sentence case.

With patch applied:

See also: #1340500: Merge "list terms" page into "edit vocabulary" page (which will reduce this to 4 options in the button).

Attached should fix the test.

Awesome :) Can we perhaps set up some guidelines on where we do and don't show this?

#18: taxonomy-631038-18.patch queued for re-testing.

Awesome :) Can we perhaps set up some guidelines on where we do and don't show this?

Hm, could you clarify? Where we do and don't show what? What we have so far for the dropbutton pattern is http://drupal.org/node/1808594.

We don't really have a pattern for when we show "Manage fields / Manage Displays" in the dropbutton.

We don't really have a pattern for when we show "Manage fields / Manage Displays" in the dropbutton.

It should be on any dropbutton that provides operations for a fieldable entity bundle, IMO. Checking through core:

• admin/structure/custom-blocks has them.
• admin/structure/contact has them.
• admin/structure/types has them.
• admin/config/people/accounts has these operations only in tabs, because there is only one user bundle, so there is no listing where dropbuttons would be used.
• Comment fields are at (e.g.) admin/structure/types/manage/article/comment/fields, because comment fields are coupled 1:1 to content types. Not sure if this changes once comment is decoupled from node.
• Files don't have a UI.

Those are the only fieldable ones I know of.

#18: taxonomy-631038-18.patch queued for re-testing.

Updated the summary. I think this is ready?

This added manage fields & manage display links in operations for every config entity listing #2021063: Use hook_entity_operation_alter() for manage fields and manage display links, I think this one should be marked as duplicated.

Yes, it is, didn't I already close this?

Updated issue summary.