- 🇬🇧United Kingdom nlisgo
Can someone confirm that this is an issue with 11.x? It has been 6 years since this was last confirmed.
- 🇭🇺Hungary Gábor Hojtsy Hungary
I don't think anything changed with this in the meantime.
When Drupal is installed in a foreign language or a foreign language is added on top of the English language in an install profile, Drupal imports translations. This results in two sizeable feedback messages in some cases. If all translations were imported well, some stats are reported, and if there was some format error in even one single string out of the several thousands imported, then an error is also printed.
While this reporting makes sense when a new language is added on the UI, displaying them as part of the installation process seems like too much detail. We don't display stats about config imported or modules enabled, etc. The warning (if shown) is also something the user cannot do anything about as it is about broken HTML in the .po file downloaded. The warning also makes the actual settings.php warning harder to notice and act on, causing warning fatigue.
Avoid user facing messages for imported translations except for the case of entirely missing translation files. The logging of the messages that are not displayed should still be intact.
Implement properly.
Reporting messages and warnings about invalid HTML strings will not display anymore in the installer.
No API changes. The proposed implementation fixes the finish_feedback option on locale batches to work according to its documentation and silence user messages (while still keeping logging intact).
None.
N/A.
Postponed: needs info
11.0 🔥
Umami demo
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Can someone confirm that this is an issue with 11.x? It has been 6 years since this was last confirmed.
I don't think anything changed with this in the meantime.