Realy? No one?
Maybe here is not the place to ask such things. I'll try somewhere else.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/gPmMdoLOA
The fields_for tag, when working with ActiveResource's
accepts_nested_attributes_for returns the params like this:
"book"=>{"name"=>"sdfas",
"chapters_attributes"=>{"0"=>{"name"=>"sdfaasdf"}}}
Note thé "0" as a key to the "chapters_attributes" hash.
When working with ActiveResource it gives me
Hello,
I'm trying to make ActiveResource work with nested attributes and the
fields_for tag.
I started with a typical Rails application, with two ActiveRecord models
with one to many relationship (one band has many members).
In view 'bands/new.html.erb' I have something like this:
<%= form_fo
The session is working fine. During the ajax request i can read the session
normally. But anything i write to it does not shows up in the next requests.
In all other scenario it works great.
I can reproduce this situation any time just by creating an empty project
(rails 3.0.8) with an simple sc
Anyone?
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/yrkQKYOmo9EJ.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To
Excuse me, i have a typo in the text. What i was trying to say is that
anything I include in the session (within the POST request) is NOT propagate
to the next requests.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To view this discu
include in the
session (within the POST request) is propagate to the next request.
If anyone can help me i would be very thankful.
Dimas Cyriaco
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To view this discussio
sts with
octet-stream content-type. It used to work until i try to migrate our
back-end to rails 3. Now rails just ignores the parameters and sends nothing
at all to the controllers.
Anyone have some idea why that's happening?
Thank you
Dimas Cyriaco
--
You received this message because y
8 matches
Mail list logo
