Rails%203%20In%20Action

Fixing what you broke
actions in it, checking if users are authenticated. If they aren’t, they’re redirected to
the sign-in page.
You can see all of this in action if you start your server using rails server and
attempt to sign up. Rather than being properly shown the “You have signed up successfully”
message, you’ll see the Sign In page, as shown in figure 8.3.
The configuration to send users to the root_path after sign-up is in Devise’s
Devise::RegistrationsController 1 and is defined in a method called after
_inactive_sign_up_path_for:
# The path used after sign up for inactive accounts.
➥You need to overwrite
# this method in your own RegistrationsController.
def after_inactive_sign_up_path_for(resource)
root_path
end
As you can see, this method is hardcoded to return root_path. The comment above this
method suggests that you override the method in your own RegistrationsController.
It means you must create a new controller called RegistrationsController 2 and,
inside this controller, override the after_inactive_sign_up_path_for method. To
give this controller the same functionality as Devise’s Devise::Registrations
Controller, you need to inherit from that controller. Finally, you can no longer redirect
to root_path, so you generate a new part of your application to present new users with
a message telling them they must confirm their account.
Figure 8.3 Sign-in page
1 The Devise::RegistrationsController can be found at https://github.com/plataformatec/devise/
blob/v1.4.2/app/controllers/devise/registrations_controller.rb#L93-95.
2 The controller could be called anything: it just needs a name so you can point Devise at it later.
179