similar to: Format Values from a date_select

Hi, I am doing the following: <% obj.contracts.each do |@contract| -%> ... <%= hidden_field("contract[]", :contractor_id, :index => @contract.contractor.id) %> <%= date_select("contract[]", :starting_on, :index => @contract.contractor.id) %> ... <% end -%> Here are the request parameters: {"commit"=>"Save",

I am a little confused about the best way to work with date_select. I see that in my views it generates a simple input form that allows for the entry of year, month and date information. If I just leave it at that, great! But what if now in the controller, I want to work with the date information. I actually want to take the user input date and compute a new date some number of days in the

I want to allow users to enter a day and a month, but not necessarily a year. i.e. it should be optional. If I select the day and month, but a blank year and then submit i get: 1 error(s) on assignment of multiparameter attributes The paramaters regarding the date look like this: {"date_of_birth(2i)"=>"3",

lo there all, i want to have a date_select heper default to the year 2006, but cant seem to find out how to pull it off. any takers ? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

If I pass a date through date_select to a controller, can a Active Record object be found based on this date that is passed? Here is what my log says: ArgumentError (Unknown key(s): publication_date(2i), publication_date(3i), publication_date(1i)): /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/core_ext/hash/keys.rb:48:in `assert_valid_keys''

I am using the date_select helper to generate date select elements in a form. I notice that the generated HTML shows that these selects have the following names: Month: current_job[StartDate(2i)] Day: current_job[StartDate(3i)] Year: current_job[StartDate(1i)] I''m assuming that the Xi identifiers somehow specify the appropriate date part from a date or time value. Can anyone

hello, i would like to display a collection of records on one page (e.g. an author record with all his/her books). a record contains a text_area (e.g. a description of the book) and a date_select (e.g. when the book was published). <% for @book in @author.books %> <%= text_area ''book[]'', ''note'' %> <%= datetime_select

Hi, I render a couple of date_select fields, the HTML looks fine, I can see the values submitted back to the server, but AR doesn''t pick them up from the hash in Booking.new(params[''booking'']). I''ve got a ''booking'' object with parameters product, startdate and enddate. HTML snippets: <select

Dates defined chosen with date_select are not coming through once the form is submitted. I have this in a form: <%= date_select ''search'', ''date_start'', :include_blank => true %> <%= date_select ''search'', ''date_end'' , :include_blank => true %> However, when I submit the form params[:search][:date_start]

Hi, I could not find an easy way to specify the ''id'' attribute for select inputs of ''date_select'' form helper. I need to set it because I want to retrieve date selects values from a javascript. <%= date_select ''product'', ''expiration'' %> generates <select name="product[expiration(1i)]">

Hi there I''m having problems storing dates in a DB(postgreSQL) I have the field dtmfechanac of type date I have this in the view <%= date_select ''usuario'', ''dtmfechanac'', :start_year => 1900 %> and I have this in te controller data = { "dtmfechanac" => params[:usuario][:dtmfechanac] "dtmfechainicio" =>

Can you see an obvious reason why this date_select code is failing? The parameters from the form - *Parameters*: {"commit"=>"Save All Changes", "campaign_id"=>"1", "campaign"=>{"name"=>"fdsfas", "end_date(3i)"=>"26", "start_date(1i)"=>"2006",

Hi all I have a model "party" that has a time field "starts_at". I have created a form to add new instances of this model. <%= select_date Date.today, :prefix => ''party'' %> Sadly I get the error: NoMethodError in Parties#add undefined method `month='' for #<Party:0x256a600> How can I fix this problem? I remember that I saw in

I have a date where the year range is more then I want to define in a select_date scaffold generated year range. My idea was to have the year entered as a text field and the month and day using something like: <%= select_month @person.born,:prefix => :person ,:field_name => "born(2i)" %> <%= select_day @person.born,:prefix => :person , :field_name =>

Why select_date and select_date? I dont understand why having both (backward compat?). I also look that their source are different, one use the InstanceTag and others calls 3 select_(year, month, day) functions.

Hi, I''ve put together a simple form that contains among other things a date_select: <%= date_select(:user, :dob, :order => [:day, :month, :year], :start_year => 1900, :end_year => Date.today.year) %> In my controller I have some code to create a user entity from the parameters posted up from the form, like so: parameters:

hi there, i try to use searchlogic to find entities by date. its working if i just try to search something. the ordering helper is also working if i just show all results. if i want to order (lets say by zipcode) and find by date it wont work. the order helper messes up the params[:search] in case of using a date if i just search something the params look like (good): Parameters:

i am using date_select to allow someone to select their birthdate in a form. however date_select uses 3 wierd labels in the forms like follows: <select name="user[birthdate(1i)]"> <option value="1940">1940</option> <option value="1941">1941</option> . and then the month is user[birthdate(2i)] and so on. My issue is i dont know the

I''m getting markup violation errors on my tests and I noticed that a template with this (a modified 0.13.1 generated scaffold). <label for="credit_card_account">Account</label> <%= text_field ''credit_card'', ''account'' %> <label for="credit_card_expires_on">Expires on</label>

Hello, I am not sold on FileCheck's new behaviour. For failing tests in verbose mode, it first dump the actual error messages, followed by the annotated input file to FileCheck. The result is I can't immediately see error messages if the input is more than just a few lines long, so I have to scroll all the way up to see the errors, then down again, etc. I do see some advantages of