On Feb 18, 5:38 am, "[email protected]" <[email protected]> wrote:
> When my controller passes the view an existing object, I submit the
> form and everything's dandy. When my controller passes the view a new
> object that does not have an id, then I get the error message
> regarding conflicting container types.
>
> Why? Can I use the same form to handle both new and edited objects and
Well it's a little tricky to say without seeing the html but that
error message usually means that in the same form you have something
like
foo[]=bar and foo[bar]=baz
it may be that passing an :index option to fields for when dealing
with a new record is the way out
Fred
> at the same time to work as expected with f.text_field? Am I going
> about it the wrong way? I spent quite a bit of time reading the
> tutorials on the web but still don't understand what's going on here.
>
> Any guidance appreciated!
> Yoram
--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
