Loading config overrides (e.g. translations) in listings should be configurable

Created on 18 May 2022, about 2 years ago
Updated 16 May 2024, about 1 month ago

Problem/Motivation

The change introduced in #2136559: Config entity admin lists show configuration with overrides (eg. localized) makes the site administration confusing/harder is some situations.

Steps to reproduce

Real life example:
- Site should be German
- Many of the site developers do not speak German
- Site editors (the client) do not speak English. Showing any English text to the site editors is not desired.
- The site editors can manage taxonomy terms, can access vocabulary listing page, but can't edit vocabularies

To make everyone's life easier, the site is configured as
- config is translated from English to German
- developers understand that the config edit form shows the config in source language
- developers can switch the language, and use Drupal in English
- site editors can use Drupal in German language only

The problem:
- site editors see vocabulary names in English on the vocabulary listing page

Proposed resolution

Make the config listing language configurable.
Allowed language options:
- Config source language (This is how it works currently)
- Current language (The proposed new option)

Or to make it technically accurate, the options should be:
List config entities:
- without config overrides
- with config overrides

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Feature request
Status

Active

Version

11.0 🔥

Component
Configuration entity 

Last updated 3 days ago

Created by

🇭🇺Hungary Pasqualle 🇭🇺 Budapest

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024