I’m stuck here too…no mention of this in documentation (that I could
see). When I click on the activate link in the activation email it
errors “no route found to match “/activate/d8e1326e13c18a” with
Will /logout still require a DELETE method this way or will it accept GET?
The Session#Destroy in its default state accepts a get. i.e. /logout.
It’s not destroying an Active Record object, just the session, so I
think it’s a useful feature. Note that restful_authenttication doesn’t
have a User#Destroy method- that would certainly need a delete method.
1 - My model is called User
2 - My end-user-visible signup and preferences/password management is
done through AccountController which is a singleton because users
can’t see other users and you can only have one account.
3 - Administrators can see other users (plus extra data users can’t
see about themselves) so for that purpose they have a UsersController
Hopefully that explains why I chose :account as a singleton rather
than a collection.
And, that should also illustrate that yes, your :session resource is also a singleton - each HTTP session can only have one logical
session so it’s a singleton.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.