There are several potential problems you may have:
Skip
If you miss the registration functionality, I would suggest that this would not allow Devise to call your RegistrationsController ?
I personally would do this (correct the routes):
#config/routes.rb root to: "users#index" (where ever your "logged-in" page is) devise_for :users, path: "", controllers: { sessions: "sessions", registrations: "registrations" }, path_names: { sign_in: 'login', password: 'forgot', confirmation: 'confirm', unlock: 'unblock', sign_up: 'register', sign_out: 'signout'}
This will give you the routes you need and go to a page with a verified signature in your application, thus either showing the login or registration page for Devise
Definition
Another problem you may have is a mis-definition of your Devise registration controller. We use this code in a very recent development application:
Perhaps you could try using :: before the Devise::RegistrationsController see if it calls?
Richard Peck
source share