You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EE6: It would be extremely helpful to be able to see at a glance where a given field is used — ie. to which channels it has been assigned. This would avoid situations in which editing a field to help with one channel creates an unintended consequence because the developer had forgotten that the same field is also used in another channel. Currently there's no such overview, and one has to visit each channel individually (click to get to channel list, click the specific channel, click again to get the fields tab, probably scroll and/or expand the list of fields, click to return to main channel list, rinse and repeat… laborious).
Suggestion
An overview, somewhere in the Fields section, of the relationships between a given field and the channels it affects would be most valuable. In addition to simple direct field-channel assignments, this should include instances where:
the field is part of a field group assigned to a channel
the field is assigned to a Fluid field that is then assigned to a channel
It also should potentially reveal assignment via Relationships — where a field is assigned to a channel (including via the two additional linkage types noted above) and that channel's entries are then made available to another channel via a Relationship field.
Ideally these different types of assignment type (direct, field group, Fluid, Relationship) would be separated out and indicated so that the various ways/places in which the field is used are clearly revealed to the user.
This information could be presented either from the Fields overview list or, alternatively, at the bottom of each individual field's editing screen. Perhaps the overview screen could provide a brief summary for each field ("Used in: 3 channels directly, 1 channel via Field Group(s), 1 channel via Fluid field(s), 0 channels via Relationships") alongside the field's id number, tag name, etc, with full details then being provided on the field's own editing screen.
The text was updated successfully, but these errors were encountered:
The issue
EE6: It would be extremely helpful to be able to see at a glance where a given field is used — ie. to which channels it has been assigned. This would avoid situations in which editing a field to help with one channel creates an unintended consequence because the developer had forgotten that the same field is also used in another channel. Currently there's no such overview, and one has to visit each channel individually (click to get to channel list, click the specific channel, click again to get the fields tab, probably scroll and/or expand the list of fields, click to return to main channel list, rinse and repeat… laborious).
Suggestion
An overview, somewhere in the Fields section, of the relationships between a given field and the channels it affects would be most valuable. In addition to simple direct field-channel assignments, this should include instances where:
It also should potentially reveal assignment via Relationships — where a field is assigned to a channel (including via the two additional linkage types noted above) and that channel's entries are then made available to another channel via a Relationship field.
Ideally these different types of assignment type (direct, field group, Fluid, Relationship) would be separated out and indicated so that the various ways/places in which the field is used are clearly revealed to the user.
This information could be presented either from the Fields overview list or, alternatively, at the bottom of each individual field's editing screen. Perhaps the overview screen could provide a brief summary for each field ("Used in: 3 channels directly, 1 channel via Field Group(s), 1 channel via Fluid field(s), 0 channels via Relationships") alongside the field's id number, tag name, etc, with full details then being provided on the field's own editing screen.
The text was updated successfully, but these errors were encountered: