Am I wrong or is fields_for not working right in Rails 2.2.2


#1

I may be totally wrong about what the fields_for method is supposed to
do, but for some reason I thought using it scoped an object around an
association.

For example, I have a User class and when you’re creating a new user I
want to use fields_for to add a BillingAddress to the user like so:

<%- fields_for :billing_address do |billing_address_form| -%>
<%= render :partial => ‘billing_addresses/form’, :locals => { :f =>
billing_address_form } %>
<%- end -%>

This however, is not scoping the user object around the billing address
form fields because when I view source, I see this:

Address one

Address two

I’m using Rails 2.2.2 and maybe this never worked the way I’m thinking
it should, or I could be doing something wrong…

Any suggestions anyone?

Thanks,
Josh


#2

On Dec 2, 10:29 pm, Joshua A. removed_email_address@domain.invalid
wrote:

<%- end -%>
Address two

Assuming that partial is along the lines of
<%= f.label :address_one %>
<%= f.text_field :address_one %>

That’s what I would expect. Are you expecting it to magically guess
something ?(if so, what?)

Fred


#3

I guess I’m expecting it to know from

<%- form_for(@user) do |f| -%>

<%- fields_for :billing_address do |billing_address_form| -%>
<%= render :partial => ‘billing_addresses/form’, :locals => { :f =>
billing_address_form } %>
<%- end -%>

<%- end -%>

to build inputs more like user[billing_address][address_two]

Is that not what fields_for is used for?

– Josh

Frederick C. wrote:

On Dec 2, 10:29�pm, Joshua A. removed_email_address@domain.invalid
wrote:

<%- end -%>
� Address two

�

Assuming that partial is along the lines of
<%= f.label :address_one %>
<%= f.text_field :address_one %>

That’s what I would expect. Are you expecting it to magically guess
something ?(if so, what?)

Fred


#4

On Dec 3, 9:50 pm, Joshua A. removed_email_address@domain.invalid
wrote:

to build inputs more like user[billing_address][address_two]

Just because lexically it’s ‘inside’ the first form isn’t enough (or
to put things another way, it’s hard for code to know about the code
that’s calling them). If you want what you describe you need to be
explicit: use f.fields_for

Fred


#5

Fred, I think you nailed it! Thanks a lot!

– Josh

Frederick C. wrote:

On Dec 3, 9:50�pm, Joshua A. removed_email_address@domain.invalid
wrote:

to build inputs more like user[billing_address][address_two]

Just because lexically it’s ‘inside’ the first form isn’t enough (or
to put things another way, it’s hard for code to know about the code
that’s calling them). If you want what you describe you need to be
explicit: use f.fields_for

Fred