Forum: Ruby on Rails Upgrading to Rails with git v2.3.2 tag

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Andrew F. (Guest)
on 2009-03-17 02:05
(Received via mailing list)
Hi,

This bit me but I haven't seen it mentioned on here yet. I have Rails
vendored as a submodule so to upgrade from the release candidate to
2.3 I simply pulled and checked out the v2.3.2 tag
(73fc42cc0b5e94541480032c2941a50edd4080c2).

Unfortunately a rather large bug means the nested parameters will not
be hashed when POSTing, e.g. user[name] will be "user[name]" => "bob"
instead of :user => {:name => "bob"}. This is because the gem install
of rack takes precedence instead of the newer bundled one, it's fixed
in the immediate commit after
(39ff550fa88da9a22d8c21ca872f5e4d0d83f8d4). Pulling from the HEAD of
master is pretty safe at the moment anyway.

Thanks to Matt Jankowski for original report:
http://rails.lighthouseapp.com/projects/8994/ticke...

Hope this helps someone avoid trouble!

Andrew
This topic is locked and can not be replied to.