Rails - Dec 2007 - Routes doing wrong URL parsing with Ruby 1.8.5, works with 1.8.6 (routing trouble with controllers grouped in folder)

Hello,

    We had a problem with a URL being parsed wrong by the routing
module of Ruby on Rails for the controllers stored in a folder: admin/

    Instead of having

  Parameters: {"action"=>"update_options",
"controller"=>"admin/
venues"

    we got

Parameters: {"action"=>"venues",
"id"=>"update_options",
"controller"=>"admin"

    Causing a:

ActionController::UnknownAction (No action responded to venues):

    Exception.

    We tested it a lot of boxes, the problem was happening only in one
server. The only difference we found was the server having Ruby 1.8.5
instead of Ruby 1.8.6, we upgraded the Ruby version in the server and
it started working without problem.

    Rails Version: 1.2.5
    SO: Debian Etch

--
Aníbal Rojas
http://hasmanydevelopers.com
http://rubycorner.com
http://anibal.rojas.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-/JYPxA39Uh5TLH3MbocFFw@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
-~----------~----~----~----~------~----~------~--~---

Was the controller called something like Admin::Controller or just
Controller?

On Dec 22, 2007 7:53 AM, Aníbal Rojas
<anibalrojas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hello,
>
>    We had a problem with a URL being parsed wrong by the routing
> module of Ruby on Rails for the controllers stored in a folder: admin/
>
>    Instead of having
>
>  Parameters: {"action"=>"update_options",
"controller"=>"admin/
> venues"
>
>    we got
>
> Parameters: {"action"=>"venues",
"id"=>"update_options",
> "controller"=>"admin"
>
>    Causing a:
>
> ActionController::UnknownAction (No action responded to venues):
>
>    Exception.
>
>    We tested it a lot of boxes, the problem was happening only in one
> server. The only difference we found was the server having Ruby 1.8.5
> instead of Ruby 1.8.6, we upgraded the Ruby version in the server and
> it started working without problem.
>
>    Rails Version: 1.2.5
>    SO: Debian Etch
>
> --
> Aníbal Rojas
> http://hasmanydevelopers.com
> http://rubycorner.com
> http://anibal.rojas.com
> >
>

-- 
Ryan Bigg
http://www.frozenplague.net

--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@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
-~----------~----~----~----~------~----~------~--~---