ArgumentError in Opes#edit

Showing app/views/opes/edit.html.erb where line #13 raised:

wrong number of arguments (4 for 3)
Extracted source (around line #13):

10: Date de relevé
11:
12:
13: Date de l’opération
14: Montant
15: Libellé
16:
RAILS_ROOT: /Users/admin/Documents/Rails/MyMoney

Application Trace | Framework Trace | Full Trace
/Users/admin/Documents/Rails/MyMoney/vendor/rails/actionpack/lib/action_view/helpers/date_helper.rb:964:in `date_select’
/Users/admin/Documents/Rails/MyMoney/vendor/rails/actionpack/lib/action_view/helpers/date_helper.rb:964:in `date_select’
/Users/admin/Documents/Rails/MyMoney/app/views/opes/edit.html.erb:13:in `_run_erb_app47views47opes47edit46html46erb’
/Users/admin/Documents/Rails/MyMoney/app/views/opes/edit.html.erb:12:in `_run_erb_app47views47opes47edit46html46erb’

Any idea?

To make it work well, I had to replace following lines in localization_simplified.rb:
module ActiveRecord
class Errors
#Error messages modified in lang file @@default_error_messages.update(LocalizationSimplified::ActiveRecord::ErrorMessages)
end
end

by those:
module ActiveRecord
class Errors
#Error messages modified in lang file I18n.translate(LocalizationSimplified::ActiveRecord::ErrorMessages)
end
end

Thank you very much for your plugin! And I’ll be reading your other contributions on your web site!

i have now added you on RubyForge as administrator (along with casperfabricius).

You don\t have to add a patch… just apply it in the relevant file(s). Also, make sure to add the commit comment + date + author in the changelog file as well when you commit

Thanks a lot for putting effort into it :)

I will now try to make it possible to change language dynamically, I do not really know how as I hope to find a solution that can work as an option, without changing your original plugin too much. I am just looking at rubys possibilities for dynamic compilation.
Do you have any suggestions ?

I will give you commit access to the repository and want you to commit this patch in (as i’m on my way on vacation). Unfortunately i do not know your Rubyforge user account name. Please send me.

This way you will also have access to commit in future patches. (this is actually the idea of Rubinius’ Evan Phoenix and i am very inspired by opening up the code to everybody interesting to contributing :)

def error_messages_for(*params)
options = params.last.is_a?(Hash) ? params.pop.symbolize_keys : {}
objects = params.collect {|object_name| instance_variable_get(“@#{object_name}”) }.compact
count = objects.inject(0) {|sum, object| sum + object.errors.count }
unless count.zero?
html = {}
[:id, :class].each do |key|
if options.include?(key)
value = options[key]
html[key] = value unless value.blank?
else
html[key] = ‘errorExplanation’
end
end
messages = ActiveRecord:: Errors.default_error_messages
header_message = format( messages[:error_header],
pluralize(count, messages[:error_translation]),
(options[:object_name] ||
params.first).to_s.gsub(“_”, ” “))
error_messages = objects.map {|object| object.errors.full_messages.map {|msg| content_tag(:li, msg) } }

# Patch do translate variablenames with localisation plugin
# Own error messages (:message => Example) had to be translated in the validation specification (:message => _(Example))
# error_messages_string=error_messages.join(‘%’)
error_messages.each_index do |ix|
error_messages[ix].each_index do |jx|
objects.each do |object|
object.attributes.each_key do |attribute|
variable=attribute.humanize
translated_variable=_(variable) #Translation method in Localization plugin
error_messages[ix][jx]=error_messages[ix][jx].gsub(variable,translated_variable)
error_messages[ix][jx]= error_messages[ix][jx].gsub(‘confirmation’,_(‘confirmation’)) #Fix to handle password confirmation, that not is an attribute ?
end
end
end
end
# end patch

content_tag(:div,
content_tag(options[:header_tag] || :h2, header_message) <<
content_tag(:p, messages[:error_subheader]) <<
content_tag(:ul, error_messages),
html
)
else
”
end
end
end

Concerning translation of attribute names, that feature is not implemented in LocalizationSimplified.In a previous project, I used Danish model + attribute names and added the proper pluralization rules in inflections.

That worked fine, so that’s an option if you can live with translated model/attributes.

I really prefer if the plugin could be overwritten later with a recent version. And plugins work best if we can keep them pristine with no project specific changes. Therefore I wanted to be able to place the settings like L10N_LANG in more appropriate places.

Any suggestions on how I could honor that principle and still make the code work ‘out of the box’?

It is a great plugin, but I have some problem with using it as in the error messages the variable or attribute names are not translated.
I tried to do that by using my own version of full_messages incorporating localization translation method, but failed as I not know when and where you change from the original messsage to the translated
Any idea how to separate out the name of the attributes