StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PORails routes, problem with custom :action not being recognized, always 'show'
primarykey
Id
3130126
data
AcceptedAnswerId
3130178
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-28T04:50:13.773
FavoriteCount
2
LastActivityDate
2015-08-06T06:34:26.300
LastEditDate
2010-06-28T06:01:31.277
LastEditorUserId
1123
OwnerUserId
373855
ParentId
0
PostTypeId
1
Score
0
ViewCount
6633
LastEditorDisplayName
text
Body
I'm trying to 'manage' users, instead of 'new' and 'show' users via actions. The problem is somewhere in routes I suspect, as my link '/users/manage' is being received as an id parameter to 'show' action: Terminal log of process: <pre><code>Processing UsersController#show (for 127.0.0.1 at 2010-06-28 00:31:45) [GET] Parameters: {"id"=>"manage"} ActionController::UnknownAction (No action responded to show. Actions: create, destroy, index, manage, and update): </code></pre> Here are some code snippets of relevant parts: users/index.html.erb (the link created to go to the manage section, i.e. '/users/manage'): <pre><code><%= link_to('New User', :action => 'manage') %> </code></pre> users_controller.rb (supposed to be receiving 'manage' action, but gets 'show' fr om above call: <pre><code>def index @users = User.all respond_to do |format| format.html # index.html.erb format.xml { render :xml => @users } end end def manage @users = User.all @user = User.find(params[:id]) if params[:id] @user = User.new if @user.nil? respond_to do |format| format.html # new.html.erb format.xml { render :xml => @user } end end </code></pre> Ruby/rails sees '/users/manage' as a ':controller/:action/:id' i.e. 'users/show/1'. When using '/users/manage/1' to edit a single user, the proper :action (as 'manage') is loaded via the UsersController 'manage' function, and everything is displayed to edit from the manage.html.erb file. UsersController sees 'manage' and not 'show', correctly, int his case, but only because of the :id being passed making the ':controller/:action/:id' route kick in and work. 'users/manage', :controller/:action seems to be the problem, not recognizing 'manage' as a valid :action alone, instead sending is as an :id in 'show'... routes.rb: <pre><code>ActionController::Routing::Routes.draw do |map| map.resources :users map.resources :categories map.resources :posts map.connect ':controller/:action' map.connect ':controller/:action/:id' map.connect ':controller/:action/:id.:format' end </code></pre> Can someone please help me resolve this? Why is the 'show' action being automatically undertaken? Can I force 'users' and 'manage' in routes to be recognized in the controller as 'manage' and not as 'show'? Thanks for the help people :) Peace. EDIT rake routes <pre><code>$ rake routes (in /home/krnel/sites/rails_projects/simple_blog) users GET /users(.:format) {:action=>"index", :controller=>"users"} POST /users(.:format) {:action=>"create", :controller=>"users"} new_user GET /users/new(.:format) {:action=>"new", :controller=>"users"} edit_user GET /users/:id/edit(.:format) {:action=>"edit", :controller=>"users"} user GET /users/:id(.:format) {:action=>"show", :controller=>"users"} PUT /users/:id(.:format) {:action=>"update", :controller=>"users"} DELETE /users/:id(.:format) {:action=>"destroy", :controller=>"users"} categories GET /categories(.:format) {:action=>"index", :controller=>"categories"} POST /categories(.:format) {:action=>"create", :controller=>"categories"} new_category GET /categories/new(.:format) {:action=>"new", :controller=>"categories"} edit_category GET /categories/:id/edit(.:format) {:action=>"edit", :controller=>"categories"} category GET /categories/:id(.:format) {:action=>"show", :controller=>"categories"} PUT /categories/:id(.:format) {:action=>"update", :controller=>"categories"} DELETE /categories/:id(.:format) {:action=>"destroy", :controller=>"categories"} posts GET /posts(.:format) {:action=>"index", :controller=>"posts"} POST /posts(.:format) {:action=>"create", :controller=>"posts"} new_post GET /posts/new(.:format) {:action=>"new", :controller=>"posts"} edit_post GET /posts/:id/edit(.:format) {:action=>"edit", :controller=>"posts"} post GET /posts/:id(.:format) {:action=>"show", :controller=>"posts"} PUT /posts/:id(.:format) {:action=>"update", :controller=>"posts"} DELETE /posts/:id(.:format) {:action=>"destroy", :controller=>"posts"} manage_users GET /users/manage(.:format) {:action=>"manage", :controller=>"users"} GET /users(.:format) {:action=>"index", :controller=>"users"} POST /users(.:format) {:action=>"create", :controller=>"users"} GET /users/new(.:format) {:action=>"new", :controller=>"users"} GET /users/:id/edit(.:format) {:action=>"edit", :controller=>"users"} GET /users/:id(.:format) {:action=>"show", :controller=>"users"} PUT /users/:id(.:format) {:action=>"update", :controller=>"users"} DELETE /users/:id(.:format) {:action=>"destroy", :controller=>"users"} /:controller/:action/:id /:controller/:action/:id(.:format) </code></pre>
Tags
<ruby-on-rails>
Title
Rails routes, problem with custom :action not being recognized, always 'show'
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMagnar
UserOwnerUserId
1. USKrNel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PORails routes, problem with custom :action not being recognized, always 'show'
 UserUserId
 USjjl2
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

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.