similar to: Check_box woes

I would like to have a customer that has references to two addresses, a billing address and a shipping address. In a non-rails environment I would have two keys in the customers table, billing_address_id and shipping_address_id to reference the addresses. It appears that ActiveRecord expects the parent id to reside in the child table, regardless of whether the relationship is one-to-one or

Hello, I posted a similar email, earlier in the week, but I still must not be getting it. I have a customer that aggregates two addresses; a shipping address and a billing address. Addresses can also be referenced by other objects in a similar way, so I would really like to avoid putting the keys referencing the customer or other objects in the addresses table. Addresses are exclusively

Op 8-9-2015 om 17:15 schreef Michele Locati: > I'm using Dovecot 2.2.9 and I'm having problems configuring multiple > vacation actions. > The problem is that I'd like to have two different senders and two > different messages, selecting the correct case by the recipient email > address. > I mean, if someone writes me to my email address "to-address1 at

I''ve got a question on the use of check_box. *** This is working but there just has to be a better way: RHTML: <% for book in @books do %> <tr> <td><%=book.label%></td> <td> <%checked = book.subscribed ? ''checked'': ''nope''%> <%=check_box("book" + book.id.to_s,

Hi all I'm using Dovecot 2.2.9 and I'm having problems configuring multiple vacation actions. The problem is that I'd like to have two different senders and two different messages, selecting the correct case by the recipient email address. I mean, if someone writes me to my email address "to-address1 at example.com" I'd like to answer from "from-address1 at

I''ve got the following problem, I''ve created two check_boxes in my view. The user has to select one check_box, but isn''t allowed to seth both of them together on true. Now i am looking for functionality that can help me doing the folling: Scenario 1 CheckBox1 = True, The user sets CheckBox2 from False to True, now CheckBox1 should automatically become False.

I''ve tried this (in a new method/template -- so @type doesn''t actually exist yet): check_box ''type'', ''notify_on_create'', {:checked=>''true''} But :checked seems to get swallowed. I''ve also tried setting notify_on_create to true in the Type model, but that doesn''t work either. Any way to get the

I''m using Rails 1.1.x and it looks like the check_box form helper expects me to provide and object and method so it can determine if the checkbox should be checked or not. I''m having a couple of issues with this. note: I''m using UserEngine and adding a HABTM so that: class User < ActiveRecord::Base has_and_belongs_to_many :foos end class foo <

hey, i need a select list with a id property and not name, cuz i just ajax with this list and it checks on id not name if @request.post? #called by ajax if @request.xml_http_request? #called by ajax @geotag_id=params[:geotag_id].nil? ? -2 : params[:geotag_id] else @geotag_id=params[:geotag][:id].blank? ? -1:params[:geotag][:id] end else @geotag_id = -1 end i use this @geotags =

Hello, I have the following: My Controller: def new . . @teammembers.each do |teammember| request = @request_thread.requests.build(:recipient_id => teammember.user_id, :full_name => ''Billy Bob T'') end My View: . . <%= f.fields_for :requests do |builder| %> <div class="field"> <%= builder.label

I have a checkbox: <%= check_box(:day, :monday, {:disabled => ''''} , (day.monday == true ? {:checked => ''checked''} : {:checked => false} )) %> It is disabled allright, but it is always uncecked. Is this supposed to happen. It looks like (day.monday == true ? {:checked => ''checked''} : {:checked => false} ) is not

What is the difference between the check_box_tag and the check_box form helper? I can''t understand why both must exist. :( Thanks. Fernando Lujan

Hi, I would like to put a checkbox on a form where the input field is a variable rather than a field in a model. The normal way (with a model) would be: <%= check_box(''client'', ''accept'', {}, "1", "0") %> But since accept is a variable @accept and model client will not be there, how do I make a check box work? Regards, Paul

Can anyone help me with this, which has been making me tear my hair out for 2 days now ? I have the following classes using has_many :through relationships... (I''ve changed the class names to make it easier to understand, so don''t beat me up about naming conventions ;) ) class Movie < ActiveRecord::Base has_many :localdetails has_many :territories, :through=>:rights

I am sure this is a trivial problem for a rails guru! all I want to do is display an appropriately cheched check_box in a table, so: instead of <% for t in @patient.histories%> <tr> <td><%= t.ihd %></td> </tr> <%end%> I want something like: <% for t in @patient.histories%> <tr>

I''m new to RoR and I''m having a little problem that I can''t solve. My model is simple. I have Lists and ListItems. I have a view that loops through all the list items, and I put the HTML for the each list item row in a partial called _list_item.rhtml. This is the view, called show.rhtml <ul> <%= render(:partial => "list_item", :collection =>

I have the following code to send out email notifications. The view can vary for each call to signup_confirmation, so I''m setting template_root on each call in order to do that. It works for a while, but after a few days it will start using a value of signup_path that was used in a previous call. In other words, Notifier.template_root = signup path does not actually set

I have the following code to send out email notifications. The view can vary for each call to signup_confirmation, so I''m setting template_root on each call in order to do that. It works for a while, but after a few days it will start using a value of signup_path that was used in a previous call. In other words, Notifier.template_root = signup path does not actually set

I have two objects, QuoteInput and Insured. QuoteInput has one Insured and Insured belongs to QuoteInput. I don''t understand what I''m seeing. I assign an Insured to a QuoteInput. The Insured object has invalid data. I call save! on the quote input. QuoteInput has no validations. I expect two things to happen - 1) an exception should be thrown, indicating that there was a

I have the following (abridged) routes in routes.rb: map.namespace :member do |member| member.resource :profile, :controller => ''profile'' do |profile| profile.edit_address ''address/:id/edit'', :action => ''edit_address'', :conditions => { :method => :get } end end which nicely creates (among others):