I have a custom serializer object that I use for an attribute of ActiveRecord as presented in this article: http://www.edgerails.info/articles/what-s-new-in-edge-rails/2011/03/09/custom-activerecord-attribute-serialization/index.html If I assign a value to that attribute with a form (in my case a nested form), I don''t get the deserialized value in the params hash as it used to be with Rails 3.1, but now I get a serializer struct that contains the custom serializer class instance and the deserialized value. Does anybody know whether this is intentional, or is it just broken and I have to work around that until it gets fixed...? -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I''m seeing the same problem after having upgraded to rails 3.2 . No custom serializer for me, just a regular serialized field. Previous behaviour was to have the field automatically deserialized, but instead I''m getting the serialized version. -- 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/-/er4-674IIecJ. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Any update on this? Serialization just plain isn''t working for me using 3.2. Gabriel On Thursday, February 9, 2012 10:09:38 AM UTC-8, tigrish wrote:> > I''m seeing the same problem after having upgraded to rails 3.2 . > > No custom serializer for me, just a regular serialized field. > > Previous behaviour was to have the field automatically deserialized, but > instead I''m getting the serialized version. >-- 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/-/85iDW81V9y4J. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Mar 27, 9:22 pm, Gabriel Williams <ummo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Any update on this? Serialization just plain isn''t working for me using > 3.2. >Which version are you using ? Rails 3.2.2 fixed some behaviour in that respect for us. Fred> Gabriel > > > > > > > > On Thursday, February 9, 2012 10:09:38 AM UTC-8, tigrish wrote: > > > I''m seeing the same problem after having upgraded to rails 3.2 . > > > No custom serializer for me, just a regular serialized field. > > > Previous behaviour was to have the field automatically deserialized, but > > instead I''m getting the serialized version.-- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.