Databases
StackOverflow2013
Postsdbo
PODevise looking for wrong locale on Rails 4.0.2
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODevise looking for wrong locale on Rails 4.0.2
    primarykey
    data
    text
    <p>I've just updated to Rails 4.0.2 and I got the deprecation warning:</p> <pre><code>[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message. </code></pre> <p>To get rid of the warning, I decided to set: </p> <pre><code>I18n.config.enforce_available_locales = true </code></pre> <p>in my <strong>config/application.rb</strong> file.</p> <p>It worked pretty well on Development, all tests passed, and I was happy... Then I deployed my work in a staging server and it crashed!</p> <p>Devise is looking for a locale <strong>:pt</strong>. All I have is a locale <strong>:pt-BR</strong>. I set it in my <strong>application.rb</strong>:</p> <pre><code>config.i18n.default_locale = 'pt-BR' </code></pre> <p>I don't know why devise is looking for <strong>:pt</strong> only. My locales in the <strong>config</strong> folder are: <strong>pt-BR.yml</strong> and <strong>devise.pt-BR.yml</strong>.</p> <p>I tried to change the file name from <strong>devise.pt-BR.yml</strong> to <strong>devise.pt.yml</strong> (and inside from pt-BR to pt) and it worked.</p> <p>I had to go back and set:</p> <pre><code>I18n.config.enforce_available_locales = false </code></pre> <p>to make it work.</p> <p>I have two questions:</p> <p>1 - Why this is not happening on the tests and on development?</p> <p>2 - Why Devise is asking for <strong>:pt</strong>, if I'm setting the default locale as <strong>:pt-BR</strong> in my config?</p> <p>Thanks in advance</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMauricio Moraes
    1. USMauricio Moraes
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COAre you using devise-i18n as well or just devise? It may be that devise is looking for strings that are not defined in your locale files, and so is falling back from pt-BR to pt, triggering the error. devise-i18n includes pt-BR, so assuming it's complete, adding it to your Gemfile would avoid this issue.
      singulars
      1. PODevise looking for wrong locale on Rails 4.0.2
      1. USPeter Goldstein
    2. COThat worked fine! I added the gem and it worked. Thanks! But I still don't know why it is not appearing in development mode... Any idea?
      singulars
      1. PODevise looking for wrong locale on Rails 4.0.2
      1. USMauricio Moraes
    3. COJust posted my thoughts as an answer, along with the content of my previous comment.
      singulars
      1. PODevise looking for wrong locale on Rails 4.0.2
      1. USPeter Goldstein
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload