- 🇫🇷France duaelfr Montpellier, France
I faced an issue where my field labels and some values (on list fields) were rendered in the wrong language after a
drush cr
call. I traced it back to 🐛 Clearing cache via UI in translated language resets config translation of field labels to default language Fixed then I saw this issue, so thank you for working on it!I've currently used the workaround in #2650434-77: Clearing cache via UI in translated language resets config translation of field labels to default language → but it's only working for my cache rebuild issue. Other issues explained in #12 wouldn't be affected by this workaround.
I'm outskilled here so I can only try to cheer you on! ✺◟(^∇^)◞✺
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
This is a serious problem for Drupal use in the Government of Canada since these sites are require to be in English and French without giving priority to either language.
- 🇩🇪Germany sascha_meissner Planet earth
+1 serious problem! patch#9 fixes this for me
- 🇨🇦Canada joseph.olstad
+1 also hitting this.
I enabled cachetag debugging thinking this might help lead to a solution, the language context is being passed in, everything looks normal according to the caching system debugging I did but I may have missed something.
- 🇫🇮Finland heikkiy Oulu
We discussed this issue in Slack and I tested the latest patch from 🐛 Configuration being imported by the ConfigImporter sometimes has stale original data Fixed against 10.2.6 to solve the issue. At least in our staging environment which was suffering from this issue, the patch seems to now solve it. Our symptom was that taxonomy term and select list values in frontend were showing in wrong language after Drush deployment. Previously I tried the patch from this issue and 🐛 Wrong language field labels after `drush cr` because of Drush language negotiation Needs work to solve it.
- 🇳🇱Netherlands SanderJP
I have seen the issues described here on a number of websites we maintain, where the translations are used correctly after a deploy. Some time later however the English defaults are back again.
The patch of #9 does seem to fix the broken translations after a cache rebuild. We will now test and see if the English defaults are still being reset after a while.
I'm surprised this Major core issue is hardly getting any attention at all. - 🇫🇮Finland heikkiy Oulu
I can also report the patches seemed to fix the initial language issue after deployment but like mentioned in #23 the English labels made a return a bit later. We also discussed this further in Drupal Slack and there I mentioned that the returning of the English labels seemed to have something to do with cron. When I ran the cron tasks manually on the server it seemed to have an effect on the labels. So basically running drush cr command first to fix the labels and then a cron task again seemed to revert the labels back to English.
Unfortunately I haven't been able to track a specific set of commands to reproduce the issue. I guess this issue is so hard to fix because the problem can happen in several ways and steps of the workflow.