Language > Render Language setting doesn't inherit setting from master = bad UX

Created on 21 March 2024, 9 months ago
Updated 2 July 2024, 6 months ago

Problem/Motivation

All areas in views use the "Override" logic and inherit their defaults from the master view display.
Only Language > Rendering language setting breaks with this concept and that's super confusing. It also has a high risk to create hard to find bugs due to wrong configuration.

With many years of Drupal experience for example I configured this setting in the master display and was assuming it's now also inherited to the other views displays, if I don't override it. But it isn't, I had to configure this setting (which typically is expected to be the same for all displays in most cases) in each display.

Steps to reproduce

  1. Create a view, for example for Content
  2. Change the value in Language > Rendering language to a different value
  3. Add a further view display, for example a block and see there's no inheritance for the value selected in the master for this setting.

Proposed resolution

  • Consistently use the override functionality also in this area.
  • To not introduce a breaking change, set all view displays with a different value from master to overridden.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Active

Version

11.0 🔥

Component
Views 

Last updated about 2 hours ago

Created by

🇩🇪Germany Anybody Porta Westfalica

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024