Forum: Ruby on Rails Rails 1.X to 2.1 routing problem

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.
8dad1ec4d769734583f45fbbee5cd009?d=identicon&s=25 Jeff Pritchard (jeffpritchard)
on 2008-12-31 02:58
Hi,
I'm trying to bring an "old" rails app up to 2.1.

I'm getting this error when trying to access the app via an iFrame setup
we had working before for showing widgets on other domains pages:
ActionController::RoutingError (No route matches "/topics;summary" with
{:method=>:get}):
    /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/routing/recognition_optimisation.rb:67:in
`recognize_path'
    /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/routing/route_set.rb:385:in
`recognize'
    /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:148:in
`handle_request'
yadda yadda...


My routes.rb has this:
  map.resources :topics,
                { :member => { :rank_item => :put,
                               :rank_items => :put,
                               :widgets => :get },
                  :collection => { :summary => :get },
                  :new => { :copy => :post,
                            :link => :post } }


and my topics controller has a "summary" method.

Any ideas what has changed that makes this no longer valid?  The other
developer on the job set this part up, and I never quite understood it.
Seems to be a pre-cursor to the "modern" REST way of doing things, but
seems only to complicate something that would otherwise be simple.

Anyway, enough bitching from me.  Anyone know what's wrong here?

many thanks,
jp
8dad1ec4d769734583f45fbbee5cd009?d=identicon&s=25 Jeff Pritchard (jeffpritchard)
on 2009-01-01 22:41
Jeff Pritchard wrote:
> Hi,
> I'm trying to bring an "old" rails app up to 2.1.
>
>
> many thanks,
> jp

Shameless bump.  Apparently everyone was out partying last night and
didn't see my plea for assistance...

thanks,
jp
4b1b339ee3f96d37aba2adfa3e03276e?d=identicon&s=25 Brandon Keepers (Guest)
on 2009-01-01 23:31
(Received via mailing list)
jp,

On Tue, Dec 30, 2008 at 8:58 PM, Jeff Pritchard
<rails-mailing-list@andreas-s.net> wrote:
> 
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/routing/route_set.rb:385:in
>                               :widgets => :get },
> seems only to complicate something that would otherwise be simple.
>
> Anyway, enough bitching from me.  Anyone know what's wrong here?

Rails 1.x used a semi-colon instead of just a slash to specify the
action, so instead of "/topics;summary", the route will generate
"topics/summary".  I'm guessing whatever is calling the iframe has the
url with the semi-colon hard-coded.

Brandon

--
--------------------------------------------------------------------------------
Training by Collective Idea: Ruby on Rails training in a vacation
setting
http://training.collectiveidea.com – San Antonio, TX – Jan 20-23
8dad1ec4d769734583f45fbbee5cd009?d=identicon&s=25 Jeff Pritchard (jeffpritchard)
on 2009-01-01 23:59
Brandon Keepers wrote:
> Rails 1.x used a semi-colon instead of just a slash to specify the
> action, so instead of "/topics;summary", the route will generate
> "topics/summary".  I'm guessing whatever is calling the iframe has the
> url with the semi-colon hard-coded.
>
> Brandon
>
> --
> --------------------------------------------------------------------------------
> Training by Collective Idea: Ruby on Rails training in a vacation
> setting
> http://training.collectiveidea.com � San Antonio, TX � Jan 20-23



GENIUS!

Thanks Brandon, that was the whole problem.  Everything is working great
now!

cheers,
jp
This topic is locked and can not be replied to.