Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Use case:
You need to replace the default "en" language with something like "en-003" and have a profile-driven workflow where you are reinstalling the site many times.
Right now, if you have system.site.langcode set to a custom language value like "en-003", you get this error when you install:
"The en-003 translation file is not available at the translation server"
To reproduce:
- Make a custom language like en-003
- Set this as the default language
- Set system.site.langcode to en-003
Problem:
Drupal assumes that any language you set as default must have a translation. I'm not sure this is a good assumption: a site might want to set up region-specific languages before the translation exists so that in the future they won't have to batch update their content.
Solution:
I propose that if we detect a custom language, we reduce the translation-file-not-available requirements violation to REQUIREMENTS_INFO rather than REQUIREMENTS_ERROR in install.php.
Patch forthcoming.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2756577-custom-lang-installer-exception.patch | 1.79 KB | dpolant |
Comments
Comment #2
dpolant CreditAttribution: dpolant at Mediacurrent commentedHere is the patch.
Comment #3
dpolant CreditAttribution: dpolant at Mediacurrent commentedComment #15
cilefen CreditAttribution: cilefen commentedI am closing this support request because there have been no recent comments.
It seem as if this should have been a bug report.