Databases
StackOverflow2013
Postsdbo
POnested namespace route going to wrong controller
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POnested namespace route going to wrong controller
    primarykey
    data
    text
    <p>Using Rails 3.0.7, I'm creating an API for our app, and I have this setup:</p> <p>routes.rb</p> <pre><code> namespace :api do namespace :v1 do match "connect" =&gt; "users#login", :via =&gt; :post match "disconnect" =&gt; "users#logout", :via =&gt; :post resources :users match "users/:id/foos" =&gt; "foos#list", :via =&gt; :get match "users/:id" =&gt; "users#update", :via =&gt; :put match "foos/:id/bars" =&gt; "bars#list_by_foo", :via =&gt; :get match "foos/:id" =&gt; "foos#show", :via =&gt; :get, :constraints =&gt; { :id =&gt; /\d+/ } match "bars/:id" =&gt; "bars#show", :via =&gt; :get end end # other routes here e.g. match "users/find" =&gt; "users#find_by_name", :via =&gt; :get match "users" =&gt; "users#create", :via =&gt; :post </code></pre> <p>And then I have my regular <code>app/controllers/application_controller.rb</code> and <code>app/controllers/users_controller.rb</code> files as well as my <code>app/controllers/api/v1/application_controller.rb</code> and <code>app/controllers/api/v1/users_controller.rb</code> files that are defined like the following:</p> <pre><code>class Api::V1::ApplicationController &lt; ApplicationController before_filter :verify_access def verify_access # some code here end end class Api::V1::UsersController &lt; Api::V1::ApplicationController skip_before_filter, :except =&gt; [:show, :update, :delete] end </code></pre> <p>And before everything seemed to be working right until I overrode a method that is shared by both UsersController and Api::V1::UsersController -- and now it seems like everything is pointing to UsersController even though I'm accessing through the api/v1/users route.</p> <p>I'm at my wit's end trying to figure it out. Any suggestions? Thanks. PS - feel free to comment with whatever conventions I'm ignoring that I shouldn't be or other things I might have messed up :)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpaulnsorensen
    1. USpaulnsorensen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POnested namespace route going to wrong controller
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTurns out I just had to make all my controller names unique, regardless of namespace. [Here's a link that helped](http://blog.philburrows.com/articles/2008/05/02/rails-namespaces-rock-rails-namespaces-suck-/)
      singulars
      1. POnested namespace route going to wrong controller
      1. USpaulnsorensen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload