Rails%203%20In%20Action

180 CHAPTER 8 More authorization
Create a new controller now at app/controllers/registrations_controller.rb and fill it
with this content:
class RegistrationsController < Devise::RegistrationsController
private
def after_inactive_sign_up_path_for(resource)
confirm_user_path
end
end
By defining this new controller as inheriting from Devise::Registrations-
Controller, you inherit all the behavior from that controller and gain the ability to
override things such as the after_inactive_sign_up_path_for, of which you take
full advantage here. The resource argument is the User object representing who’s
signing up. You could use it, but in this context, don’t. Next, you need to tell Devise to
use this controller instead of its own. Alter the following line in config/routes.rb
devise_for :users
to this:
devise_for :users, :controllers => { :registrations => "registrations" }
The :controllers option tells Devise you want to customize the controllers it uses,
and with this new hash, you tell it to use the RegistrationsController you defined
for registrations. In this controller, you override after_inactive_sign_up_path_for
to go to a new route: confirm_user_path.
Because you’re overriding Devise’s controller, Rails won’t use Devise’s views. You
must copy the views from Devise into your application and move them into the app
/views/registrations directory. Lucky for you, Devise has a generator that places
Devise’s views in your application: devise:views. You can run the generator with
this command:
rails g devise:views
This command places Devise’s views into the app/views/devise directory of your application.
This directory shares the same name as the directory internal to Devise where
these views came from, and if a view exists in your application first, then Rails doesn’t
look for it in the engines attached to the application. With these files copied over,
move the app/views/devise/registrations directory out to app/views/registrations so
you have some views to use for your new RegistrationsController.
Now you must address the problem that although the confirm_users_path
method used in your RegistrationsController isn’t defined yet, redirect_to takes
users to that location. Define a route for it by opening config/routes.rb and inserting
this line underneath devise_for :users:
get '/awaiting_confirmation',
:to => "users#confirmation",
:as => 'confirm_user'