Thanks very much -- that is the obvious approach, but I wasn't sure if
there would be a better way to do it or any side effects of extending
the controller. But actually, I tried it and it doesn't seem to
work... The signin page URL is
http://localhost:3000/users/sign_in so
it should find it, but it's not. In the log, I see "Processing
SessionsController#new" rather than my controller, which looks like
it's due to the routing. In routes.rb I'm doing the usual
"map.devise_for :users" which I see creates this route:
new_user_session GET /users/sign_in
{:controller=>"sessions", :action=>"new"}
Since that's calling the sessions controller, it's of course not
calling the UsersController. Is it safe to create a custom
SessionsController that extends Devise::SessionsController and just
specifies "layout false"?
I'll try that when I get the chance later and see, but any advice
would certainly be appreciated. Thanks again.