Since the Override button only appears alongside configuration data for one field, it tells the user the override applies only to that field. In fact, the Override button applies to all fields for a given display.

I screwed up some default settings on a view before I realized this.

I'm sure there are many ways to make this obvious, but some include:
-Remove settings that apply to all fields away from individual fields.
-Put explanation text below the button where it appears on the individual field settings pages.

Comments

dawehner’s picture

dawehner
Primary language German
commented

-Remove settings that apply to all fields away from individual fields.

As far as i understand views, thats not possible by design.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Closed (works as designed) 
[22:28] <dereine> merlinofchaos: is it possible to override just a single field? i guess thats not possible by design of options, right?
[22:28] <merlinofchaos> override how?
[22:28] <merlinofchaos> Oh, no it is not.

So its not possible

aren cambre’s picture

aren cambre commented
Status: Closed (works as designed) » Active

Sorry if I was unclear, but the bug is about the UI.

For example: if I'm in the Views editor and click on Fields, I see a new section below titled Page: Configure fields. The Override button in that section makes perfect contextual sense because the section and the button clearly apply to all fields.

However, if I click on an individual field, I get a section named Page: Configure field Content: field display name (field name). The UI makes it clear that this section is only about that field, except the same Override button is on the top right, and Override applies to all fields. So you have a UI that fails to communicate the difference in scope between the Override button and everything else in that section.

merlinofchaos’s picture

merlinofchaos commented

Unfortunately this isn't easily fixable; that button is placed there as a needed convenience. Without it, users have real trouble figuring out how they can override fields. And it is not feasible to override fields one at a time. There are significant complexities to doing so that convinced me to rule it out.

ManyNancy’s picture

ManyNancy commented

Just add a tooltip on the title that says it applies to all fields...

aren cambre’s picture

aren cambre commented

Change button name to Override all fields?

dawehner’s picture

dawehner
Primary language German
commented

This might be possible. I think this is a task for someone to do it, or?

esmerel’s picture

esmerel commented
Category: bug » feature

Changing to a feature request.

aren cambre’s picture

aren cambre commented
Category: feature » bug

This is a bug because the UI is miscommunicating something important.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

And won't fix as per #4.

aren cambre’s picture

aren cambre commented
Status: Closed (won't fix) » Active

Can wording be changed per #6?

esmerel’s picture

esmerel commented
Category: bug » feature
Status: Active » Closed (won't fix)

The feature works, as intended. That makes this a feature request. Merlinofchaos also said no, he doesn't intend to change it.