Welcome aboard Java guy =), I hope you’ll enjoy the Rails world. Simply, to solve your issue you have 2 solutions: For each user create a table in the database and corresponding model. Create a single table in the database and for each user type create a model. This is called single table inheritance (STI). … Read more
Create a custom_failure.rb in your lib directory, with: class CustomFailure < Devise::FailureApp def redirect_url your_path end def respond if http_auth? http_auth else redirect end end end In you Devise initializer, include: config.warden do |manager| manager.failure_app = CustomFailure end Make sure Rails is loadin your lib files, in your application.rb : config.autoload_paths += %W(#{config.root}/lib) Don’t forget … Read more
I’m trying to figure this out myself. I just found this issue logged on Github https://github.com/plataformatec/devise/issues/issue/504/#comment_574788 Jose is saying that devise_error_messsages! method is just a stub (though it contains implementation) and that we’re supposed to override/replace it. It would have been nice if this was pointed out somewhere in the wiki, which is why i … Read more
I think the route for signing out is a DELETE method. This means that your sign out link needs to look like this: <%= link_to “Sign out”, destroy_user_session_path, :method => :delete %> Yours doesn’t include the :method => :delete part. Also, please note that for this to work you must also include <%= javascript_include_tag :defaults … Read more
As it turns outs ‘domain: all’ creates a cookie for all the different subdomains that are visited during that session (and it ensures that they are passed around between request). If no domain argument is passed, it means that a new cookie is created for every different domain that is visited in the same session … Read more
In your form are you passing in any other attributes, via mass assignment that don’t belong to your user model, or any of the nested models? If so, I believe the ActiveRecord::UnknownAttributeError is triggered in this instance. Otherwise, I think you can just create your own controller, by generating something like this: # app/controllers/registrations_controller.rb class … Read more