I have 3 usability concerns with the interface for this condition:
- The list of fields is too long, and is in no particular order
On the modestly sized site i'm working on, the list has 185 in seemingly arbitrary order
- The list of fields displays machine names
Yes, machine names are unique, but labels are meant for labeling
- Most of the fields are not relevant to the selected entity.
The list should be limited to only those fields that are already associated with this entity.
To me, this is an important issue since I find myself using this condition significantly more often than any other.
An ideal solution, in my opinion, would be a two- (or three-) step process:
1. select entity (or entity type)
2. (optional) select bundle, if not apparent from the selected entity
3. select from only those fields which are actually associated with the entity and bundle.
Since the list will be so much shorter, radio buttons with labels and descriptions might even be appropriate
Comments
Comment #1
dave reidProblem with listing field labels is that different bundles can have the same field with different labels. This problem is evident in Views as well since they have to show the "also known as" information when adding a field-related field/filter/sort.
Comment #2
ptmkenny commentedComment #3
Yuri commentedI confirm that this is a practical problem especially if you have many fields in the site.
I don't see this as a feature but as a necessity, to at least make this list alphabetically sorted.
Comment #4
skwashd commentedThis is something that frustrated me too, especially on larger sites. The attached patch sorts the fields alphabetically.
Comment #5
aaronbaumanksort++
1 vote for RTBC here
Not a perfect solution, but better than the current arbitrary order
Thanks skwashd
Comment #6
dixon_Sorting is a good idea, it does indeed make it easier to use.
Patch looks good.
Comment #7
fagoThanks, committed.