I have a simple app -- essentially just restful_authentication at this
point. I have the following in my routes.rb:
map.resources :attendees
map.resource :sessions
# nice named routes
map.signup '/signup', :controller => 'attendees', :action =>
'new'
map.login '/login', :controller => 'sessions', :action => 'new'
map.logout '/logout', :controller => 'sessions', :action =>
'destroy'
map.activate '/activate/:activation_code', :controller =>
'attendees', :action => 'activate'
My tests all work OK, and functionally this seems to be working...I
can signup, activate, log in and log out.
When I use the named routes I created (eg localhost/signup) I do get
the correct page routed, but I also get an error in the log:
/!\ FAILSAFE /!\ Sat Nov 07 17:09:34 -0800 2009
Status: 500 Internal Server Error
PROPFIND, accepted HTTP methods are get, head, put, post, delete,
and options
C:/Ruby/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/
action_controller/request.rb:35:in `request_method'
(etc)
I don't get that if I use the resource route (/attendees/new).
The easy solution is not to use named routes I guess, but I'd rather
keep a few clean/sparse routes for embedding in emails. I'm assuming
this is some conflict with rest routes and named routes...but that's
just speculation.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
