Here’s a method my colleague just showed me: # In config/application.rb module YourAppNameHere class Application < Rails::Application # Whatever else is already here… # The part to add config.to_prepare do Devise::SessionsController.skip_before_filter :your_before_filter_here end end end
I think you’ll need to manage the Devise views yourself. Try the following in a console: rails generate devise:views This will generate all the views Devise uses (including mailer templates), which you can now customize. The mailers you’re looking for should then be in ‘app/views/devise/mailer’ If you want to generate scoped views, or only a … Read more
Per the comments in the core application_controller.rb, set protect_from_forgery to the following: protect_from_forgery with: :null_session Alternatively, per the docs, simply declaring protect_from_forgery without a :with argument will utilize :null_session by default: protect_from_forgery # Same as above UPDATE: This seems to be a documented bug in the behavior of Devise. The author of Devise suggests disabling … Read more
config/routes.rb Create your own registration controller like so … (see Devise documentation for the details of overriding controllers here …) … which is more elegant way as opposed to doing it via the ApplicationController devise_for :users, controllers: {registrations: ‘users/registrations’} app/controllers/users/registrations_controller.rb Override the new method to create a Profile associated with the User model as below … Read more
You can configure the error messages in the locales file at: /config/locales/devise.en.yml Which should have something like below code and which you can easily modify to your liking: en: errors: messages: not_found: “not found” already_confirmed: “was already confirmed” not_locked: “was not locked” devise: failure: unauthenticated: ‘You need to sign in or sign up before continuing.’ … Read more
Well this little exercise in frustration turned out to be a good lesson in RTFM. I had set up Devise with confirmable, and when I created my layouts I neglected to insert the following lines: <p class=”notice”><%= notice %></p> <p class=”alert”><%= alert %></p> … as it clearly states to do in the getting started guide. … Read more
Did you use devise’s before action in your controller? before_action :authenticate_user!
Just in case anyone got here through Google – in the latest version of Devise, header_for takes two parameters. So your code would need to be: class MyMailer < Devise::Mailer backup_email = “…” def headers_for(action, opts) headers = { :subject => subject_for(action), :to => resource.email, :from => mailer_sender(devise_mapping), :bcc => backup_email, :reply_to => mailer_reply_to(devise_mapping), :template_path … Read more
Your routes.rb file won’t have any idea what role the user has, so you won’t be able to use it to assign specific root routes. What you can do is set up a controller (for example, passthrough_controller.rb) which in turn can read the role and redirect. Something like this: # passthrough_controller.rb class PassthroughController < ApplicationController … Read more
I’m using Devise 3.1.2, it has a placeholder method after_confirmation which is called after the confirmation finished successfully. We just need to override this method in User model. class User < ActiveRecord::Base devise :database_authenticatable, :registerable, :recoverable, :rememberable, :trackable, :validatable, :confirmable # Override Devise::Confirmable#after_confirmation def after_confirmation # Do something… end end See: Devise 3.5.9 Source Code: … Read more