Rails locale fallbacks are not working in production env










2















I have a rails 3.2 application.
It has 2 locales ko & en.
ko is the default but I want it to fallback to en if it's not available.
The fallback works in development env but not in production env.



[config/application.rb]
config.i18n.default_locale = :ko
config.i18n.fallbacks = [:en]

[config/environments/production.rb]
config.i18n.fallbacks = true


[config/locales/en.yml]
ttt: TTT

[config/locales/ko.yml]
(ttt is not defined)


**In development console:**

I18n.localt #=> :ko
I18n.t("ttt") #=> "TTT" (Works fine)


**In production console:**

I18n.locale #=> :ko
I18n.t("ttt") #=> "translation missing: ko.ttt" (Not working)


What am I missing?



Thanks.



Sam










share|improve this question

















  • 1





    I commented out config.i18n.fallbacks = true in config/environments/production.rb. Now it works. Probably, that's not what it seems.

    – Sam Kong
    Aug 12 '13 at 17:34
















2















I have a rails 3.2 application.
It has 2 locales ko & en.
ko is the default but I want it to fallback to en if it's not available.
The fallback works in development env but not in production env.



[config/application.rb]
config.i18n.default_locale = :ko
config.i18n.fallbacks = [:en]

[config/environments/production.rb]
config.i18n.fallbacks = true


[config/locales/en.yml]
ttt: TTT

[config/locales/ko.yml]
(ttt is not defined)


**In development console:**

I18n.localt #=> :ko
I18n.t("ttt") #=> "TTT" (Works fine)


**In production console:**

I18n.locale #=> :ko
I18n.t("ttt") #=> "translation missing: ko.ttt" (Not working)


What am I missing?



Thanks.



Sam










share|improve this question

















  • 1





    I commented out config.i18n.fallbacks = true in config/environments/production.rb. Now it works. Probably, that's not what it seems.

    – Sam Kong
    Aug 12 '13 at 17:34














2












2








2








I have a rails 3.2 application.
It has 2 locales ko & en.
ko is the default but I want it to fallback to en if it's not available.
The fallback works in development env but not in production env.



[config/application.rb]
config.i18n.default_locale = :ko
config.i18n.fallbacks = [:en]

[config/environments/production.rb]
config.i18n.fallbacks = true


[config/locales/en.yml]
ttt: TTT

[config/locales/ko.yml]
(ttt is not defined)


**In development console:**

I18n.localt #=> :ko
I18n.t("ttt") #=> "TTT" (Works fine)


**In production console:**

I18n.locale #=> :ko
I18n.t("ttt") #=> "translation missing: ko.ttt" (Not working)


What am I missing?



Thanks.



Sam










share|improve this question














I have a rails 3.2 application.
It has 2 locales ko & en.
ko is the default but I want it to fallback to en if it's not available.
The fallback works in development env but not in production env.



[config/application.rb]
config.i18n.default_locale = :ko
config.i18n.fallbacks = [:en]

[config/environments/production.rb]
config.i18n.fallbacks = true


[config/locales/en.yml]
ttt: TTT

[config/locales/ko.yml]
(ttt is not defined)


**In development console:**

I18n.localt #=> :ko
I18n.t("ttt") #=> "TTT" (Works fine)


**In production console:**

I18n.locale #=> :ko
I18n.t("ttt") #=> "translation missing: ko.ttt" (Not working)


What am I missing?



Thanks.



Sam







ruby-on-rails locale fallback rails-i18n






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 9 '13 at 22:54









Sam KongSam Kong

2,29864079




2,29864079







  • 1





    I commented out config.i18n.fallbacks = true in config/environments/production.rb. Now it works. Probably, that's not what it seems.

    – Sam Kong
    Aug 12 '13 at 17:34













  • 1





    I commented out config.i18n.fallbacks = true in config/environments/production.rb. Now it works. Probably, that's not what it seems.

    – Sam Kong
    Aug 12 '13 at 17:34








1




1





I commented out config.i18n.fallbacks = true in config/environments/production.rb. Now it works. Probably, that's not what it seems.

– Sam Kong
Aug 12 '13 at 17:34






I commented out config.i18n.fallbacks = true in config/environments/production.rb. Now it works. Probably, that's not what it seems.

– Sam Kong
Aug 12 '13 at 17:34













2 Answers
2






active

oldest

votes


















4














If you comment out config.i18n.fallbacks = true in your production / staging environments it works as expected.






share|improve this answer






























    0














    Even if this question/answer is quite old, I will let here what I found for my case (Rails 5.X). The settings should look like this in application.rb



    config.i18n.default_locale = :en

    config.i18n.available_locales = %i(en de)
    config.i18n.fallbacks =
    de: :en



    And with that, all the references to config.i18n.fallbacks = true should be removed from the different environments.






    share|improve this answer






















      Your Answer






      StackExchange.ifUsing("editor", function ()
      StackExchange.using("externalEditor", function ()
      StackExchange.using("snippets", function ()
      StackExchange.snippets.init();
      );
      );
      , "code-snippets");

      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "1"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f18156860%2frails-locale-fallbacks-are-not-working-in-production-env%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      4














      If you comment out config.i18n.fallbacks = true in your production / staging environments it works as expected.






      share|improve this answer



























        4














        If you comment out config.i18n.fallbacks = true in your production / staging environments it works as expected.






        share|improve this answer

























          4












          4








          4







          If you comment out config.i18n.fallbacks = true in your production / staging environments it works as expected.






          share|improve this answer













          If you comment out config.i18n.fallbacks = true in your production / staging environments it works as expected.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 6 '14 at 14:12









          JuandaJuanda

          1,08511627




          1,08511627























              0














              Even if this question/answer is quite old, I will let here what I found for my case (Rails 5.X). The settings should look like this in application.rb



              config.i18n.default_locale = :en

              config.i18n.available_locales = %i(en de)
              config.i18n.fallbacks =
              de: :en



              And with that, all the references to config.i18n.fallbacks = true should be removed from the different environments.






              share|improve this answer



























                0














                Even if this question/answer is quite old, I will let here what I found for my case (Rails 5.X). The settings should look like this in application.rb



                config.i18n.default_locale = :en

                config.i18n.available_locales = %i(en de)
                config.i18n.fallbacks =
                de: :en



                And with that, all the references to config.i18n.fallbacks = true should be removed from the different environments.






                share|improve this answer

























                  0












                  0








                  0







                  Even if this question/answer is quite old, I will let here what I found for my case (Rails 5.X). The settings should look like this in application.rb



                  config.i18n.default_locale = :en

                  config.i18n.available_locales = %i(en de)
                  config.i18n.fallbacks =
                  de: :en



                  And with that, all the references to config.i18n.fallbacks = true should be removed from the different environments.






                  share|improve this answer













                  Even if this question/answer is quite old, I will let here what I found for my case (Rails 5.X). The settings should look like this in application.rb



                  config.i18n.default_locale = :en

                  config.i18n.available_locales = %i(en de)
                  config.i18n.fallbacks =
                  de: :en



                  And with that, all the references to config.i18n.fallbacks = true should be removed from the different environments.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 15 '18 at 13:15









                  Cris RCris R

                  656922




                  656922



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f18156860%2frails-locale-fallbacks-are-not-working-in-production-env%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      這個網誌中的熱門文章

                      How to read a connectionString WITH PROVIDER in .NET Core?

                      Node.js Script on GitHub Pages or Amazon S3

                      Museum of Modern and Contemporary Art of Trento and Rovereto