Named Route question

rubyonrails-talk
1

I have in my routes.rb

map.resources :accounts

This is fine for the standard crud routes.

But then I add a method in the accounts_controller

def logout   blah blah end

I want to link to it so I do:

<%=link_to 'Logout' ,:controller=>'accounts', :action=>'logout'%> which creates: <a href="/accounts/logout">Logout</a>

But it just calls the 'show' method of the accounts_controller and trys to find an account with an id of 'logout'

What am I missing here?

How can I call the logout method. It doesn't seem to be a problem if I dont specify a controller, but in this case the link is in the layout and needs to specify the controller.

Cheers George

2

I have in my routes.rb

map.resources :accounts

This is fine for the standard crud routes.

But then I add a method in the accounts_controller

def logout blah blah end

I want to link to it so I do:

<%=link_to 'Logout' ,:controller=>'accounts', :action=>'logout'%> which creates: <a href="/accounts/logout">Logout</a>

But it just calls the 'show' method of the accounts_controller and trys to find an account with an id of 'logout'

What am I missing here?

map.resources :accounts, :collection => {:get => :logout}

That should give you a accounts_logout_path named route you can use.

3

That doesn't work.

I can do:   map.logout 'logout', :controller => 'accounts', :action => 'logout' Not very elegant though But what is the point of having the default routes if you cant get to them?

Is the idea to make a named route for everything?

G

4

That doesn't work.

I had it backwards.

Try this.

map.resources :accounts, :collection => {:logout => get}

5

map.resources :accounts, :collection => {:logout => :get}

works...(:get not get)

6

You can make named routes for everything using the technique Phillip posted, you could rearrange your actions to be more restful (maybe a sessions controller, and map login to sessions#create, or move your default routes to a different position in the routes file (order is important here).