Creating Variable Number of Models in One Form (Page 3 of 7)

We're getting closer. The debug information is:

- !ruby/object:Position
  attributes:
    name:
    voucher_id:
    account:
    debit_credit:
    category_id:
    amount: !ruby/object:BigDecimal 0.0
  new_record: true

And believe it or not with this line the position is visible, without it's not. Seems to be a initializing problem? I'm sure that is easy to solve but I don't know how? Sorry for annoying you with such rudimental questions but at this time rails has some kind of magic for me. It will getting better in a few weeks, I promise!

Last edited by BigTitus (2007-02-07 05:05:40)

Well ... it does. What kind of bug do you mean? Within the rails environment? Or within my application?

And by the way, I can't find 'to_yaml' in rails API, am I blind?

to_a works for me, but I am using Rails 1.1.6. Even the voucher model does not look very special:

class Voucher < ActiveRecord::Base
  has_many :positions
    
  validates_presence_of :date, :desc, :voucher_nr
  validates_uniqueness_of :voucher_nr
    
  protected
  def validate
    errors.add(:voucher_nr, "should be at least 1" ) if voucher_nr.nil? || voucher_nr <= 1
  end
end

Thank you very much for that!

Not yet. I'm still planning on writing one but haven't gotten around to it yet. I need to do some testing to find the best way to do this. It can get rather complex.

The only thing I can suggest for now is to keep the new tasks and the existing tasks completely separate on the edit page. Even make two delete actions for deleting an existing task vs. one that is new. After you are done doing this you will no doubt have a lot of duplication, but you will be in a better position to refactor and remove the duplication (merge the two delete actions into one, etc.).

I'd be interested in seeing that as well ...

I fixed the problem after reading this post:

http://kekova.ca/articles/2006/04/15/ie … e_tr_error

I had to place my id="tasks" in the <tbody> element and I moved the id="task_<%= index %>" attribute to the <tr> element of my partial. This way I could add and delete a row for a task dynamically!

But in the end: great tutorial Ryan!

Thank you very much for this tutorial! It has been extremely helpful.
I have only run into one problem so far. The user is able to click the Add Task link multiple times before it is updated with a new index. This results in multiple sets of fields with the same index.

I was able to remedy this by hiding the link with javascript. I just added this bit of code to the link_to_remote call:

:loading => "document.getElementById(\"div_containing_link\").style.display = 'none'"

I'm having some trouble with adding another Phone Number field.  The remove feature works fine.

Here is my form code:

<table>
  <tbody id="phone_numbers">
    <% @company.phone_numbers.each_with_index do |phone_number, index| %>
    <%= render :partial => 'phone_number_fields', :locals => { :phone_number => phone_number, :index => index } %>
    <% end %>
  </tbody>
  <%= render :partial => 'add_phone_number_link', :locals => { :index => @company.phone_numbers.size } %>
</table>

<% fields_for "phone_numbers[#{index}]", phone_number do |f| %>
    <tr id="phone_number_<%= index %>">
        <td><%= f.text_field :number  %></td>
        <th>
            <!-- Insert Location here -->
        </th>
        <td class="addremove">
        <%= link_to_remote 'remove', :url => { :action => 'remove_phone_number', :index => index } %>
    </td>
    </tr>
<% end %>

page.insert_html :bottom, :phone_numbers, :partial => 'phone_number_fields', 
  :locals => { :phone_number => @phone_number, :index => params[:index] }
  
page.replace :add_phone_number_link, :partial => 'add_phone_number_link', 
  :locals => { :index => (params[:index].to_i + 1) }

Any advice?  Also, is there anyway to debug what happens when I click on the "Add another phone number" link.

Last edited by drlelon (2007-05-06 13:49:26)

The add_phone_number_link partial is :

<tr id="add_company_phone_number">
    <td class="add">
        <%= link_to_remote 'Add another', :url => { :action => 'add_phone_number', :index => index } %>
    </td>
    <th>&nbsp;</th>
    <td class="addremove"></td>
</tr>