Posted by sun on October 18, 2009 at 11:53pm
11 followers
Jump to:
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | field_ui.module |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | DrupalWTF |
Issue Summary
I think the IA decision to put Field UI configuration pages into the context of the fieldable entity is wrong.
Here are two reasons why it won't work out that way:
- Fieldable comments: If comments are fieldable, then we want to create separate field bundles per-content-type. So where will the field management pages for comments live?
- Fieldable fields: Where is that supposed to live?
Why did we implement that Field UI IA in the first place?
Comments
#1
I'm pretty sure it was done this way because it was the shortest path to a Field UI in core because it was most similar to the way CCK's UI already worked.
I've always thought the Field UI should have a mode with an entity type dropdown list that lets you operate on all fieldable entity types from one place.
#2
#3
The comments part of this looks like a duplicate of #537750: Field UI for comments. Let's focus this one on the fieldable fields.
#4
Well, both issues can be resolved in one fell swoop, if we would introduce a generic/overall Field UI on admin/structure/fields.
That would also allow to move the kinda strange menu item "Field list" (admin/reports/fields) from Reports. (?!)
Whether we still need the contextual field ui tabs for nodes, users, and taxonomy terms then is a different question. Even more interestingly, those field management pages do not even have an own user permission... so whoever has "administer users" can alter user fields? ugh.
#5
I agree with this.
During an informal discussion with Barry, Karen and Bec on the last day of Paris DC, we agreed that a central 'Field admin' page, giving access to the 'manage fields' screens for the various bundles of the various fieldable entities, would probably be a best solution.
fieldable entity modules can then add handy shortcut links to those screens where they see fit (on the content type overview table for node fields, in the comment settings for comment fields, etc)
#6
Tagging and marking #537750: Field UI for comments as duplicate.
#7
So I think tieing it into the a general Fields UI page, is fine. But that is not the issue really, its more the issue of do we have contextual field ui links or not? I think it makes sense to have them but we do need a centralised way of handeling that, so that it doesn't cause confusion.
#8
Sub
#9
The bug is that we don't know, doesn't seem like the right argument for calling this a bug. We might need a generic page where you can manage your entities, but I think this late in the cycle - that is less likely to happen.
#10
subscribing
#11
Subscribing
#12
Even less likely to happen now, I guess.
I reopened the comment-specific issue with a patch: #537750: Field UI for comments
#13
Let's attack this in D8.
#14