Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  James B. Byrne November 23rd, 2010 @ 02:18 PM

  Just mouse over the links and you will see the difference in the generated urls.

• You flagged this item as spam.
  

  Andrés Mejía November 23rd, 2010 @ 11:29 PM

  I cannot reproduce this. Can you try to isolate the issue to a minimal application that exhibits the problem? Thanks!

• You flagged this item as spam.
  

  James B. Byrne November 24th, 2010 @ 01:58 AM

  I will try. The difficulty being that we are about to deploy the next release of our application. So, I might be a little while getting to it.

• You flagged this item as spam.
  

  James B. Byrne November 26th, 2010 @ 04:19 PM

  I have done a little more investigation and I do not think that I can get things much simpler than this:

  Routes as given above.

  3.0.3 behaviour ( same as 3.0.2 )

  $ rails c
  Using AdapterExtensions
  Loading development environment (Rails 3.0.3)
  ruby-1.8.7-p302 > app.user_roles_path
   => "/user/roles" 
  ruby-1.8.7-p302 > app.user_roles_path( 1 )
   => "/user/roles.1" 
  ruby-1.8.7-p302 > exit
  

  3.0.1 behaviour

  $ rails c
  Using AdapterExtensions
  Loading development environment (Rails 3.0.1)
  ruby-1.8.7-p302 > app.user_roles_path
  ActionController::RoutingError: No route matches {:controller=>"user_roles", :action=>"create"}
          from /home/byrnejb/.rvm/gems/ruby-1.8.7-p302/gems/actionpack-3.0.1/lib/action_dispatch/routing/route_set.rb:424:in `raise_routing_error'
          from /home/byrnejb/.rvm/gems/ruby-1.8.7-p302/gems/actionpack-3.0.1/lib/action_dispatch/routing/route_set.rb:397:in `generate'
          from /home/byrnejb/.rvm/gems/ruby-1.8.7-p302/gems/actionpack-3.0.1/lib/action_dispatch/routing/route_set.rb:453:in `generate'
          from /home/byrnejb/.rvm/gems/ruby-1.8.7-p302/gems/actionpack-3.0.1/lib/action_dispatch/routing/route_set.rb:481:in `url_for'
          from /home/byrnejb/.rvm/gems/ruby-1.8.7-p302/gems/actionpack-3.0.1/lib/action_dispatch/routing/url_for.rb:132:in `url_for'
          from /home/byrnejb/.rvm/gems/ruby-1.8.7-p302/gems/actionpack-3.0.1/lib/action_dispatch/routing/route_set.rb:195:in `user_roles_path'
          from (irb):2
  ruby-1.8.7-p302 > app.user_roles_path( 1 )
   => "/users/1/roles"
  

• You flagged this item as spam.
  

  James B. Byrne November 26th, 2010 @ 04:37 PM

  I should point out that this behaviour is exhibited after I did the following simplifications:

  1. The entire route.rb file looks like this:

  Proforma::Application.routes.draw do
  
    resource :user do
      resources :roles
    end
  
    resources :users do
      resources  :roles, 
        :controller => 'user_roles'
    end
  
  end
  

  The Gemfile contains only this:

  source 'http://rubygems.org'
  gem "rails", "= 3.0.3"
  gem 'pg
  

• You flagged this item as spam.
  

  James B. Byrne November 30th, 2010 @ 09:57 PM

  I generated a new rails-3.0.3 project and added the suspect routes only. The problem is instantly reproducible:

  $ rails c
  Loading development environment (Rails 3.0.3)
  ruby-1.8.7-p302 > 
  ruby-1.8.7-p302 >   app.user_roles_path( 1 )
   => "/user/roles.1"
  

• 

  José Valim December 9th, 2010 @ 07:27 PM

  • State changed from “new” to “invalid”
  • Importance changed from “” to “Low”

  A conflict of the routes name is happening here. I don't think this is a regression, but actually a fix as routes methods generated first have higher priority than the ones generated later. If you change the routes order, you should get this fixed. The output of rake routes will also help you.

• You flagged this item as spam.
  

  James B. Byrne December 17th, 2010 @ 10:34 PM

  Reordering the resources did resolve the problem.