Databases
StackOverflow2013
Postsdbo
PORails routes error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails routes error
    primarykey
    data
    text
    <p>I am following along with Michael Hartl's <a href="http://ruby.railstutorial.org/ruby-on-rails-tutorial-book" rel="nofollow">Ruby on Rails Tutorial 2nd Edition</a> and have reached the signin/signout section of the book.</p> <p>So far I can create a new user (or in my case landlord) and log in with the new credentials. The problem I have is when signing out. I click "signout" and get a route error saying:</p> <blockquote> <p>No route matches [GET] "/signout"</p> </blockquote> <p>Below are code snippets. Any help would be very appreciated!</p> <p>rake routes output</p> <pre><code>landlords GET /landlords(.:format) landlords#index POST /landlords(.:format) landlords#create new_landlord GET /landlords/new(.:format) landlords#new edit_landlord GET /landlords/:id/edit(.:format) landlords#edit landlord GET /landlords/:id(.:format) landlords#show PUT /landlords/:id(.:format) landlords#update DELETE /landlords/:id(.:format) landlords#destroy properties GET /properties(.:format) properties#index POST /properties(.:format) properties#create new_property GET /properties/new(.:format) properties#new edit_property GET /properties/:id/edit(.:format) properties#edit property GET /properties/:id(.:format) properties#show PUT /properties/:id(.:format) properties#update DELETE /properties/:id(.:format) properties#destroy sessions POST /sessions(.:format) sessions#create new_session GET /sessions/new(.:format) sessions#new session DELETE /sessions/:id(.:format) sessions#destroy root / content_pages#home content_pages_home GET /content_pages/home(.:format) content_pages#home help /help(.:format) content_pages#help questions /questions(.:format) content_pages#questions signup /signup(.:format) landlords#new signin /signin(.:format) sessions#new signout DELETE /signout(.:format) sessions#destroy </code></pre> <p>routes.rb file</p> <pre><code> resources :landlords resources :properties resources :sessions, only: [:new, :create, :destroy] root :to =&gt; 'content_pages#home' get "content_pages/home" match '/help', to: 'content_pages#help' match '/questions', to: 'content_pages#questions' match '/signup', to: 'landlords#new' match '/signin', to: 'sessions#new' match '/signout', to: 'sessions#destroy', via: :delete </code></pre> <p>link to signout</p> <pre><code>&lt;%= link_to "Signout", signout_path, method: "delete" %&gt; </code></pre> <p>sessions controller</p> <pre><code>def destroy sign_out redirect_to root_path end </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBert
    1. USTony Staunton
    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. PORails routes error
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. CODo you have a `sign_out` method in the sessions helper? Look at listing 8.30 in the book/website. The `destroy` method of the controller is looking for it.
      singulars
      1. PORails routes error
      1. USBert
    2. COYea I have a sign-out method in the session helper 'def sign_out self.current_landlord = nil cookies.delete(:remember_token) end'
      singulars
      1. PORails routes error
      1. USTony Staunton
    3. COHey @TonyStaunton did the answer work for you? I am still having the same issue.
      singulars
      1. PORails routes error
      1. USn_x_l
 

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