similar to: errors_for

Hi all, I am trying to change the default formatting for the error_messages_for. To quote from the ROR manual: /////////// error_messages_for(object_name, options = {}) Returns a string with a div containing all the error messages for the object located as an instance variable by the name of object_name. This div can be tailored by the following options: header_tag - Used for the header of

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''m having a problem, ''cause I wrote the following line in my model "Hi": [code] validates_numericality_of :phone, :only_integer => true, :allow_blank => false, :message => "must be a number" [/code] And in my "new" view, I put: [code] <%= error_messages_for :oi, :header_message => "Erro ao cadastrar

In iteration D.1 on page 109 I am not getting a styled error message box displayed at the top of the checkout as described in the tutorial and I cannot seem to discover where I have erred. The scaffold.css is copied from the pragmatic programmers site: #-------------------------------------------------------------------- $ cat public/stylesheets/scaffold.css body { background-color: #fff;

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

Hi, I would like to ask how to override validation functionality in RoR? In active_record_helper.rb class there is "hardcoded" default html generated durning validation. If I will use {code:ruby} validates_presence_of :summary, :description {code} in my model class, there is html generated: {code:html} <div class="errorExplanation"

Hi, I think the columns and table in migration should be able to have an optional "display_name" set manually. Something like: create_table :people, {display_name => "Personne"} do |t| t.column :first_name :string, :display_name => "Prénom". end Let me explain my point of view: Rails is a framework made to write programs in English. You see it when you

Hi all, I have a ajax form creating by "form_remote_for", whose url is to create a new model by default. The page doesn''t change after the ajax call on submit button so the form is still there after the new model is created. But if I submit the form for the second time, I want to update the formerly created model using an Ajax post. I think I could render an rjs at the end of

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 everyone here i go again, i have problem we error message validation here is the sample of my code: error_messages_for :user, :header_message => ''X errors, please find red mark'', :message => ''Following errors were found:'' the problem is that how where going to get the value "X errors" or the number of errors if they have when the is

Hey All ! I have a form which contains two models. I would like both models to be validated, but have their validations aggregated on the page. If I do: <%= error_messages_for(:model1) %> <%= error_messages_for(:model2) %> It puts two big validation blocks on the page. I would like all the errors from both models, but only in one validation box. Is this possible ? All my attempts

I cannot work out why this error is appearing. ActionView::TemplateError (can''t convert ActiveRecord::Error into String) on line #3 of app/views/button/_show_enquiry.html.erb: 1: <h1>Send us a message</h1> 2: <% remote_form_for :enquiry, :url => {:action => ''send_mail''} do | f| %> 3: <%= error_messages_for ''enquiry'',

Is there a trick to using control_for in forms? I''ve been trying to make a simple form with a couple of text fields and I keep getting a unknown method error. Thanks!

Hi all, I tried to implement the error-message-for-Method with German output, but it don''t works. Here my code: <%= error_messages_for(''permission'', :header_message=>''%d Fehler beim Speichern'') %> Anybody an idea what could be wrong? Greets -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You

I don''t have a blog, but wanted to share this little bit of code with other semi-beginners like myself who are still learning to take advantage of rails features. Selecting an attribute with a boolean switch is a common pattern in forms. You can do it with a check box, but radio buttons are more expressive in some situations and better convey to the user that they are making a mandatory

Hi guys, I just upgraded to the latest version of Rails 1.1 and am getting some odd error messages. Specifically, I have the line: <%= error_messages_for ''user'' %> at the top of one of my .rhtml files and of course a variable @user. When an error occurs when saving ''user'', instead of getting the error message (which happened fine in Rails 1.0), I now

I''m using the latest trunk of 1.2-ish, and I''m wondering how to do what I want to do. I am using a form_for :builder I wrote, simply called TableFormBuilder after the rails cookbook, and want to be able to present help icons automatically. I want these icons to appear next to form fields I am rendering. For example, I have this method in helpers/table_form_builder.rb: # This

(this is my first post on the ruby forum. If this is not the right place for this type of question please let me know). Ajax question I have a checkbox that toggles the visibility of another element (a text field) with the code: --- <p><label for="checkbox">Appear!</label> <%= check_box :object_name, :method, :onClick =>

Hi all The following scaffold creation form code... <%= start_form_tag :action => ''create'' %> <%= render :partial => ''form'' %> <%= submit_tag "Create" %> <%= end_form_tag %> ...creates this HTML colde: <form action="/en/bookings/create" method="post"> <!--[form:artist]-->

Hi ActionView::Helpers::FormHelper methods (e.g. #text_field, #check_box...) take object_name as an argument. From this argument they infer a name that is supposed to contains the reference to the relevant object. I can''t see why the FormHelper methods were designed that way. Compared to simply passing them a reference, the current way seems too complicated and an invitation to problems