This project is archived and is in readonly mode.

#2529 ✓resolved
Ole Bjarnstroem

Rack parameter issue still persists

Reported by Ole Bjarnstroem | April 20th, 2009 @ 07:11 PM | in 2.x

Hi,

this is my first ticket, so please excuse any mistakes.

I have a very strange issue. I upgraded my Application to Rails 2.3.2 without any problems, then freezed it to vendor/rails and worked through all my specs after I also upgraded Rspec to 1.2.4. At some point (I cannot exactly tell you when) nested parameters didn't work anymore (as described here: https://rails.lighthouseapp.com/...>

That means the server receives something like:

{ "post[body]" => "data" }

instead of

{ "post" => { "body" => "data" } }

So I worked through all the forums, deinstalled the gem rack-0.9.1 and checked that I have the commit 39ff550fa88da9a22d8c21ca872f5e4d0d83f8d4 (http://github.com/rails/rails/co.... That means the bundled rack-1.0 should be loaded, at least my rack.rb reads on line 6

$:.unshift(File.expand_path(File.dirname(FILE)))

Still the problem persists and I don't know exactly how to fix this.

Any help is appreciated! Thanks

Comments and changes to this ticket

  • Ole Bjarnstroem

    Ole Bjarnstroem April 20th, 2009 @ 07:51 PM

    I also tried to do this:

    $ sudo rake rails:freeze:edge

    But all I get is:

    cd vendor Downloading Rails from http://dev.rubyonrails.org/archi... rake aborted! Operation timed out - connect(2)

    I cannot call or reach http://dev.rubyonrails.org , any ideas?

  • Ole Bjarnstroem

    Ole Bjarnstroem April 20th, 2009 @ 10:06 PM

    Ok,

    $ sudo rake rails:freeze:edge RELEASE=2.3.2.1

    was successfull now, so I'm 100% sure I have the correct version. I even deinstalled the ruby gem just to make sure my freezed version is used.

    The problem still exists!

    For me that means Forms arent working anymore in Rails 2.3.2 - that is kind of a serious issue.

    Does anyone has a solution for this?

  • Ole Bjarnstroem

    Ole Bjarnstroem April 21st, 2009 @ 06:56 AM

    This "bug" is solved, it was just a very stupid mistake. I had accidently frozen the rack-0.9.1 gem with

    rake gems:unpack:dependencies

    and didn't notice it. A simple

    sudo rm -rf vendor/gems/rack-0.9.1

    did the trick.

    This ticket can be closed.

  • Matt Jones

    Matt Jones May 11th, 2009 @ 12:01 AM

    • State changed from “new” to “resolved”

    Marked resolved.

    I'm curious, though, why you need to use sudo to get stuff out of vendor/gems. Did you unpack gems as root?

  • Ole Bjarnstroem

    Ole Bjarnstroem May 11th, 2009 @ 09:20 AM

    That could be. Could that lead to any other problems?

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

People watching this ticket

Pages