Browse files

Fixed incorrect examples of ActiveRecord error message lookup in the …

…I18N guide [Thanks Alex Fortuna]

See http://www.ruby-forum.com/topic/179273
  • Loading branch information...
1 parent a6f1e42 commit 61656cf7702f46fcbb810a70bf0298ac5ea6c0d3 @karmi karmi committed Mar 1, 2009
Showing with 5 additions and 5 deletions.
  1. +5 −5 railties/guides/source/i18n.textile
View
10 railties/guides/source/i18n.textile
@@ -705,20 +705,20 @@ end
The key for the error message in this case is +:blank+. Active Record will lookup this key in the namespaces:
<ruby>
-activerecord.errors.messages.models.[model_name].attributes.[attribute_name]
-activerecord.errors.messages.models.[model_name]
+activerecord.errors.models.[model_name].attributes.[attribute_name]
+activerecord.errors.models.[model_name]
activerecord.errors.messages
</ruby>
Thus, in our example it will try the following keys in this order and return the first result:
<ruby>
-activerecord.errors.messages.models.user.attributes.name.blank
-activerecord.errors.messages.models.user.blank
+activerecord.errors.models.user.attributes.name.blank
+activerecord.errors.models.user.blank
activerecord.errors.messages.blank
</ruby>
-When your models are additionally using inheritance then the messages are looked up for the inherited model class names are looked up.
+When your models are additionally using inheritance then the messages are looked up in the inheritance chain.
For example, you might have an Admin model inheriting from User:

0 comments on commit 61656cf

Please sign in to comment.