Problem/Motivation
While this seemed like a neat trick originally, @berdir and others found it confusing on #2212069: Non-English Drupal sites get default configuration in English, edited in English, originals not actually used if translated that the system.site language code is both used as a language code for that file itself and the default langcode for the whole site.
Proposed resolution
Introduce a default_langcode key that is used for the site default.
Remaining tasks
Do it. Ensure tests pass.
User interface changes
None.
API changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | interdiff.txt | 613 bytes | gábor hojtsy |
| #4 | 2457653-4.patch | 15.92 KB | gábor hojtsy |
| #2 | 2457653.patch | 15.32 KB | gábor hojtsy |
Comments
Comment #1
gábor hojtsyComment #2
gábor hojtsyIt is hard to tell all the instances 100% so here are the ones I found immediately. Let's see what fails with this.
Comment #4
gábor hojtsyFix config schema.
Comment #5
alexpottThis looks good. It is a hard break for existing sites but very easy to fix.
Comment #6
berdirYes, this looks good to me as well.
Comment #7
berdirUps, change record :)
Comment #8
gábor hojtsyPosted https://www.drupal.org/node/2459073
Comment #9
catchCommitted/pushed to 8.0.x, thanks!
Also speculatively opened head2head issue; #2459119: Upgrade path for #2457653 (system.site langcode).
Comment #11
gábor hojtsyThanks, published the change notice.
Comment #14
catchI reverted then unreverted this due to an unrelated regression in beta 8 so we could roll beta 9 with no schema/config changes from beta 8. Nothing to do with this issue directly.
Comment #15
siva_epari commentedComment #16
siva_epari commentedAdded #2460027 as child issue instead.