As per http://dev.rubyonrails.org/ticket/5012, calling <%=
error_messages_for ''foo'' %> produces the following error
consistently:
wrong number of arguments (2 for 1)
I''m running the latest Edge. Anyone else seeing this?
--
Posted via http://www.ruby-forum.com/.
Apparently Analagous Threads
- Why does error_messages_for take string as param?
- rails:freeze:edge task is broken [updating to 2.0]
- Problem w/ error_messages_for: wrong number of arguments?
- Having problems with edge rails
- error_messages_for - different controllers, one view [revisited]
Wisdom of the Ancients
