CODEWITHSUNDEEP
ruby-on-railsrubyruby-on-rails-3ruby-on-rails-3.1
hyperrjas
hyperrjas

Reputation: 10744

How can I use i18n for my error pages in Rails 3?

I need use the I18n api on my public/404.html page.

If I add to 404.html page:

<%= t('.page_were_looking') %>

I get an error message like:

Cannot use t('.page_were_looking') shortcut because path is not available

How can I use the I18n feature to this page?

Upvotes: 8

Views: 2319

Answers (1)

Robin
Robin

Reputation: 8498

Rails supports multilinguality by serving up error pages with a path like public/500.de.html, where de is the locale. It makes no sense, to use i18n for that case when Rails itself is fundamentally broken. If Rails is that much broken to get the right localized error file, it or probably the server will serve public/500.html.

This was introduced in Rails 2.3.1

There is the solution to generate this static files with a rake task, before you deploy the app. Have a look on this gist.

Upvotes: 12

Related Questions