similar to: error_message_on broken?

Hello all I would like to overload the error_message_on method in the ActiveRecordHelper module in order to emit a span tag instead of a div tag. I try to achieve this by way of plugins: Under vendor/plugins I''ve made a error_messages_on_fix directory, containing init.rb like this: --- require ''active_record_helper_fix'' --- ..and a lib directory with

Leaving the body of the method the same as the default still throws the "stack level too deep" error. As a matter of fact, it only disappears if I comment out the ''require'' in line 1. As it turned out, it was the method definiton itself that caused problems. Ruby doesn''t have keyword arguments, but I tried calling the method as if it had. But when I changed

Hey all I was encountering problems with error_message_on in the fact that it caused an exception when no object by that name had any errors (or did not exsist) so i created this work around... def display_error(obj, method, prepend_text = "", append_text = "", css_class = "form_error") object = instance_variable_get("@#{obj}") if object

Hello I have a problem with relationship with belongs_to - has_one and with error_message_on I have splitted one huge table users into two tables user and profile. In users I''m keeping main fields like id,email,password and in profile there are the rest of fields. Table users: id,email,password Table profiles: id,user_id,publicname, and more ... My models are: - user.rb has_one

Hi, just a simple question between error_message_on / error_messages_for ... Well, if you use error_messages_for in your web page, there is no problem even if anObject==nil (for example , the first time you load your form) whereas error_message_on must be use with an instanciated object ... So, you always has to double check if anObject is not nil before using error_message_on ? I

Hi. I am writing an application that has a lot of boolean conditional display logic, like this: <% if user.description then %> <p class="css_class"><%= user.description %></p> <% end %> Often the displayed content is more complex than the above, and to clean up my views I am trying to pull a lot of this sort of thing into partials. However, the problem

Hello Friend, I want to override the default error message, but some how I am not able to implement it. The scenario is I have a user table and user detail table I have implement nested model. And the below mention message is appearing and instead of that I want something "User Name cannot be blank" - *User detail given name can''t be blank* Thanks Abhis -- You

Greetings, I''m in the throws of deploying an app on site5, and I''m getting strange errors. I think I might need to understand how error_messages_for works. I get a pretty standard looking error: " You have a nil object when you didn''t expect it! You might have expected an instance of ActiveRecord::Base. The error occured while evaluating nil.errors Extracted

I have a problem with translation of english phrase when an input error occurs. When I put: error_messages_for("registratie") above my view. I get the error: "xx errors prohibited this registratie from being saved". The problem now is, the site is for dutch customers and I would like to translate this to a dutch phrase. I know I can translate the individual fields with the

Hi Facebookers, Is there a helper or suggested approach for presenting validation errors on an fbml form? Something to translate rails error markup to fbml:error markup? thanks Joel

I am trying to figure out how to disable the error field thing in rails, the thing that wraps errous fields with a div (class fieldWithError). Any help on this would be great! -Ray -- Posted via http://www.ruby-forum.com/.

I have a link-to that I wish to look somewhat like this: link_to "link here", new_object_path, :method => :post, :confirm => ''Press OK'', #url options :class => "css_class", :id => "css_id" #html options In any case I can either get the url_for options to work or the html options to work, but

Attached is a patch file for listbook.rb 1) Message box scrolls properly now 2) Blank lines are skipped when adding pizzas and ice cream _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

I have a select_tag in my view that uses options_for_select with multiple = true. I am having trouble figuring out the Rails way to create and update that field. Please help. Models: ------------- Service has_many AccessControl AccessControl belongs_to Service application.rb ------------------------- $types = Array["Athens", "htpasswd", "IP", "None",

On my registration form I have a checkbox for a waiver. In the model I have the statement: validates_acceptance_of :waiver, :on => :create, :message => "must be accepted" In the view: <%= check_box_tag("waiver") %> <%= error_message_on "user", "waiver", "Waiver "%> For some reason validate is accepting everything when the

On 1/4/06, John Indra <ji.milist@gmail.com> wrote: > However, it doesn''t work for me. Following your article, I change my I have found the source of the problem. I follow the solution provided by http://blog.teksol.info/articles/2006/01/03/belongs_to-user-interface-take-ii It''s a nice solution, however it contains typo :) There is indeed no error_messages_on method,

How do I show the selected values in options_for_select? I have a Service model and a AccessControl model. When a user edits a Service I want the services access_controls to be pre-selected. Models: Service has_many AccessControls AccessControl belongs_to Service application.rb: $types = Array["Athens", "htpasswd", "IP", "None", "Other",

Hi, Here''s two blog posts for those that need to test respond_to blocks and/or are currently using simply_helpful extensively. http://blog.methodmissing.com/2006/11/22/testing-different-content- types-with-rspec http://blog.methodmissing.com/2006/11/23/using-simply_helpful-with- rspec-controller-tests - Lourens

Does anyone have view specs running on edge with simply_helpful? I tried http://blog.methodmissing.com/2006/11/23/using-simply_helpful-with-rspec-controller-tests/but it seems that was written for pre-9 versions. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070420/0bc8d366/attachment.html

Hi All I''m having some problems running my view specs when using simply_helpful. I have it semi-working via the following: module SimplyHelpfulHelper def self.included(base) base.send :include, SimplyHelpful::RecordIdentificationHelper base.send :include, SimplyHelpful::RecordTagHelper end end context "The index template" do setup do @shift =