How to output messages from Devise?

Question

Ruby on Rails

Actually, the messages themselves are displayed without problems, the problem is with displaying the message after registration, when it is necessary to inform the user that he is registered, but to activate the account, you need to go to the mail and ...
This very message is lost. After registration, you are redirected to a form with a username and password. I did the output of messages like this - https://github.com/plataformatec/devise/wiki/How-T...
Error messages appear on the registration form itself.
I'm talking about these messages:

registrations:
      destroyed: "Bye! Your account has been successfully cancelled. We hope to see you again soon."
      signed_up: "Welcome! You have signed up successfully."
      signed_up_but_inactive: "You have signed up successfully. However, we could not sign you in because your account is not yet activated."
      signed_up_but_locked: "You have signed up successfully. However, we could not sign you in because your account is locked."
      signed_up_but_unconfirmed: "A message with a confirmation link has been sent to your email address. Please follow the link to activate your account."
      update_needs_confirmation: "You updated your account successfully, but we need to verify your new email address. Please check your email and follow the confirm link to confirm your new email address."
      updated: "Your account has been updated successfully."

Answer 1

I did so. After registration, a standard message is displayed. A non-activated user is allowed by default. He comes in. If he points to his account, then somewhere in a conspicuous place in the account it is written that the mail must be confirmed if !user.confirmed is otherwise not displayed. And in general, there is a cabinet controller, it has a befort filter where the user is confirmed, if not, then we redirect to the page where everything is described in detail, that the selected action requires email confirmation and you should look into the spam if the letter did not arrive, or specify another soap etc. very detailed, links right there to resend the email with the confirmation code. Now all controllers that assume the use of profile functions are inherited from the cabinet controller. And any action will say that you need to confirm the soap. For example, user phones controller phone << cabinet. When adding, deleting and any action that requires changing the profile - we force you to confirm the email first. Well, this is my case. It doesn't have to be all tied up.

Answer 2

Add to layout/application.html.erb before yield

<% if alert.present? %>
  <%= alert %>
<% end %>

<% if notice.present? %>
  <%= notice %>
<% end %>