# 2.3.0.beta9 へのアップグレード後の I18n.translations の問題
**URL:** https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560
**Category:** Support
**Created:** [2019 年 5 月 23 日午後 9:53 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560 "2019-05-23T21:53:11Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [2019 年 5 月 23 日午後 9:53 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/1 "2019-05-23T21:53:11Z")
Dear Discourse team,
we are currently trying to solve a problem on [https://community.hiveeyes.org/](https://community.hiveeyes.org/). After upgrading to 2.3.0.beta9, the Discourse page stays blank - probably like [Blank topics page when interface language is German](https://meta.discourse.org/t/blank-topics-page-when-interface-language-is-german/40753) - while the Javascript console yields the runtime error
```plaintext
TypeError: I18n.translations[I18n.currentLocale(...)].js.composer is undefined
```
After checking things a bit, it turns out that
```plaintext
I18n.currentLocale()
"en_US"
```
but it looks like `en_US` is not defined when looking at `I18n.translations`
```plaintext
I18n.translations
{
en: Object { js: {…} }
}
```
Bummer!
Everything works fine when switching my personal account to plain “English” after navigating to [https://community.hiveeyes.org/?safe\_mode=no\_custom](https://community.hiveeyes.org/?safe_mode=no_custom), but we fear everyone will have “English (United States)” in her interface settings which was also the default setting for me. We also deactivated all plugins to make sure its not one of them who is the culprit.
Does someone have an idea what we have been running into here?
With kind regards,
Andreas.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [2019 年 5 月 23 日午後 10:14 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/2 "2019-05-23T22:14:37Z")
Easiest solution: Switch the default locale to English (`en` instead of `en_US`).
Or make sure that your plugins and theme (components) ensure that the `js.composer` key actually exist. We recently fixed a similar issue in [DiscoTOC - automatic table of contents - #82](https://meta.discourse.org/t/discotoc-automatic-table-of-contents/111143/82).
---
### Author:  [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [2019 年 5 月 23 日午後 10:18 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/3 "2019-05-23T22:18:51Z")
> [@gerhard](#):
>
> We recently fixed a similar issue in [DiscoTOC - automatic table of contents](https://meta.discourse.org/t/discotoc-automatic-table-of-contents/111143/82).
It really looks like DiscoTOC is also responsible here, as it this very line which raises the error
```plaintext
I18n.translations[I18n.currentLocale()].js.composer.contains_dtoc = I18n.t(themePrefix("topic_will_contain_a_table_of_contents"));
```
However, I don’t quite get it because I believed to have it deactivated from the list of plugins in `containers/app.yml`.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [2019 年 5 月 23 日午後 10:19 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/4 "2019-05-23T22:19:54Z")
DiscoTOC is a theme component. You need to update it in [safe mode](https://meta.discourse.org/t/53504?silent=true).
---
### Author:  [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [2019 年 5 月 23 日午後 10:20 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/5 "2019-05-23T22:20:06Z")
> [@amotl](#):
>
> I believed to have it deactivated from the list of plugins in `containers/app.yml` .
Ah, it’s a **theme component**! I should probably update this and everything will be fine again. Sorry for the noise and thanks for bringing me on track!
---
### Author:  [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [2019 年 5 月 23 日午後 10:24 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/6 "2019-05-23T22:24:30Z")
> [@gerhard](#):
>
> DiscoTOC is a theme component. You need to update it in [safe mode](https://meta.discourse.org/t/53504?silent=true).
> [@amotl](#):
>
> and everything will be fine again.
That’s it! Of course it wasn’t in the list of plugins and updating the theme component as you suggested worked like a charm. Currently rebuilding with plugins activated.
Thank you so much!
---
### Author:  [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [2019 年 5 月 24 日午前 9:24 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/7 "2019-05-24T09:24:07Z")
> [@amotl](#):
>
> […] as you suggested worked like a charm. Currently rebuilding with plugins activated. Thank you so much!
Did we ever mention how awesome the whole Discourse team and community actually is?
With your help, we have been able to revive [https://community.hiveeyes.org/](https://community.hiveeyes.org/) quickly after the last upgrade had some minor hiccups and we are now ready to start with [https://meta.discourse.org/t/knowledge-base-plugin/115288](https://meta.discourse.org/t/knowledge-base-plugin/115288) on [https://community.hiveeyes.org/k/](https://community.hiveeyes.org/k/) – installing this plugin was the reason for the upgrade/rebuild.
Thanks again, @gerhard, @tobiaseigen, @angus and all others!
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [2019 年 6 月 23 日午前 9:24 UTC](https://meta.discourse.org/t/problems-with-i18n-translations-after-upgrading-to-2-3-0-beta9/118560/8 "2019-06-23T09:24:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.